ue-gameplay-framework

In Unreal Engine multiplayer, GameMode exists only on the server and defines game rules, while GameState exists on both server and clients to sync replicated game data like scores. GameMode handles spawning logic, whereas GameState broadcasts state to all connected players.

Unreal Engine 5 handles the player lifecycle through PlayerController and PlayerState classes. PlayerController manages input and exists only on the owning client and server, while PlayerState tracks persistent player data like scores, replicating join and leave states seamlessly across the network.

Player score data in Unreal Engine should be stored in the PlayerState class. PlayerState replicates to all clients, ensuring every player sees consistent scores. Avoid placing replicated score variables in the Pawn, which only represents the physical avatar and has limited network authority.

Unreal Engine gameplay framework supports seamless travel to preserve player continuity across maps. Seamless travel mechanics carry PlayerController and Pawn references forward without dropping the connection, preventing client disconnects during server transitions and maintaining active replication states.

Unreal Engine RPCs fail on the server when called from unauthoritative clients or without proper replication setup. Ensure the calling actor has replication enabled, verify the RPC direction, and confirm the PlayerController has authority. Server RPCs require the caller to be owned by the local client.

PlayerController in Unreal Engine is designed for client-side input handling. It exists on both the owning client and the server, parsing input and translating it into actions. Movement and interaction logic should route through the PlayerController before replicating resulting state changes to the server.