vsemenyakin
Wed, 03 Apr 2019 13:17:56 +0000
Multiplayer & Networking

GameMode - GameState architecture issue

There are several places (Documentation, AnswerHub) where using of Game Mode & Game State is discribed in details. This architecture looks logical when Game Mode is small and simple. But when Game Mode becames more complex it’s good idea to separate it’s logic using Game Mode Components. And according to Game Modes architecture every Game Mode Component should be connected with Game State Component that holds Component state access logic for clients.

So, the question is - what sense in separating Game Modes & Game States? Why not manage Game Modes and it’s components as all other Actors, using replication, RPC & NetRole checks for control what API is client-accessable and what is server-only?

1 post - 1 participant