Downgrading a Minecraft world's version until it breaks

preview_player
Показать описание
Hey people

So today I decided to do an experiment...

As the title and thumbnail say I created a world in 1.17 and went down in versions, stopping at every major one. (for example 1.17 - 1.16 - 1.15 - 1.14-... and so on...)

What will happen to the world? Will the end still be beatable in the .. well end? How broken will the world be?

Well.. we're about to find out.

St0p scrolling and subscrib.
Рекомендации по теме
Комментарии
Автор

I remember back in 2018 when I converted my world to the snapshot of 1.14 and then it was so laggy and I tried going back but every structure disappeared and my inventory was still there, I still miss that world

iamgoldnn
Автор

minecraft world of theseus: if the seed changes and none of the same mobs are there anymore after multiple downgrades of the same world, is it even the same world

sweetaplle
Автор

Actually getting to seed zero is a really hard problem that was solved by some people reverse engineering the string to seed conversion. It's cool you found another way to get there!

james_wasson
Автор

plate tectonics changes the world alot when going back in time

TrinityCodex
Автор

1.2.1 most likely fixed it because 1.2.1 is one of the versions where the server isn't mixed with the client. 1.3 mixed the client and the server

smqfl
Автор

For each one that you got a complete new world is because the world save format was different. So technically every time you got a new world the older game could not see that a world still existed. Just the world folder could be seen. since a older game cannot read the new save formats. So now if you look in the region folder you will see 2 or 3 different formats rather than just the 1.

MrShourin
Автор

6:23 I personally call them chunk cliffs. Just because that’s what they are. Cliffs between chunks. Usually this is due to corruptions, or generating terrain in different versions. It’s neat, and they sometimes just happen in normal worlds and I don’t know why. It’s obvious when they happen in an ocean or when they destroy a structure.

Real_Moon-Moon
Автор

Seed 0 happens when you badly mess up your world to the point where it can be loaded, it’s just very very corrupted and Minecraft doesn’t want your pc to crash so it loads Seed 0. In newer versions, you can actually go to seed 0 without having to get your world corrupted or typing: "pollinating sandboxes" into the seed area

ZiaFyisco
Автор

Interesting experiment. I sadly had a ton of my old worlds from 2010-2018 being lost over time. I wish I'd still have them

SzaSzabiYT
Автор

6:38 That is caused becouse 1.2 and later use the "Anvil" save format, but Beta 1.3 all the way up to 1.1 use the "MCRegion" save format. That's why it says "Must be converted" in the save load menu

ignacyk
Автор

I accidentally logged onto my 1.18.2 creative testing world on 1.8 awhile back. I realized it before it completely loaded though and did alt + f4. All of the structures I had made before are gone and there is a checkerboard of chunk errors at spawn but it still works and is playable. It's really neat to look at although if I had done this to one of my survival worlds I would have been completely devastated.

keagaming
Автор

You should try that again but each time before downgrading, you change the version value in the level.dat of the map.

itsquadrus
Автор

I did something similar to this in a superflat world for an old version I always played on years ago. I'd get whatever OP enchants or stuff I wanted, and was free to explore the insane terrain. I think the steps I did were below: I tried to remember the best I can:

1) go to a older version from your current version (1.2.5 is the one I used a lot)
2) choose a super flat world and create it
3) load that Super Flat world in beta or something. After you die by suffocation, then
3) go back to the version you created the world with (in this example, 1.2.5.)
4) You'll see a normal world / flat world split

-Siknakaliux-II
Автор

6:19 ah, the classic chunk border. Usually they don’t crash your world, but that’s when old terrain is… y’know, updated.

JustWowNick
Автор

I used to do this in Pocket Edition, by changing apks (the update block is my favorite still) and using an app to change the seed of the world to a superflat, causing those chunk cliffs.

andheregoesmyname
Автор

you can see the game start looking nostalgic again at 1.8 > 1.2.1

hexateron
Автор

i once upgraded my world from 1.7.9 to 1.8 and it cleared my inventory

artiejay
Автор

Surprised this only has 44 views. Very high quality stuff. Subbed.

QuentacosIsMe
Автор

I played a Creative world in 1.9 but accidentally made a repeating command block at spawn that summoned an exponentially growing number of entities which crashed my game when I loaded the world. I got rid of it by downgrading to 1.8 (before repeating command blocks) then updating to 1.9 again. A couple of chunks near spawn were re-generated like they were from a different world.

Sabagegah
Автор

what i find cool is how seed 0 is similar in most of the versions

joda