Eco server problems and how to fix them

These cover almost every Eco ticket we see.

1. Players are refused after an update

Eco requires the client and the server to be on the same version, with no tolerance. When the game updates, restart the server from the panel so it updates too, then check the console for the version it reports and compare it with what your players have.

2. Config changes disappear

• Eco writes its config files when it shuts down. Editing a running server throws your changes away.
• Stop the server, edit, save, then start.
• If a file is not valid after your edit, Eco falls back to defaults for the whole file. That is why one missing comma can reset the server name, password and slot count at once.

3. The server is not listed

• Public listing has to be enabled in Network.eco.
• Give it a few minutes after a start.
• Give players the direct connect route with IP:Port in the meantime.

4. The first start takes forever

World generation is slow, and the console looks idle while it works. A large world can take many minutes. Do not restart the server during generation, or it starts again from the beginning.

5. The server slows down as the world grows

• Eco simulates plants, animals and pollution across the whole world, so load grows with the settlement.
• Lower the player limit if you are near the limits of your plan.
• If the console shows the process being killed rather than an in game error, it ran out of memory and a larger plan is the fix.

6. A mod broke the boot

Read the console for a compile error, move that mod out of the Mods folder, and restart. See the mods guide in this category.

Open a ticket from Support in the Client Area with the last 50 lines of console output if none of this fits.