Summary
When: today, November 17, 2026, about 11:43 AM to 12:31 PM Pacific (19:43 to 20:31 UTC), on a live public server of island 1019-5361-6272.
On that live public server of our published island (Max Players = 4), one player who was no longer in the game stayed on the server’s player list for at least 40 minutes and never got removed while we watched.
GetPlayspace().GetPlayers()kept returning him andPlayer.IsConnected[]kept succeeding.- His row on our scoreboard showed 0 / 0 / 0, which is what our code shows when
GetPersistedDatafails for a player; every real player showed their real values. - Fortnite’s social menu did NOT count him: it showed the session as 4/4 while the server listed 5 players, and later 3/4 while the server listed 4.
- Matchmaking kept admitting new players into the slot he still held on the server, so the server effectively held Max Players + 1.
- As far as we can tell
PlayerRemovedEventnever fired for him (our leave handling never ran for him).
Impact: our island gives each of the 4 players a base. The ghost kept his base for the life of the server, so every 4th real player who joined got stuck on our loading screen with no base. One stuck player gave up and left; the next joiner got stuck the same way.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Matchmaking
Steps to Reproduce
We could not reproduce it on demand; it was seen on a live public server. What happened, in order:
- Publish an island with Max Players = 4 and play it live with 4 players.
- One player drops (we believe without a clean exit; we don’t know how).
- That player stays in
GetPlayspace().GetPlayers()withIsConnected[]succeeding, but his persisted data can’t be read andPlayerRemovedEventdoes not fire. - Fortnite’s social menu shows one fewer player than the server lists (4/4 vs 5 on the server, later 3/4 vs 4).
- Matchmaking lets another player join, so the server now holds Max Players + 1.
- The ghost player was still on the list after at least 40 minutes.
Expected Result
A player who leaves or loses connection is removed from the playspace, PlayerRemovedEvent fires, and IsConnected[] fails for him. The server never holds more players than the island’s Max Players, and matchmaking and the server agree on the player count.
Observed Result
The player stayed in GetPlayers() with IsConnected[] succeeding for at least 40 minutes, his persisted data could not be read, and matchmaking admitted a 5th player into a 4-player island. Photos attached: the in-game player list next to Fortnite’s social menu count.
Platform(s)
Live public server. Seen from Nintendo Switch; other players’ platforms unknown.
Island Code
1019-5361-6272
Upload an image



