Is the map endless and are the resources depletable?

[Niy]

Just got the game wanting to know for the future ahead.

[tdb]

The map is not endless but is fairly large and varied. Resource nodes last forever.

[Suzaku]

The map is static and limited (though still quite large). All resources are unlimited except for trees, but you'll never cut them all down.

[Niy]

Thank you.

[XistenZ]

Originally posted by Suzaku:

The map is static and limited (though still quite large). All resources are unlimited except for trees, but you'll never cut them all down.

Somewhere in the world I can hear a "challenge accepted!"

[info]

Originally posted by XistenZ:

Originally posted by Suzaku:

The map is static and limited (though still quite large). All resources are unlimited except for trees, but you'll never cut them all down.

Somewhere in the world I can hear a "challenge accepted!"

I asked awhile back if anyone had cut down everything, seems like a thing to do really.

I also became aware that the way saves work is

OG Map + this tree gone, that tree gone, that powerslug harvested ect...

So the more interaction with the map the larger the save grows.

It seems odd to me to do it this way and I would really think there would be some sort of save compile at the end of each session to make a new loading map for the next go around.

[tdb]

Originally posted by info:

It seems odd to me to do it this way and I would really think there would be some sort of save compile at the end of each session to make a new loading map for the next go around.

So, you'd rather have the save file for a new game to be large, potentially even hundreds of megabytes, and gradually get smaller as the player removes trees (which I imagine doesn't really happen to a significant degree in most playthroughs)?

[info]

Originally posted by tdb:

Originally posted by info:

It seems odd to me to do it this way and I would really think there would be some sort of save compile at the end of each session to make a new loading map for the next go around.

So, you'd rather have the save file for a new game to be large, potentially even hundreds of megabytes, and gradually get smaller as the player removes trees (which I imagine doesn't really happen to a significant degree in most playthroughs)?

The starting map has everything and the save denotes what has been removed. What I suggested was creating a new starting map on exit by incorporating what has been removed and replacing the starting map which would be smaller with items removed and the save file would be back at a fresh start each time the game is launched.

[info]

It has been said by CSS that removing lots of trees and other items from the map can degrade performance.

[tdb]

Originally posted by info:

The starting map has everything and the save denotes what has been removed. What I suggested was creating a new starting map on exit by incorporating what has been removed and replacing the starting map which would be smaller with items removed and the save file would be back at a fresh start each time the game is launched.

You couldn't just replace the starting map, because if I decide to load an older save, or even one from a different playthrough altogether, I'd need to have the appropriate starting map for that save available. In my current playthrough I have over 100 saves, most of which have been made at the end of a play session, so that would be over 100 starting maps stored just for this playthrough. I couldn't find out how large the game's map file is, but I expect it to be many times larger than my save file, given how large the world is.

Originally posted by info:

It has been said by CSS that removing lots of trees and other items from the map can degrade performance.

Yeah, but saving every still existing tree and bush would be even worse, since there's a lot more of them.

[info]

Storage is cheap, why not have a map for each save?

[tdb]

Originally posted by info:

Storage is cheap, why not have a map for each save?

I would prefer to keep Steam Cloud support, thank you very much. My existing save files take 520 MB and there's 430 MB remaining.

I'm also pretty sure the performance degradation only concerns saving the game. There would have to be something really weird going on for removing trees to affect framerate in anyway.

[Eminence Front]

Originally posted by info:

Storage is cheap, why not have a map for each save?

As your build grows, the save stores can take around 20 seconds or more - with the auto-saves essentially "auto-pausing" your game while it works. Storage is cheap, but the time this takes is annoying. But understandable.

[Fenix]

Most Of the resources are infinite, the ones that really matter. The few that aren't there are other ways of making the same item that needs them, or are story related and you can't use ATM.

[apdsmith]

Originally posted by info:

Originally posted by tdb:

So, you'd rather have the save file for a new game to be large, potentially even hundreds of megabytes, and gradually get smaller as the player removes trees (which I imagine doesn't really happen to a significant degree in most playthroughs)?

The starting map has everything and the save denotes what has been removed. What I suggested was creating a new starting map on exit by incorporating what has been removed and replacing the starting map which would be smaller with items removed and the save file would be back at a fresh start each time the game is launched.

That'd probably land you with the worst-case performance all of the time, though, no?

[DB]

Anyone know if something like Foliage re-growth or farming/planting has been considered for the future at some point? Although you will never need anywhere close to them all for biomass it would be nice to replenish woodland if you wanted to