Skip to content

Overview

PokeLoom games can be played together. Co-op, link battles and online features are not a separate product. They are one engine feature with three parts, all built on one rule: every player’s machine runs the same deterministic game, and what crosses the network is inputs and choices, not pictures or state. This page is the map of the parts. Co-op and The server and online play go into each.

The engine is deterministic: the same inputs and the same seed give the same game on every platform (see Determinism). So two machines that start from the same state and receive the same inputs stay in the same state without sending it. A battle sends each player’s choice; a shared field online will send each player’s buttons a tick. After every choice in a battle, each side compares a short digest of its state with the other’s; if they differ, something is wrong, and the session knows exactly where.

This keeps the traffic tiny: a few bytes a tick a player. That matters on the DS, whose wireless sends small packets and whose memory has room for little else. Every answer from the network is written into the input log at the tick it arrived, so a recorded online session replays exactly with no network at all.

Way What runs where For Players
Shared field every machine runs the same world with all the players in it; each tick waits for every player’s input puzzles where players touch the same things, a story played as one, two players on one desktop 1 to 8
Together each machine runs its own world; others are drawn from their steps; declared flags, variables and events are shared friends roaming at their own pace and meeting for battles and shared events 2 to 16 a room
Persistent shared world the server runs and mirrors the world and owns everything of value an online game with many players many, in channels and shards

A game picks per map, so a group can roam “together” and step into a shared-field dungeon. Built today: the shared field on one machine. Planned (plan 43, plan 33): the shared field online, together mode and the persistent world.

Part State
Several players in one field on one machine built: up to 8 in the world, at most two local inputs on a desktop (keyboard, a second key set, gamepads); [coop] in game.toml
Script rows for several players built: players, playerson, triggerplayer, leash; actors player2 to player8 and trigger
Link battle between two desktops built: through a server or a game hosting it; digests equal after every request
pl-net built: messages, 256-byte frames, the TCP stream, the battle lockstep with commit and reveal
ploom-server built: rooms by a six-letter code, pairing whoever asks next, relay, a timer on each choice, LAN discovery
netbattle built: a script command that starts a link battle
Desktop with melonDS partly: the battle starts, then stalls after the first choice; the cause is not found
DS with DS not run
Encryption, accounts planned (plan 33)
Everything else online planned (plan 33, plan 22)

A game built without online play links none of the network code: on the DS its ROM is the size it would be without the feature.

  • Rules and data. A link battle runs the same battle engine with the same data as a game alone, checked against Pokémon Showdown. Both players must have the same pack; the server refuses a player whose game or pack differs.
  • One model. Co-op behaviour is settings ([coop]), records (battle setups) and script rows. No game’s co-op is its own engine code.
  • Platforms. A DS and a desktop are meant to play together. Presentation may differ between them; the game may not. Until the desktop–melonDS stall is fixed, that is a goal, not a fact.
  • Co-op: several players in one world, what is set in [coop], and co-op battles, saves and cutscenes as designed.
  • The server and online play: ploom-server, link battles, and the planned accounts, trades, gifts, markets and events.