IMO, A player being added to the Playspace doesn’t mean he’s controlling a character.
I agree that this being random is weird, but I don’t think you should rely on this function to retrieve the fort_character. We all have to make the difference between the fort_character and the player. What if your player spawns in spectator ? He shouldn’t have a fort_character.
Also whenever your player disconnect you’ll notice that the fort_character.IsActive[] won’t work anymore.
Not saying this is not a bug, but I’d understand if they told you so.
PlayerAddedEvent means a player has connected to the map but it does not mean they have fully loaded in. It is possible they have not spawned in and/or not been assigned a fort_character yet. You can tell this by the black screen and the loading at the bottom right.
You should always use the spawned event to grab newly added players instead of player added due to this “bug”
PlayerAddedEvent says “Returns a subscribable with a payload of thefort_character that entered the fort_playspace.” which to me is a guarantee that during that callback calling into GetFortCharacter should not fail.
Either way, something has to happen. A bug fix or decimation update and clarification.
No the function returns a player, it should not return a fort_character, I want this function to be called even when I send my players to spectator on start you know, I think the doc is just not up to date.
Well I know that the payload returns and that the documentation is somewhat off there as well. The point is that per that documentation we should expect fort_character to be accessible during the callback. Something is clearly off and the verse team has to provide some update to something.
