It seems like players who are respawned in verse using .respawn(), aren’t being appropriately counted as being alive and/or internally being given their life back. I wonder if this has anything to do with these other bugs? This creates a lot of issues with fortnite’s spectate system as well, often leaving players in my game stuck spectating one specific person in my game, who’s class has more allowed lives, or no one at all, due to fortnite thinking everyone is dead when that clearly is not the case. But no matter what I feel like calling .respawn() should internally count as the player getting a “life” back. I think that would fix all of these bugs. If you switch to a different class, the player should internally get all of their “lives” back associated with the max spawn count of that class, etc. Yet no matter what, the total lives a player has seems to continue to bleed down, whether you respawn them manually, whether you switch their classes, etc.
Example, if a player dies and they are part of a class with total spawn limit of 1, and then respawned using verse, all of these glitches mentioned in the thread seem to come to light. I’ve also noticed other weird bugs occur, such as
Players not being rewarded xp when in this “dead but actually alive” state
Players in this state can’t be spectated as mentioned previously
Players might be moved onto the same team, even when island settings are set to FFA. Then reboot cards and DBNO start dropping or happening when you dont expect it, forcing you to explicitly turn on reboot cards and set them all to false, AND turn on team damage so your FFA gamemode doesnt become a team game
If a player in this “dead but actually alive” state is eliminated again, while currently dead, without isValid being checked on them, they will get locked forever and not respawn.
Just a ton of broken interactions.
There are a lot of other weird issues and interactions mentioned in this thread. But what is the root cause? To me it seems like fortnites internal engine is not counting players as being alive when using .respawn() from a dead state and having only 1 total allowable spawn (or having consumed all available respawns afforded to them), and that is what crops up all of these other issues
LETS GOO!! Thanks to all the team that worked on this bug and special thanks to you @Flak the creators will do some very interesting things with this bug fixed!!!
Hey so this bug kinda came back, when we added a player to an ignore list of a barrier and then the player dies, the barrier stops letting the player inside of it, this only happends when you respawn them with verse
This was never fixed properly. I took out all my work around code when 35.00 was released and let Respawn() work on its own. A couple days alter I was playing and some weird stuff was happening. I don’t remember what it was exactly, but think it was a player was downed when they were the last player on a team. So I immediately reverted back to our old code. That was early May.
@Flak this was not fixed correctly, the function is still not working literally, now it is worse than before, when you are eliminated by a player, the .Respawn() does not work.
Hey @Flak any updates? The fix made it even worse now the players don’t respawn some times and it broke all of my games mechanics, I can’t even properly play one match in my game since it’s super broken
@Flak so we found out a new bug with the Respawn Function, when we call it in our map sometimes the games glitches and shows them “alive” in the player counter, but the player shows dead and is dead in the game
You can see at the top left the 3rd player is dead, but on the right side it says theres 3 players alive, we cant call another respawn function since the player is “alive”, this bug doesnt happen 100% of the time, but once it does theres no way for the player to be spawned again, unless we end and start a new game
okay so after a few test the player counter seem to match the actual amount of alive players, but the respawn function still breaks and player do not respawn, even when calling the function multiple times, and even on a team/class that has no spawn limit
the creators will do some very interesting things with this bug fixed!!! 
