[LVS] Revert to 1.12.2! (We're doing it!)

[Zedwick]

We are reverting the world TODAY! (Monday 23rd July)

Unfortunately it seems Mojang may have rushed 1.13 out of the door, leaving us with some major issues with the world upgrade on LVS. I supose I may also be guilty of rushing LVS to 1.13; Though I did do a test upgrade in a small section of the world which didn't show any signs of these issues, and still does not in the current world, I was expecting something like this to happen and should have been a little more cautious as I had promised to be before 1.13's release.

There have been reports of chunks being completely regenerated in 1.13 on LVS, and Lady has confirmed large sections of the world seemingly not loading or being missing. There is an ongoing topic for these issues here: viewtopic.php?f=5&t=2923

Though downgrading would cause those of you who have been playing over the last couple of days to lose your progress, sticking with 1.13 would surely mean the loss of years of progress across the world(s).

I would like to hear your thoughts. Should we go back to 1.12.2, reverting to a backup taken before the upgrade, and wait for Mojang to release a future 1.13.X version which resolves these issues? Or should we stick with 1.13 and let the lost builds remain lost?

I would also point out that you may have seen small sections of 1.13 content appearing in older oceans, this is no doubt due to the odd chunk being regenerated in 1.13. If Mojang do fix the upgrade process to prevent regenerating random chunks, the smattering of sea grass would not appear when we next decide to upgrade the world to the 1.13+ format.

[ABParadigm]

I believe... given the incredibly severe damage to the world... that it would be best to revert back. I understand you do not necessarily need my reasoning, but...

I know many folks have essentially had their builds painted out of existence, and though I want to be wielding a trident, with turtle eggs in hand, it would be selfish to deny these folks who lost their builds what they worked tirelessly on for some time. We will eventually get the update, and Zedwick will find fixes to things that need fixes in time, even if Mojang for some reason does not. I think it best to turn back time, and see what happens in the future.

[Earthcow289]

Hello all, this is a bummer about 1.13 messing up the world. My build did not get messed up. I would be devastated if it did.
That would be great to reset back to help those people. Let's do it.

-EarthCow

[OffLuffy]

I haven't really been on for long, but I'd also think a reversion would be the best course. Mostly because maintaining your map history has seemingly been a major aspect of the server, and those chunk issues seem a threat to that.

On a more wishful thinking note, it'd be neat if a script could swap out the new chunks that were generated in 1.13 with the old chunks from the 1.12.2 backup if they existed. For when the map upgrade is fixed of course. I can't see immediately why that wouldn't work, but not helpful until the issue is fixed. Granted, unless there's a timestamp for when those chunks were generated, then it would still effectively revert the map to 1.12.2.

[LadyBountiful]

As such a large part of the world is affected, I think it would be best to return to 1.12.2 . We can still have fun all over again when 1.13 returns. I have voted, hope you all have too. This needs to be done soon, like today.

[Sneeze_Attack]

This also gives you more time to test some of your ideas Zed, just in case they screw something up as well. Although I love the features of 1.13, it seems too unstable and incompatible with 1.12 worlds. I personally think that there should be a new LVS for those like me who'd love to play a proper 1.13 world on Zedwork, but that's me.

[Zedwick]

On a more wishful thinking note, it'd be neat if a script could swap out the new chunks that were generated in 1.13 with the old chunks from the 1.12.2 backup if they existed. For when the map upgrade is fixed of course. I can't see immediately why that wouldn't work, but not helpful until the issue is fixed. Granted, unless there's a timestamp for when those chunks were generated, then it would still effectively revert the map to 1.12.2.

I took a backup immediately after I upgraded the world, before players roamed it and in theory generated the missing chunks (if that is how it worked). So, in theory, I could write a script to compare the before and after backups to identify which chunks were erased. However, please understand that the 1.12.2 world and the 1.13 world are different world formats. It would not be a simple case of copy&paste one chunk from one world file into the other. I would essentially be writing my own world upgrade script, and aiming to do it better than Mojang. Not an entirely realistic expectation, really. Though I would certainly give it a go if we were to stick with 1.13, it is very unlikely I would ever complete the script and patch up the holes in the existing world.

[Dax23333]

I have thought about this a fair bit now, and think it would be better roll back until the world can be converted.

I am faced with the choice of losing 3/4 of the land area of my base, or lose a few hours of fishing and beach ruining. Pretty clear choice to me.

Unfortunately I don't really trust mojang to fix this.

[OffLuffy]

please understand that the 1.12.2 world and the 1.13 world are different world formats. It would not be a simple case of copy&paste one chunk from one world file into the other. I would essentially be writing my own world upgrade script, and aiming to do it better than Mojang..

Yeah, I had an issue where I had built some nice stuff, and neglected to backup before trying Spigot 1.13-pre7, and reverted to 1.12.2 after a crash and it deleted everything. I definitely get that, lmao. I figured that the server would handle re-converting the chunks that were imported from 1.12.2, hence why it'd only be helpful if Mojang's upgrader was funcitonal

[Zedwick]

I figured that the server would handle re-converting the chunks that were imported from 1.12.2, hence why it'd only be helpful if Mojang's upgrader was funcitonal

Right, if we stayed in 1.13, once 1.13.1 rolls around with a fixed world upgrade, I upgrade separately from the 1.12.2 backup and try to copy&paste from the temp world? The other consideration is: what if people build in the chunks that were regenerated, and once again lose their work all over again? And that would be maybe a month of building or more too.