Ready to power up your Soulmask server with mods? Smart move: more content, more replay value, more fun. Follow these clear steps—even if this is your first time.
Prerequisites
- Access to your Oxygenserv panel (login and password)
- A Steam account and access to the Soulmask Workshop
- A shortlist of mods you want to run (Workshop links)
- Permission to stop/start your server when needed
Detailed steps
-
Create a Steam Workshop collection for Soulmask
In Steam, open the Soulmask Workshop and click “Create Collection.” Give it a clear name (e.g., “Soulmask Server Mods”) and set visibility to “Public” or “Unlisted” (not “Private,” or the server can’t download). Add your desired mods via “Add/Remove Items,” tick them, and save. Pro tip: start with 5–10 mods to validate stability first. If you use the website, make sure you’re logged into your Steam account. -
Copy the collection ID
Open your collection page and look at the URL. You’ll see something likehttps://steamcommunity.com/sharedfiles/filedetails/?id=3123456789. Copy the digits afterid=only (e.g.,3123456789). If you copy a single mod ID instead of the collection ID, auto-download won’t trigger. -
Stop the server from the Oxygenserv panel
Log into your Oxygenserv panel, open your Soulmask service, and go to “Console” or “Overview.” Click “Stop” and wait until the status shows stopped. You’ll see the logs stop scrolling and the status turn red/gray. If it hangs, wait 30–60 seconds and try stopping again. -
Paste the ID into the Workshop startup field
Go to theStartuptab. Find the Workshop field (e.g.,Workshop Collection IDorWorkshop Collection). Paste the numeric ID from step 2—no spaces or extra text. If you see a toggle likeAuto download WorkshoporAuto update Workshop, enable it. Click “Save” at the top. -
Start the server and let it download the mods
Click “Start.” Open the console to watch the automatic Steam downloads. You should see lines likeDownloading Workshop collection...andDownloading item 123456789.... First boot can take several minutes depending on the number and size of mods. If you see401 UnauthorizedorFailed to download, the collection is likely private or the ID is wrong. -
Verify that mods are loading
When you seeServer startedin the logs and the status turns green, join your server in-game. Check for a feature or item added by a mod to confirm. You can also spot lines likeLoaded mod ...in the console. If the server loops or crashes, remove the last added mod from the collection, save, and restart to isolate the culprit. -
Keep mods updated the easy way
On each restart, the server can fetch updates ifAuto update Workshopis enabled. Best practice: schedule a daily restart during off-hours to keep versions in sync. After a major game patch, perform a second restart if needed to ensure everything updates. If a mod breaks after an update, disable it in the collection, restart, and look for a compatible version.
Tips & optimization
– Keep your collection to 20–30 mods max for reasonable boot times and easier troubleshooting. Fewer interdependencies means more stability.
– Collection order can influence load behavior. Put shared libraries on top, dependent content below.
– Back up your save before adding heavy mods. Download your saves from the panel so you can roll back if needed.
– Track mod IDs in a text file (e.g., 3123456789, 2987654321) to share configs and speed up support.
FAQ
The server starts without mods—why?
Make sure you pasted the collection ID (not a single mod ID). Ensure the collection visibility is “Public” or “Unlisted.” Confirm the Workshop Collection ID field is saved and that you restarted afterward. Check the console: if there’s no Downloading Workshop collection, the ID/field is incorrect.
How do I update mods safely?
Enable Auto update Workshop if available, then restart the server. After a game patch, do a second restart to fully sync updates. If a mod won’t update, remove it and add it back to the collection, save, and restart.
The server crashes after adding a mod—how to diagnose?
Remove the last added mod (or disable it in the collection), save, and restart to test. Re-add mods one by one to find the offender. Verify version compatibility with your Soulmask build and read the logs to find the error line right before the stop.
Your Soulmask server is now mod-ready and tuned for your community. Add content in small batches, test, and you’ll keep it stable, fast, and fun.