Factorio Forums

• Changes
  • Server started with --start-server-load-scenario will now save to saves/<scenario name> upon exit.
  • Multiplayer usernames can only consist of letters, numbers and -_. characters.
• Bugfixes
  • Possible fix for a server not responding error.

Use the automatic updater if you can (check experimental updates in other settings) or download full installation at http://www.factorio.com/download/experimental.

Possible fix for a server not responding error.

Link?

Multiplayer usernames can only consist of letters, numbers and -_. characters

this, this is good

FactorioBot wrote:

• Changes
  • Server started with --start-server-load-scenario will now save to saves/<scenario name> upon exit.

I was having an issue with this even when I wasn't using a scenario. While just trying to load a normal save with --start-server it would give an error saying that "--start-server" can't be used. Will this fix that as well even if I'm using a normal save and not scenario?

Xterminator wrote:

FactorioBot wrote:

• Changes
  • Server started with --start-server-load-scenario will now save to saves/<scenario name> upon exit.

I was having an issue with this even when I wasn't using a scenario. While just trying to load a normal save with --start-server it would give an error saying that "--start-server" can't be used. Will this fix that as well even if I'm using a normal save and not scenario?

it fixes that yes.

new problem. i wasn't able to download the map on my localhost server with 0.14.11 Win64

Chocolatetthunder wrote:Possible fix for a server not responding error.
Link?

In some situations everyone connected to a server would see "Server not responding". It looks like a network issue but is in fact factorio freezing. We experienced this during the massive multiplayer test stream.

The server-settings.example.json still has `verify_user_identity` in it. Is it safe to still use that name or must it be renamed to `require_user_verification`?

rfvgyhn wrote:The server-settings.example.json still has `verify_user_identity` in it. Is it safe to still use that name or must it be renamed to `require_user_verification`?

My server did not recognize the verify_user_identity false statement. The new parameter works though.

rfvgyhn wrote:The server-settings.example.json still has `verify_user_identity` in it. Is it safe to still use that name or must it be renamed to `require_user_verification`?

Yes, I fixed it, but too late, so it will be in the next version.

Updated - but I needed to enter username and password. None of the earlier updates required that. I think I had to enter it once and that was it (ages ago - but I am not sure) - and for .14.11 I was asked again.