a multiplayer game of parenting and civilization building
You are not logged in.
Pages: 1
So, in this update, springs are 100 apart, which is fine.
BUT, there's a problem.
Obviously, they can't occur on arctic or desert, so that makes them less frequent than 100x100. That's expected.
But there's another thing that can block them: An existing entry in the map database for that spot.
The procedural map generation code, which puts springs on the grid, is only queried if there's nothing in the DB for that spot already.
Just because someone walks through a wild area, that's not necessarily enough to put all those tiles in the DB. Only changed tiles get put in. So, obviously, if someone moves stuff around, or interacts with a bush, or whatever, that will leave something in the DB.
But also, if the person sees moving animals, and those come alive, those will move around for a bit. They leave changed tiles in the DB as they do this.
So, if in the past (like last week), a bunch of animals moved around in an area and left changed tiles in the database, they would block some of those tiles from ever getting a spring after the update.
In testing on the main server, I've walk the fault lines many hundreds of tiles, even through spring-friendly biomes, without ever seeing a spring.
On my test server (with an empty DB), they occur every 100 tiles as they should.
So, this is causing Eves to be way more spread out than they should be, and also making it a pain to find other springs.
It seems like we may need a map wipe to fix this...
It would also be good for everyone to start back at (0,0) with all the changes, a bunch of Eves 100 tiles away from each other, etc.
Offline
Ok if you want to reset the map, please do it sooner than later.
I dont wanna play now if i know the map will be reset soon
Offline
Offline
Do it like an event, wipe days are fun days
Offline
Will be kicking off the wipe around noon pst today.
Offline
Pages: 1