Short version: almost every mod problem on a Deadside console server is solved by one of three things: a restart, a retry, or removing the mod. Here's the map. Setup basics are in the install guide.
"I installed a mod but it's not on my server"
You haven't restarted since the change. This is by far the most common case. The Mods page shows an amber banner ("Your mod list changed. Restart the server for it to take effect.") until you do. Restart from your service page; the server picks up your mod list at startup.
"Browsing is unavailable"
If the Mods page shows a locked panel instead of the catalog, mod browsing is switched off or not configured for this game right now. The panel says why. Your already-installed mods stay listed and can still be removed. If you believe this is wrong, contact support.
mod.io errors or endless loading in the browse grid
mod.io (the catalog service) is occasionally down or rate-limits requests. The browse grid shows an error with a Retry button when that happens. Your installed mods keep working: the catalog is only needed for browsing and installing. Wait a little and retry.
"I don't see a Mod.io icon at all"
Your panel account doesn't have the mod manager permission, which can happen with sub-user accounts. Contact support and we'll sort out the access.
A mod is crashing the server or breaking the game
Remove it: × on the mod's card in the Installed mods strip, confirm, restart. Removal works even when mod.io is down. If you run several mods and aren't sure which one is at fault, remove the most recently added or most recently updated one first, restart, retest.
Where our support ends and the mod author begins
We support the panel side: browsing, installing, removing, load order, and your mod list reaching the server at startup. What a mod does once it's running (bugs, conflicts, breakage after a game update) is the mod author's territory; their mod.io page is the right place for reports. The escape hatch is always the same: remove the mod and restart.
