Setting Up Server Admins
Admin permission design in Vein should follow least-privilege rules so moderation remains effective without risking accidental destructive commands.
Admin List Configuration
Admins are managed via the Admins.json file located in your server's configuration directory.
Adding an Admin
- Find the player's SteamID64.
- Add the SteamID64 to the
Admins.jsonarray. - Restart the server to apply changes.
In-Game Admin Mode
Once added, the admin can press the designated console key (usually ~ or F1) to access the command line.
Permission Model Blueprint
Use tiered roles instead of full-admin by default: moderation, support, and owner-level control. This reduces blast radius during disputes and prevents routine staff actions from modifying critical world or security settings.
- Role split: Separate player management rights from server configuration rights.
- Credential hygiene: Rotate admin access after staffing changes or inactivity.
- Action logging: Keep a changelog of privilege edits and enforcement events.
Operational Checklist
Treat this topic as a repeatable server operation, not a one-time change. Schedule changes during lower traffic, announce maintenance windows, and keep a rollback snapshot before each update. If your server is modded, validate changes on a staging copy first so startup logs, world loading, and player joins are confirmed before production rollout.
Validation Steps
- Capture baseline metrics: Record CPU, RAM, and average player ping before changes.
- Apply one change at a time: Avoid batch edits that make root-cause analysis difficult.
- Review logs after restart: Check for version mismatch and dependency warnings immediately.
- Run a real join test: Confirm fresh clients can connect and complete core gameplay actions.
- Observe for at least 24 hours: Validate behavior under peak load, not only right after reboot.
Performance and Stability Notes
Most hosting incidents come from resource spikes combined with configuration drift. Keep restart cadence predictable, review world/save growth weekly, and cap optional systems that generate extreme entity counts. When performance drops, compare with your last known-good baseline and revert recent high-risk changes quickly to reduce downtime.
Backup and Rollback Policy
Use automated daily backups plus pre-change snapshots for risky operations. Keep at least one off-node copy and test restore procedures routinely. A practical retention strategy is 7 daily, 4 weekly, and 2 monthly restore points. If a change causes instability, roll back first, stabilize service, and then reattempt with a narrower test scope.
Game-Specific Hosting Notes
- Experimental updates: Keep controlled rollout windows and verify save compatibility.
- Admin permissions: Audit privilege assignments after patches to prevent accidental escalation.
- World integrity: Validate persistence after restarts and crash recovery before reopening.