"connection failed"

[CoLS Firestar]

Connection failed. Connection timed out. Is the message I'm getting.

But I'm playing a SP game I was playing just minutes ago.

[SLG-Dennis]

Hello,
please contact our support at [e-mail], if the issue is persisting.

[Flashand]

hence the reason we asked for a single player non internet connection

[SLG-Dennis]

Has nothing to do with internet connection, but with corrupted game files. The singleplayer is a server and when it can't boot due to errors in the files, you can't connect to it, giving you a connection error. The real error is something entirely different.

[CoLS Firestar]

I deleted my mods folder, re-verified everything and the game worked again

[SLG-Dennis]

Great to hear, something broken there is the reason in most cases.

[Drageta]

Another way to get the game working in SP again is the following:

Uninstall Eco -> Delete the whole Eco folder inside of steamapps -> Install the game

It was the only way for me to start a new SP world. I don't know if I lost my old world in the process but I don't care anyway (didn't do much with that world).

[SLG-Dennis]

You did, you would need to backup the storage folder inside it before and restore it afterwards, but yes, that are ususally the steps needed to fix such issues, mostly corrupted files are the cause.

[Kallvin]

this "game" is not working due to this issue.

[Kallvin]

Manually going into the steamapp folder and deleting all progress has fixed the issue. This is the only time I have personally ever had to do this for a product on Steam. Before today, I had only started a world around launch of the game, and shortly left my world. Apparently this had corrupted my files somehow. Let me state that again, simply playing your game corrupted the files. Until the developers can verify future updates are not going to brick peoples servers I can not recommend this product. As much fun as I may have, this will merely be a single-player game for my personal experience, very disheartening.

[SLG-Dennis]

The solution to restore a backup was mentioned just a post above.

[Kallvin]

There was no backup to restore and you are side stepping the facts here.

[Kallvin]

Even a simple "let me have a peek at those files" would be reassuring but it appears your team really does not care about the state of your project.

Pending your actions from here I will be leaving a negative review as there is no further action needed on my part, I have witnessed enough.

[SLG-Dennis]

With all due respect, you pretty much posted a one-liner with no logfiles or explanation at all into someone elses thread that got a working solution, then stated you did delete all progress (how can i ask for deleted files?) in upset tone and when i hint at what could have been a possible solution before deleting the files, you blame me for that.

If you want me to look into your logs and save, i can of course do that, but that requires you actually still having the savefiles, which you stated that you don't.

Just for explanation: Eco uses a NoSQL Database to save a lot stuff while playing. Databases do not like it when you don't shutdown gracefully and tend break if that is done. Hence, we create backups every half an hour and even try to restore them automatically when a range of detectable faults are detected. There is nothing that could be done to avoid that currently, because using a different saving mechanic would implicate a heavy performance loss. We plan to optionally support SQL-Databases in the future that should be less prone to this, but still will have the same issue. Any savegame can break when there is a shutdown while saving in any game, just that Eco saves something every few seconds, while other games mostly do not.

I did totally not mean to be unhelpful, but in order to help i actually need savefiles, logs and a description of the issue. Best would be if that was done in your own thread, not as a side place in a already solved one. You can send all of that to [e-mail].