Live server keeps a disconnected player in GetPlayers() with IsConnected[] = true forever; matchmaking ignores him, so the island overfills past Max Players

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 and Player.IsConnected[] kept succeeding.
  • His row on our scoreboard showed 0 / 0 / 0, which is what our code shows when GetPersistedData fails 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 PlayerRemovedEvent never 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:

  1. Publish an island with Max Players = 4 and play it live with 4 players.
  2. One player drops (we believe without a clean exit; we don’t know how).
  3. That player stays in GetPlayspace().GetPlayers() with IsConnected[] succeeding, but his persisted data can’t be read and PlayerRemovedEvent does not fire.
  4. Fortnite’s social menu shows one fewer player than the server lists (4/4 vs 5 on the server, later 3/4 vs 4).
  5. Matchmaking lets another player join, so the server now holds Max Players + 1.
  6. 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

2.png

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

Correction to the original post: IsConnected[] in my report is a helper in our own code, not a Fortnite API, so please ignore it. It only fails after our PlayerRemovedEvent subscriber has marked the player.

In Fortnite API terms, what we actually saw for the ghost player was:

  • GetPlayspace().GetPlayers() kept returning him for 40+ minutes.
  • Player.IsActive[] failed for him, which per the digest means he had already left the game.
  • Our PlayerRemovedEvent subscriber never marked him as removed. Either the event never fired for him, or a later PlayerAddedEvent for the same player cleared our mark. We can’t tell which from our side.

So the mismatch is: a player who is no longer active (left) stays in GetPlayers() indefinitely, while matchmaking treats his slot as free and lets another player in. Expected: once IsActive[] fails, the player leaves GetPlayers() and PlayerRemovedEvent fires.

Our workaround checks IsActive[] directly: a player who stays listed while inactive for 150 seconds gets his base freed, is hidden from our player lists, and is sent off with SendToLobby().