Eco Server Mod Loading (SLG)

Installing Mods on Eco

Eco modding can greatly improve server identity, but unmanaged mod stacks are a frequent source of startup failures and season-breaking incompatibilities.

Installation Steps

1. Stop the server.
2. Download the mod (usually from mod.io or Eco forums).
3. Extract the files into the Mods folder in your server root.
4. Restart the server.

Client Requirements

Most Eco mods are server-side, but if a mod adds new assets (models, textures), players must also install the mod locally to join.

Troubleshooting

If the server fails to start, check the Log.txt for "Reflection" errors, which usually indicate outdated mods.

Mod Lifecycle Management

Run mods through a lifecycle: intake, staging validation, production rollout, and post-update audit. Treat every game patch as a compatibility checkpoint and communicate temporary mod freezes when upstream support is uncertain.

• Intake: Evaluate maintenance activity and dependency footprint before adoption.
• Staging: Boot test with representative player data and verify no schema/runtime errors.
• Production: Roll out during low traffic and monitor logs for reflection or serialization faults.

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

• Simulation tuning: Law, meteor, and economy settings should be tested together to avoid destabilizing progression.
• Admin policy transparency: Publish governance rules clearly so law changes do not feel arbitrary.
• World lifecycle: Plan season length and wipe criteria before launch to prevent mid-cycle conflict.