Server mods and client mods
Every mod says what it is. A server mod (or one all players need) runs on the server, and players download it when they join. A client-only mod, such as a status display or a minimap tweak, runs on each player's own game: enabling it on a server changes nothing. On Flux, the Mods tab marks client-only mods so you do not wonder why one has no effect.
Add a mod
- Open the mod on the Steam Workshop and copy the number at the end of its link: its ID.
- On Flux, add it in the Mods tab, or list IDs and links in Workshop Mods when you deploy. By hand, add ServerModSetup("ID") to mods/dedicated_server_mods_setup.lua and ["workshop-ID"] = { enabled = true } to modoverrides.lua in both worlds.
- Restart the server: it downloads the mod and loads it.
Collections
A Workshop collection is a list of mods. On Flux, give its ID or link and every mod in it is downloaded and switched on; by hand, ServerModCollectionSetup("ID") only downloads them.
Mod settings
Most mods have options, written into modoverrides.lua as configuration_options. On Flux the Mods tab reads each mod's own list from the mod itself and shows it as dropdowns with the author's labels, for both worlds at once.
Updates
Players download a mod's newest version when they join, so a server with an older one turns them away. Our image checks the server's mods against the Workshop every 30 minutes and restarts onto a new version, warning the players first.
Frequently asked questions
How do I add mods to my Don't Starve Together server?
Add the Workshop ID, enable it in modoverrides.lua for both worlds, and restart. On Flux, the Mods tab does both.
Do players have to subscribe to the server's mods?
No. They download the server's mods automatically when they join.
Why does a mod do nothing on my server?
It is probably client-only: it runs in each player's own game, and each player installs it themselves.