Sharing
Limits
Numbers
| what | limit |
|---|---|
| a graph's run | 10,000 steps before a Wait |
| runs started by runs | 16 deep |
| function calls | 64 deep |
| added pins on a node | 16 |
| a graph's log | 1,000 lines |
| a message to players' machines | one value, 1,024 bytes; text 512 bytes; lists 32 items |
| messages sent | 20 a second per graph |
| Send near | 500 metres |
| an expression | 1,000 letters, 400 parts, 48 deep, 16 inputs |
| a list | 100,000 items |
| people made by graphs | 64 alive at once |
| brain graphs | 1 ms per person each weighing up, 2 ms for everyone each frame |
| arena weapons, armour pieces | 4,096 each in all |
| mod bodies | 32 in all |
| a loadout's points | 100 |
What mods never reach
Patches and graphs reach only the game's own gameplay. Nothing a mod does touches:
- files outside its own folder, processes, the network or the web
- Steam, the Workshop, achievements
- saving and loading, except saved graph variables kept by the game
- the mod system itself, dev grants, roles or admin
- reports, settings, chat as another player, or quitting
Patches never reach the mod system, the network, saving or reports, nor the content catalog, the network's prefab table, the recorder's catalog or achievements. Graphs reach only the nodes the game offers.
Not yet
- A weapon's own hit effects (what flies off where a blow lands), a muzzle flash picture, scabbards for new pictures
- New kinds of things that need code the game hasn't got (a vehicle that drives a new way). Props, buildings and animals are copied and changed with patches.
- New shaders
- Villages in a mod's map: their generator runs only in the Unity editor
- Game events that only the host sees reaching a guest's graphs by themselves: a graph forwards them with a Send node
- RP data already read keeps its old rows when mods are switched during a game; outside a game it is read again
- Waiting for a Workshop download to finish before joining: the join waits for the next start
Modding