Sharing
Online
Players meet online only when they have the same mods with the same files.
The stamp
Every file of a mod is hashed into its stamp. The mods' things are listed after ours in the handshake's content list, with the stamp of every mod, so a server and a player with a different file are told apart. A mod's thumb.png is not part of it.
Joining a server with other mods
A server refusing a join for its content names its mods. The joining game asks on the connect sheet:
- Switch to its mods and join: the server's set of mods becomes yours, and you join. The Mods page says a server's mods are on in place of yours, with Put mine back and Keep these.
- Get ... for each one missing: subscribed on the Workshop. The join waits for the next start.
An older server names none: the question is then to switch mods off.
How many fit
| what | in all |
|---|---|
| arena weapons | 4,096, ours and every mod's (about 4,000 from mods) |
| armour pieces | 4,096 (about 4,000 from mods) |
| mod bodies | 32, from every mod |
| content ids (things, items, quests a mod adds) | about 62,600 past ours |
On the wire, a weapon or piece of ours takes one byte, a mod's two.
What runs where
- New things, items and quests a patch adds are content after ours, as mod weapons are.
- Things placed in scenes are made where the game is decided and reach players as anything spawned does.
- Graphs send nothing over the network by themselves: each machine runs its own copy, every node on the side it says (Online sides).
- Brain graphs run only where the game is decided.
- A dedicated server reads no sounds. The official servers run no mods.
A dedicated server
Starting one, its modes and maps, the console and updating: Running a server.
Modding