Rejoining a Game Is Broken - Respawn Verse (GAME BREAKING BUG)

General Issues and Bug Reporting
, , , ,
1

Summary

When rejoining a game that you have been called to respawn via Verse (during your first visit). The game will no longer consider you a player in the game.

You will not appear on the Fortnite scoreboard.
You will not receive items via Fortnite devices.
You will become apart of another players team (even if set to FFA).

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

  1. Call the built in Respawn() function on a player.
  2. Have them leave and join back (same session)
  3. Once they join, look at scoreboard, try granting them items via Item Granter.

Expected Result

The player shouldn’t be treated any differently between the 1st join and next.

Observed Result

Basically nothing works on them because they don’t seem to be considered an agent to the game.

Platform(s)

Everything.

Island Code

1940-1982-6871

Additional Notes

I will be more than happy to share snippets of my code to show that it cant be anything else besides the respawn. (the island code is effected by this, players respawn when a new round starts)

If there is a workaround, please reply below if you are willing to share.

2

You need to wait for the player to be fully added, before you can teleport or put in teams/ grant weapons etc.

If you want to persist player stats or loadout, add the save point device.

1 Like
3

I wait 5 seconds this seems to be the nice number for everything to work. Some people use the run event ect too

4

I agree I see the exact same thing. Although I am not sure it is tied to Respawn(). It appears to be random. What appears to be happening is the PlayerAdded event is NOT firing. I am using a Player Spawner Event. This happens randomly. I just tested with one of our games and a player rejoining randomly appears to not be added into the game: they are not getting a HUD, item granter does not give them any items, etc. I had it happen on 3 out of 6 rejoins to same game. Twice after a Respawn(), one time without a Respawn(). This appears to be new with 36.00

1 Like
5

FORT-925256 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

6

Are you saying on all player joins? New or rejoining? Well I guess it would have to be all, no way to tell if a player is rejoining.

7

Yea any player joining if you have maps ect make sure to remove the player and do proper cleanup when they leave or it could mess your game up.

1 Like
8

I think this is working as intended, I’ll have someone check.

9

This is only when a player who was in a game REJOINS the same game. Which is common for maps that dont have a lot of players. I here what @AtAshTag is saying, and I have never seen an issue before when using the SpawnedEvent from Player Spawner. I use Player Spawner for my player adds. Player Spawner occurs after PlaySpace.AddedEvent. The island I am seeing this on was introduced before 36.00 and I tested join in progress a lot and it was a lot of rejoins and I NEVER saw an issue. As I said earlier I was able to see an issue on 3 of 6 rejoin attempts.

10

Please define what you think of as proper cleanup? I remove players from my Player Map, what else can you do? It just seems to me that Epic leaves a footprint and crumbs for players in games they were once part of and we have no way to control/clean that up.