Multiplayer

EOR is intended to remain active in multiplayer, but every participant must run the same deterministic content.

Required matching

  • Install the same EOR release and build identity on every computer.
  • Use the same full or mod-only content revision; do not mix old JSON/assets with a new DLL.
  • Match gameplay-affecting configuration, especially market, quest-board, affix, and content options.
  • Select the same campaign modifications on every client. FTK2 does not make the host's local selections replace everyone else's choices.
  • Use the same FTK2 game version and DLC availability.

The main-menu build signature and diagnostic configuration summary help identify near-matches that share a version number but not identical content.

Network safeguards

EOR uses deterministic seeds and host/client snapshots for markets and quest boards, stable content fingerprints, synchronized sanctum ownership work, and multiplayer-safe guards around custom actions. Presentation-only systems such as the free combat camera remain local.

Deliberate limitations

Custom town specialist services are disabled online. This affects Pet Trainer, Mercenary Captain, Relic Broker, and Sanctum Pilgrim, not ordinary synchronized markets or quest boards. Development/debug mutations should remain disabled.

If a desync occurs

  1. Stop rather than repeatedly advancing turns.
  2. Compare the complete version/build text on both clients.
  3. Verify or reinstall the entire archive on every computer.
  4. Compare campaign modifications and EOR configuration.
  5. Press F8 to submit a report from each affected computer; use Ctrl+F8 or Shift+F8 for a forced report if the description prompt cannot complete.