Repository navigation
Load Order and Priorities
When several sources have the same content id, one of them wins. The game decides per id, in layers:
| Layer | What | Wins over |
|---|---|---|
| 1. the disc | the game's own content | |
| 2. Project Avalanche | the port's own content (markers, skies, the menu's files) | the disc |
| 3. your mods | the switched-on mods on the Mods page | the disc and the port |
| 4. the server | a server's resources, while you are on that server | everything below |
Among your mods, the one with the higher priority in its resource.toml wins; on the same priority, the one
lower on the Mods page's list (later in mods.toml) wins. A newly installed mod goes to the end of the list, so it
wins over the others of its priority. Use Up and Down to change the order.
Patches do not replace each other: every patch of a record applies, in load order, on top of the winning record. Two mods that change different fields of one board both take effect; where they change the same field, the later one wins.
Requirements do not change the order: a mod whose [dependencies] require is missing, switched off or of a
version out of range is skipped at the start, with the reason. A mod that changes another mod's content belongs below
it on the list (or at a higher priority).
The Mods page's BEFORE PLAY tab lists every conflict with its winner (Installing Mods).
Servers
- Hosting a Server
- Server Configuration
- Ports and Firewalls
- Server Console
- Operators and Remote Console
- Access Control List
- Bans and Mutes
- The Server List
- Query and LAN Discovery
- Server Resources
- Blocklists
- Maps and Gamemodes
- Logs and Metrics
- Running as a Service
- Running in Docker
- Joining a Server
Scripting
- Resource Packages
- Content IDs and Kinds
- Scripting Overview
- Server Script API
- Client Script API
- Events and Messages
- Script Permissions
- Script Examples
Modding