Whether a knight can reach a tile or a card can be played is a decision for the game's rules. Nerdino Platform handles the shared work around multiplayer, so each game does not have to build all of it again.
Decisions that belong to the game
The game decides whether an action is legal, what changes after it and whose turn comes next. Those choices give a game its character. Putting them into shared infrastructure would make other games work around assumptions they never asked for.
The same applies to what players see. A game decides which information a player is allowed to know and how to present it. The platform should support those choices without prescribing the board, the cards or the way a turn feels.
A shared answer about the match
Players need to agree on which moves counted. A client can show the board and send an action, but drawing a move on screen does not make it valid. The server checks it against the game's rules.
That matters when a connection drops, too. Returning players need an accurate view of their match, including any changes that happened while they were away.
Separating these responsibilities also gives us a clearer place to investigate problems. An illegal move points toward the rules that evaluated it. Trouble connecting or recovering a saved match points toward the infrastructure.
Work worth sharing
Accounts, saved matches and client connections are work we expect to need across projects. Deployment tooling and client SDKs belong alongside them. Reusing those pieces should reduce the work required to get another game running.
There are still limits to what any shared system can support. We are building against the needs of our games and checking where those needs overlap. That does not establish that the platform fits every kind of multiplayer game.
Keep testing the boundary
A turn-based game played in one sitting can feel very different from one played over a week. Games need room to choose their timing and decide what happens when a player takes too long.
Battle for Velune gives us a concrete place to test that freedom. Its rules describe the tactical game; the platform supplies the surrounding infrastructure. If a platform interface makes a tactical rule awkward to express, we need to look again at that interface.
