Eco Dev Tracker

Hey Kenny,
sorry to hear you have crashes - it will likely say why it crashes in the logfiles though, so please send over your client logs to [email protected] and we'll give it a look: https://github.com/StrangeLoopGames/EcoIssues/wiki/Getting-the-Eco-game-log-file

In that case I'd need to see the server logs. You need to pay attention that the mods are actually compatible with Update 9.7, which has just released, so most mods won't be updated yet.

I'd need a bit more info about what is not working to say anything, but you can download mods manually and install them from here: https://eco.mod.io/

My expectation was obviously not correct, one of the many reasons why I typically don't give ETAs, but we should manage this night. Sorry for the inconvience.

Am I assuming correctly that the areas where you are getting ejected there is water somewhere _above_ you? We are working on a remedy for that problem.

This will be addressed in Update 9.7.2 which I expect to be released in ~ 6 hours.

For the meteor it seems that for some reason your configuration in Configs/Disaster.eco got reset - that can happen if you edited the .eco.template file directly (that gets overwritten on each update) instead of the .eco file or the edited file got lost for some other reason.

You can fix that by setting the meteor in Disasters.eco to false again and then restore a backup where the meteor didn't land yet (it probably hit when you loaded your world the first time after the config was no longer set to false) from /Storage/Backups/ to the Storage folder and load that and you should be good again. (.db and .eco file)

As for the mods, it is expected that after a new major update mods need to be adapted - the changelog states changes that need to be made to any overrides in the "Modkit" area and third-party mods likely need updating as well - Nid and Kye seem to have pre-release versions available, we informed major modders a while before release what is coming.

Glad to hear that solved it :)

Seems you already found a solution yourself, great to hear, that was a new one. It's known that Steam sometimes needs a restart, but that will help future users with the same issue :)

Weather is aesthetic only at this time, you're experiencing the meteor hit, though. There is visual weather as well, but it's still a bit buggy.

As for the meteor: The settings of Eco are not saved per world, but globally. Whenever you change the settings or they get reset by reinstalling they apply to all worlds. This is due to Eco running a server for singleplayer, just like for multiplayer. You can go to /Steam/steamapps/common/Eco/Eco_Data/Server/Configs and open Disasters.eco and set the meteor to false.

Then restore a backup where the meteor didn't land yet (it probably hit when you loaded your world the first time after the config was no longer set to false) from /Steam/steamapps/common/Eco/Eco_Data/Server/Storage/Backups/ to the Storage folder and load that and you should be good again. (.db and .eco file)

Have your wife select "none" in the betas, that is the last version.

No, that is corrupted files, the server didn't update correctly. Try to remove the /Mods/ folder and do another Steam update.

We have identified the issue and a hotfix will be available in about four hours. Thanks for your help.

This workaround should work for you until the hotfix is out:
Go to /Steam/steamapps/common/Eco/Eco_Data/Server/Storage and rename the .db and .eco file of the savegame you are currently playing to Game.db and Game.eco (note the capitalization!) respectively.

Then start the server manually via the EcoServer.exe (in /Steam/steamapps/common/Eco/Eco_Data/Server/). You will then be able to start the game and in Your Worlds, at "LAN Servers" you should be able to join it.

Alternatively you can link your Steam account to an SLG account on https://play.eco, that will solve it without the steps above being necessary.

As a workaround you can try the following?

Go to /Steam/steamapps/common/Eco/Eco_Data/Server/Storage and rename the .db and .eco file of the savegame you are currently playing to Game.db and Game.eco (note the capitalization!) respectively.

Then start the server manually via the EcoServer.exe (in /Steam/steamapps/common/Eco/Eco_Data/Server/). You will then be able to start the game and in Your Worlds, at "LAN Servers" you should be able to join it.

Thank you. To all of you as well: Do you use Steam only accounts or have you linked your Steam accounts with an SLG account?

I'm really sorry for anyone affected, we are not able to reproduce the issue ourselves yet. Hence we need as much as information as any possible what is different for the affected people vs. the non-affected. Could you help us out with the following:

Do you start the game just normal via Steam? Have you set any parameters in the Properties (Right click)?

Do you start the world via ingame, e.g. "Your Worlds" -> Local Worlds -> Load? Or any other way? If you start the server via ingame means, can you try to manually start by executing /Steam/steamapps/common/Eco/Eco_Data/Server/EcoServer.exe, do you get the same issue then?