SLG-Dennis

The room type has nothing to do with the tier level of the room, that is solely determined by what material it is made of.

It's the naturally generated surface, not water level.

We have not released any updates to the game since monday, did you play since then before?

In any case please send your logfiles after such freeze to [email protected], you can find how to get the logfiles here: https://github.com/StrangeLoopGames/EcoIssues/wiki/Getting-the-Eco-game-log-file

No, but I'm not able to reproduce, the first item freshly crafted after the module is taken out in a work order does no longer benefit from it, as with all subsequent ones. Can you provide additional details to [email protected] or on our bug tracker?

The avatars are also saved locally (although in AppData and the registry), but once you join a server with a specific avatar it will stay for the whole lifetime of that game and can only be changed at a dresser in-game, new avatars or changes made with the main menu do not apply to servers / games already joined.

Correct, you can edit it manually. For singleplayer we don't support any size other then default, though. That is only supported for the actual dedicated server.

There is Small, Medium and Large, but the preset doesn't do anything when changed in the config file, only when changing via the server ui. It only changes the size, with the following being Large and the maximum supported size.

"WorldWidth": 160,
"WorldLength": 160

Eco uses a local dedicated server for singleplayer, there is no cloud storage. To move your save game to a different computer you need to move the /Steam/steamapps/common/Eco/Eco_Data/Server/ folder, respectively at least the Configs and Storage folders within, if you don't use any mods.

Flux only spawns on worlds generated with Update 10 configs or later, you can use /give flax to just spawn some in and do the same for seeds to plant it yourself in zones that are habitable for it. If the server is started locally, the host will automatically have admin permissions.

It's one of the most used admin tools to enforce rules, which can include rules for taking from unclaimed property as well.

Originally posted by Dani: Join a server, take a pickaxe and give it a go.
Been on 3 different servers in the last week and have been mining for hours and hours ...
Mostly tiny "veins" here and there.
Maybe I have been unlucky and landed on servers where the algorithm wasn't doing that great.

There is developer commands that allow the clear the whole world or any amount of chunks from anything but ore, so we can easily adjust and test the distribution. Maybe the problem is the expectations of veins being always chunk sized, which they aren't. The requirement to use drills and have a lot of byproduct in mining is intended.

Originally posted by PajamaBanana:

Originally posted by Hatsikidee: Should be trackable if people take stuff

Sounds like a lot of extra code for no reason. Just claim your property or understand public property is owned by the public.

There is the "Chronicler" mod that allows admins to log actions.

Originally posted by FluffyPotato: How hard is it to find in grasslands? I haven't played in a long time and the last time I played iron was everywhere. I kinda hate how deserts look and I wanna play with just a few friends. Building the infrastructure to transport iron without access to it first seems very annoying.

Also is there any way to change how ore spawn is done now? I would prefer to make it spawn under mountains if that's possible.

The locations where ore spawns hasn't changed, even the amounts are still nearly the exact same - it is a sole change of distribution to make it available more spread out over the biomes and less of singular massive chunks. You can adjust ore spawn via WorldGenerator.eco, but ... Read more

Yes, server language and client language is different, that also enables you to add modifications server side with localization and change the name of recipes and basically anything server-side with simple measures. Things that are fully configurable / changeable / deletable on the server are served via it, not the client. It is nowhere an optimal implementation and that wasn't claimed anywhere either, but it does work as it was developed and is not a bug. It has advantages and disadvantages on many levels and we'll surely look into that again in the future, but for now it is working correctly.

You are talking about a different issue than OP, see here: https://steamcommunity.com/app/382310/discussions/4/4140564315468460733/

Not sure what you mean with "old" ore spawn method? We never used this one before.

This will be fixed in Hotfix 10.1.2 later today.