#Chunk reset in the middle of the base
61 messages · Page 1 of 1 (latest)
@hallow ivy <@&188648556578603010> don't know whether you receive notifications from this channel, sorry if you already got it.
Meanwhile the amount of backups that still contain uncorrupted chunk gradually decreases. Do I get to receive at least an answer if not help?
i'll see what i can do this evening
Meanwhile another chunk got corrupted. What happens?
your base has ghostloading
check your chunkloading system
for the rollback i need a time (gmt+1 format) at which it was still not rolled back
Ok. About 14.12.23 10:00 GMT+1 I've logged off, everything was ok.
#chatepsilon message
I'm not familiar with "ghostloading" term, what should I avoid? The base has personal chunkloaders in three 3x3 areas, powered by shop coins.
There's also old base in overworld that's loaded the same way, I often go back and forth between them via teleposers. Main base teleposers are not chunkloaded.
your chunk are kept in memory while they shouldn't
and this can causes situation in which the chunk is badly used, corrupting it
So is it countered by replacing chunkloaders to passive? Or logging off somewhere else, but not on main base?
I've done a quick search in Discord history, and found you said its AE2's fault. Probably can't simplify that at this point...
Or maybe cutting off ME power before logging off?
So boubou stopped answering whatsoever. Anyone else up to help or tell me to fuck off?
what's your dim?
mars? also remember that it is a public dim, therefore, if there is an oregen update, we will need to wipe it
while we can move small outposts such as a miner or a pump, we will not migrate a whole base
Mars is correct.
I've read about server policy regarding bases in different dimensions and was willing to take the (low) risks of (sudden) worldgen update and move it myself.
Now, having faced 2 chunk resets in short period of time, I'm willing to move the base to persdim when / if it would be restored.
@graceful hare should be rolled back. Tell me if it was not enough.
Everything was ok when you've said it was rolled back.
Now one of those two chunks had reset again.
Maybe there are conditions that let this bug reproduce more often than usual, so if someone is interested in debugging this - you've got a test site now.
Or, if no one is interested, I'm going to tear down everything and move.
@graceful hare i rolled it back again, check your chunkloading system, and ideally move into your personal dim. Merry Christmas!
Ok, I will dismantle everything next time I'm on and move probably during holidays.
Ty, boubou, have a happy NY.
...sigh... Either someone played with my base in the meantime, or the reset happens when the chunk loads, not saves. Happens with awesome regularity, I'd say, its quite an opportunity to find and fix rare bug with severe consequences.
Had no chance to even start disassembling anything.
Am going to start moving what I can, please let me finish with that.
we will not try to debug this, it is probably an interaction with a poorly chunkloaded area and several mods. All i can is to offer you a rollback once again. And i'm pretty sure it's caused by some galacticraft shenanigans, because there the empty blocks are not quite empty.
So tell me from when i should restore in GMT +1
Please don't restore it yet. Right after you do this, something happens and it resets immediately or almost so. Let me move what I can first. Also, you restore the entire base, so all my precautions with removing chunkloaders and disabling ME go elsewhere.
i can't do this. The rollback will just restore the rest of the base, allowing you to dupe easily. Either you don't move stuff and you get the rollback, or you say goodbye to what was in your reset chunks
So I didn't earn a shit of trust in two years? Never tried to tierskip, dupe, grief, did write some articles for wiki, took care to keep the turbine calc updated? Just hadn't talked in the discord as much as those who earned that?
Then restore just the chunk that needs it after I move everything else. Or it might reset again and more before I finish.
Fine, go on with rollback then, no machines were moved yet.
But if it resets again before I finish, what will you do?
it wont if properly chunkloaded
I don't think you can guarantee something is "properly" chunkloaded. This "properly" part has no strict definition to follow.
Like "you do this, you never get resets"
the reset only happens on chunkreloading. If you loaded it in memory without it rolling back, if it stays in memory, it won't change. So if you load it properly, you have at least up to until next reboot to move stuff. Given you always have the same chunk reset, i guess moving what's in those chunks won't take you more than 15 mins.
So if you go in another dim, and come back, and see it reset itself, then your chunkloading grid is not working
i have a lot of experience in chunk resets, 4 as a player, 3 as an admin. And it's always caused by improper chunkloading, forcing the game to load ghost chunks in memory
I've logged in first time today after you restored this base. First thing I see is chunk had reset again. So I had no opportunity to do anything, and it probably was not loaded by anyone before my logon. Do you have an explanation for that?
No. Rollback had properly restored the chunk that was reset that second time. This was another one, that was on the first attempt.
Assline. luv mixer with maybe 30-40 alloy recipes.
you'll have to redo the patterning
Since unplanned moving will already cost me weeks, I guess a day or two of small things don't matter. Just assline then, with 16x data hatch please.
will do in 15 mins
done
Controller is like about 1% of assline's cost.
full one?
Like in questbook. 11 long.
Wish me enough patience to restore all this, so it wasn't for nothing, I guess...
Thank you anyways.
you should watch your attitude tho, i didn't like it, and next time, if you see a failed rollback, don't assume it just reset when you join, tell me directly i failed the rollback
If I see that the chunk that reset is not the one that you tried to restore (and successfully restored), I say so, because its the empirical fact. So the only plausible variant is backup succeeded AND another chunk was reset on load.
Or thats how it was in the backup itself.