I have two. My first world using Alpha 1.1.2 and the second one which is my main map hast been going on since Beta 1.3. I havent played Minecraft for 6 months but my Beta world is still going strong.
The reason for cut off worlds is this: The game comes across old worlds, the game is written to generate new worlds and doesn't know how to properly convert them in a way that makes it smooth so the game just puts a cut
a few things wrong with this: - skipping versions not on the launcher? whuh? there's like only one infdev version in the launcher and you are skipping over very important details by doing this. Why exactly wouldn't it make sense...? It's not like these versions are modded, they are official, it just that they haven't been archived in the launcher, and it doesn't even mean the devs don't support archiving them cuz wouldn't you know it, those versions are on the wiki. - skipping most versions before the official release is also stupid, you skipped from alpha all the way to beta 1.8 which was the preparation to release anyway so you essentially just skipped beta altogether. or how you said alpha looks way different from infdev but in reality that's just late alpha you've shown which is virtually the same as early beta. Infdev also had three entire phases you've skipped over. Please read about those versions next time. I wouldn't be typing this but oh god you treat release versions like versions and entire phases of the game before releases... also like versions? Overall, not the worst video but these things ticked me off so far that I actually commented, which I almost never do.
There is a glitch in 1.8 where ocean monuments could spawn then pre existing terrain if there was meant to be an ocean there in the current version. So if 1.8 ocean chunks where generated in an older version with desert for example, there is a chance an ocean monument would spawn and overuse all the terrain.
@@LennonsRetroTech yes, I know. But it won't try to smooth the transition from mountain to ocean. It will just place the monument in the mountain. Smothed transition was implemented in 1.18 where both new and old chunks would change from the world generator to meet in the middle to prevent chunk cliffs.
I vehemently disagree with your interpretation of “latest stable versions” Alpha 1.0.x, Alpha 1.1.x, Alpha 1.2.x, Beta 1.0.x, etc. (replace x with highest release number) ESPECIALLY since when you get to release versions you do this (mostly… there’s still a lazy cop-out skip going on with the early release versions). Otherwise, based solely on how you started, the latest stable release pattern as of this comment would be Alpha 1.2.6, Beta 1.8.1, 1.21, done.
Also, your interpretation of the world generation borders is equally as lazy, imho. Until VERY recently, world smoothing was NOT a thing and any changes to world generation was a straight line cut. Any sudden biome changes (such as the desert/swamp line) are the results of totally different versions, not poor biome interaction.
I did this once where I loaded a world in the oldest possible version, generated some new terrain, repeated the process with subsequent versions making a ripple effect of old to new terrain.
2b2t is not really a good way to see how updating affect the world, the 2b2t world is going through A LOT, etho's single player world would be probably better, even though he also played with the world a bit throughout the year
Because programming that is hard with the generation becoming more realistic and the old world not as but to make it more realistic he should of updated it version by version
Off topic here, but it's very cool seeing that you used the 10 years Realms anniversary map! I actually worked on it and it did make the whole video feel so good
While an aether dimension could be cool, I think it’d be awesome to see a dimension based on the wild and bizarre terrain that the game could generate through the various bugs and experiments done through the years Maybe with the saturated beta colours too
It feels like you don’t know a huge amount about Minecraft generation. Video is overall good though. For anyone wondering about the video’s premise: You can take a save from Infdev to the newest version (but the Infdev version you need isn’t in the launcher).
okay how the hell does this have 3.8k views? I went through this whole video thinking this was absolutely more like *380k* views,stick with it man. you'll end up doing a lot better if you keep this quality up,this was a good ass video.
he actually has channel in Russian, which has millions of subscribers and thousand of views. He is actually from Ukraine (living in polad). 😅 This is I guess his other channel which is in English. I guess it hasn't got really viral yet
Bro ur so good at translating @Nerkin. I have been watching him for quite a while(a couple years) and it still feels like it's his normal voice. Good job. (Btw I have seen a lot of english to russian translations, but it's the first time i saw russian to english lol)
ALOT of issues here Number 1 The Minecraft Launcher Is Missing ALOT of Version So Use BetaCraft Number 2 DONT use Beta 1.8 the beta minecraft community HATES b1.8 USE B1.7.3
only like 35% of people hate beta 1.8 so that’s not a good reason to skip it i think he should have used beta 1.7.3 because beta 1.8 and 1.0 have barely any difference generation wise besides strongholds and villages.
10:50 1.15 was NOT a minor update, very little features were added but they did basically remade the world generation engine, there were A LOT of changes behind the scenes!
@@ZaCloud-Animations___she-her там можно написать что угодно. Я тоже могу переименовать себя в неркина и написать что это официальный аккаунт. Тем не менее, мне уже в телеграм чате ответили на мой вопрос
Surprisingly when I realoaded a lot of chunks on my save so the bluemap overview could render them properly. I noticed that, the newish 1.18 terrain is trying to avoid „butter-knive cliffs“. This avoidance works surprisingly good with old alpha 1.2.6 terrain. Moderately well with. Everything up to beta 1.7 terrain und fails completely on beta 1.8 terrain. I had no newer terrain until I copied those chunks into a new world with 1.12 terrain but both parts are too distant to share a terrain border.
The reason the world keeps cutting off at almost every new version is because changing how the world generation is coded even a tiny bit causes it to change completely even on the same seed because random number generation is very chaotic. If you load new chunks on a version of the game that is different it will generate those chunks using the world generation of the new version and it will place that right next to the old chunks which causes the cutoff. This isn't really a bug, it's just that trying to make it look good would take too much effort. They have actually implemented something that should make it look better, but I haven't really seen it in action so I can't tell if it works nicely or not.
Really missed a lot of changes by skipping all the alpha, beta versions and just doing the "latest" because this is when the game was growing a picking up speed and experimental, every beta was different from the last
I have a private server v1.20.1, it has multiverse portals on it, that connects to multiple old maps my server ran. Oldest that plays perfectly is from Beta 1.5
Pretty neat, & I appreciate how indepth you went. But I'm a bit disappointed that you didn't go back to your original spawn at the end, to go full circle and really prove that your already existing start point really did survive the transitions intact. Kind of unsatisfying.
I miss my god seed where I was near swamp and had 3 diff mob spawners at spawn so close to the surface. I wonder what it would look like it was in new version.
Newer players being surprised about chunk border cliffs from updated worlds is... wow. Wasn't it only a couple years ago that 1.18's chunk blending between old and new chunks was, like... a cool and new feature? Do newer players not know that older updates usually caused chunk cliffs?? Also you skipped two entire phases of Minecraft. Alpha and Beta shouldn't be treated as single versions, especially their final versions which are more like prequels to the following development phase of the game... you used Alpha 1.2 (skipping the actual Alpha) and Beta 1.8 (skipping the actual Beta).
This is all actually happening in 2b2t cuz their world appears to be converted all the time the server updates we can see broken chunk due to its game updates
It would be interesting to have a world-save where the middle section is the oldest version of Minecraft able to be kept through converting worlds and then from there make a ring around each converted world of the next updates, loading new chunks in concentric circles, like tree rings! That would make for an interesting way to show off each versions generation and it's like a slice/picture of history :)
according to minecraft wiki: villages were added in beta 1.8, while villagers (as "testificates") were added in pre release 1.9, which then ended up being 1.0
Actually 1.17 was very big update that completely changed graphic and java version also allowing shaders without mods and fixing some bugs. Due to big changes more bugs apeared than were fixed and optimalization was so bad that on my older pc 1.17 runs in 30fps with massive lag spikes and TEN secound latency while 1.20 runs smooth
gotta love watching people who have done not even the slightest bit of research on old Minecraft (it is super easy, like, ridiculously easy, there is no excuse except pure laziness), try and make videos with old Minecraft and make themselves look like total morons in the process, don’t get me wrong, i LOVE that more people are trying old Minecraft, but dear god, if you’re just doing it to follow a trend, which i see many youtubers do it even though they clearly have zero interest or passion in it, at least try not to make it so blatantly obvious you’re just doing it for the trend
Next challenge use the oldest can save world version and save the world and put the old world to newest world literally don't put on old but just put on new litterelly
_beginning of video_ I'm literally expecting the most drastic and obvious world border glitch ever. Just flat terrain and then BOOM cherry blossom mountains.
![FendiDa Rappa - Clock Dat ft. Shamar Marco [Official Music Video]](http://i.ytimg.com/vi/3NBU8KHdxYY/mqdefault.jpg)
![OsamaSon - ik what you did last summer [Official Music Video]](http://i.ytimg.com/vi/4DIQDnu3mr4/mqdefault.jpg)
I imagine somewhere out there, there is a person that has been actively playing a single survival world since beta minecraft
There definitely is. For example Etho's single player lets play world has been going since beta 1.9 anyway.
Edit: Fixing obvious typo 1.19 ->1.9
@@NirateGoel beta 1.19?
@@theeduummpp Typo
@@NirateGoel ohh, well either way that's really cool! don't think I could ever have that kind of dedication
I have two. My first world using Alpha 1.1.2 and the second one which is my main map hast been going on since Beta 1.3. I havent played Minecraft for 6 months but my Beta world is still going strong.
The reason for cut off worlds is this: The game comes across old worlds, the game is written to generate new worlds and doesn't know how to properly convert them in a way that makes it smooth so the game just puts a cut
Yes
1.12.2 for example (which is one of the most modded versions) if you try to upgrade your world to lets say 1.19 That happens
@@marsmelon24_officialNo it doesn't, the transition would be smooth in that case because they added chunk smoothing to new chunks in 1.18
Infdev 20100327 is the oldest version that you can still run worlds in today without external editing tools. Luckily that version is not missing.
Nred🤓🤓🤓🤓🤓🤓
Why yes, I am one.@@NolanHOfficial
"Nred"
@@NolanHOfficialno ability to comprehend information?
@@skazzuie I'm not reading all of that
a few things wrong with this:
- skipping versions not on the launcher? whuh? there's like only one infdev version in the launcher and you are skipping over very important details by doing this. Why exactly wouldn't it make sense...? It's not like these versions are modded, they are official, it just that they haven't been archived in the launcher, and it doesn't even mean the devs don't support archiving them cuz wouldn't you know it, those versions are on the wiki.
- skipping most versions before the official release is also stupid, you skipped from alpha all the way to beta 1.8 which was the preparation to release anyway so you essentially just skipped beta altogether. or how you said alpha looks way different from infdev but in reality that's just late alpha you've shown which is virtually the same as early beta. Infdev also had three entire phases you've skipped over. Please read about those versions next time. I wouldn't be typing this but oh god you treat release versions like versions and entire phases of the game before releases... also like versions?
Overall, not the worst video but these things ticked me off so far that I actually commented, which I almost never do.
4:15 no. Prior to 1.18 no smoothing on chunk cliffs was done. The new non matching chunks are simply places next to the old.
There is a glitch in 1.8 where ocean monuments could spawn then pre existing terrain if there was meant to be an ocean there in the current version. So if 1.8 ocean chunks where generated in an older version with desert for example, there is a chance an ocean monument would spawn and overuse all the terrain.
@@LennonsRetroTech yes, I know. But it won't try to smooth the transition from mountain to ocean. It will just place the monument in the mountain. Smothed transition was implemented in 1.18 where both new and old chunks would change from the world generator to meet in the middle to prevent chunk cliffs.
1.8.1 beta is basically the same as 1.0 release.
Should've used 1.7.3 beta
Yeah, he pretty much skipped a whole phase
He also skipped a huge Alpha phase since alpha 1.2 is basically the same as beta 1.0 + 1.1
Should've played Aloha 1.1.2
Minecraft is basically the same as Minecraft.
Should've used Minecraft
@@piranhalettuce no different versions are way different
@user-gi4tw3ft4o the joke flew over your head.
I vehemently disagree with your interpretation of “latest stable versions”
Alpha 1.0.x, Alpha 1.1.x, Alpha 1.2.x, Beta 1.0.x, etc. (replace x with highest release number)
ESPECIALLY since when you get to release versions you do this (mostly… there’s still a lazy cop-out skip going on with the early release versions). Otherwise, based solely on how you started, the latest stable release pattern as of this comment would be Alpha 1.2.6, Beta 1.8.1, 1.21, done.
Also, your interpretation of the world generation borders is equally as lazy, imho.
Until VERY recently, world smoothing was NOT a thing and any changes to world generation was a straight line cut. Any sudden biome changes (such as the desert/swamp line) are the results of totally different versions, not poor biome interaction.
You should check out that wool tree in 1.21
I did this once where I loaded a world in the oldest possible version, generated some new terrain, repeated the process with subsequent versions making a ripple effect of old to new terrain.
Look at 2b2t, it has never reset, and it started in 2010.
Didn’t it reset a few months ago
@@EtherealSkino
@@EtherealSki no it updated it didn't reset
it has the same issues
2b2t is not really a good way to see how updating affect the world, the 2b2t world is going through A LOT, etho's single player world would be probably better, even though he also played with the world a bit throughout the year
i wonder though why do they not make a system that just blends the old generation with the new one
they did in 1.18, it didnt work that good though
@@animating_painswhat snapshot
Because programming that is hard with the generation becoming more realistic and the old world not as but to make it more realistic he should of updated it version by version
Have you tried to code in java?
Would be pretty pointless to make something that 99% of the community wouldn't use
4:15 this is called a chunk border. It is very common with older worlds that are played in newer version s
2:28 aplha, typo in the chapter too
yea
Probably bc the creators are russian
alpha!
Off topic here, but it's very cool seeing that you used the 10 years Realms anniversary map! I actually worked on it and it did make the whole video feel so good
That map was awesome!
While an aether dimension could be cool, I think it’d be awesome to see a dimension based on the wild and bizarre terrain that the game could generate through the various bugs and experiments done through the years
Maybe with the saturated beta colours too
It feels like you don’t know a huge amount about Minecraft generation. Video is overall good though.
For anyone wondering about the video’s premise: You can take a save from Infdev to the newest version (but the Infdev version you need isn’t in the launcher).
okay how the hell does this have 3.8k views? I went through this whole video thinking this was absolutely more like *380k* views,stick with it man. you'll end up doing a lot better if you keep this quality up,this was a good ass video.
he actually has channel in Russian, which has millions of subscribers and thousand of views. He is actually from Ukraine (living in polad). 😅 This is I guess his other channel which is in English. I guess it hasn't got really viral yet
this is not his video.
@@kaytenison2291Whose is it then?
@@kaytenison2291it is.
@@kaytenison2291Yes it is. This is an official translation
Bro ur so good at translating @Nerkin. I have been watching him for quite a while(a couple years) and it still feels like it's his normal voice. Good job. (Btw I have seen a lot of english to russian translations, but it's the first time i saw russian to english lol)
I think that's an official translation
@@TirailTirindeed, the channel description says it's official
ALOT of issues here Number 1 The Minecraft Launcher Is Missing ALOT of Version So Use BetaCraft Number 2 DONT use Beta 1.8 the beta minecraft community HATES b1.8 USE B1.7.3
only like 35% of people hate beta 1.8 so that’s not a good reason to skip it
i think he should have used beta 1.7.3 because beta 1.8 and 1.0 have barely any difference generation wise besides strongholds and villages.
9:24 It's not 1.12, it's 1.11. Nonetheless, great video ❤ I appreciate the spent time on doing this
10:50 1.15 was NOT a minor update, very little features were added but they did basically remade the world generation engine, there were A LOT of changes behind the scenes!
Интересно, это официальный канал неркина, куда он заказывает переводы, или какой-то рандомный чувак переводит его видосы?)
Это официальный перевод
Read this channel's description. :)
@@ZaCloud-Animations___she-her там можно написать что угодно. Я тоже могу переименовать себя в неркина и написать что это официальный аккаунт. Тем не менее, мне уже в телеграм чате ответили на мой вопрос
Неофф
10:01 farlands?
You make such good videos! You deserve way more subscribers than this!
so true
Surprisingly when I realoaded a lot of chunks on my save so the bluemap overview could render them properly. I noticed that, the newish 1.18 terrain is trying to avoid „butter-knive cliffs“.
This avoidance works surprisingly good with old alpha 1.2.6 terrain. Moderately well with. Everything up to beta 1.7 terrain und fails completely on beta 1.8 terrain. I had no newer terrain until I copied those chunks into a new world with 1.12 terrain but both parts are too distant to share a terrain border.
5:45 I’ve always found it weird where a swamp is just part of the ocean like that, like it feels weird lol
Yeah craft world I was trapped in alots of block inf hole and maintain being block a block massive and blocks
PLEASE give us a link to download this world onto our own games, I want to play on this world so bad!!!!
*The opposite would be more interesting, certain blocks that did not exist in previous versions would simply disapear.*
The reason the world keeps cutting off at almost every new version is because changing how the world generation is coded even a tiny bit causes it to change completely even on the same seed because random number generation is very chaotic.
If you load new chunks on a version of the game that is different it will generate those chunks using the world generation of the new version and it will place that right next to the old chunks which causes the cutoff.
This isn't really a bug, it's just that trying to make it look good would take too much effort. They have actually implemented something that should make it look better, but I haven't really seen it in action so I can't tell if it works nicely or not.
At exactly 2:35 you can see his file directory... it says MultiMC, which is a 3rd party application 😂
I once transferred a world from beta 1.8.2 to 1.20 but I couldn’t transfer a world from 1.15 to 1.20
Really missed a lot of changes by skipping all the alpha, beta versions and just doing the "latest" because this is when the game was growing a picking up speed and experimental, every beta was different from the last
11:26 once again, there were actual changes. did you even read what they changed? or do you work from memory and visible changes?
I have a private server v1.20.1, it has multiverse portals on it, that connects to multiple old maps my server ran. Oldest that plays perfectly is from Beta 1.5
Pretty neat, & I appreciate how indepth you went. But I'm a bit disappointed that you didn't go back to your original spawn at the end, to go full circle and really prove that your already existing start point really did survive the transitions intact. Kind of unsatisfying.
this also depends how much you jump between versions
You shoult try doing it with the new one to the old one
Hmmm,i have seen this skin somwhere but i cant remember where,the the channel name are also simmilar
i thought the update after 1.8 was the exploration update and im pretty sure 1.12 is called the world of color update
edit: ok nevermind he included it he just got confused a little
new drinking game: everytime he says "world" take a drink
😂😂😂
I miss my god seed where I was near swamp and had 3 diff mob spawners at spawn so close to the surface. I wonder what it would look like it was in new version.
Newer players being surprised about chunk border cliffs from updated worlds is... wow. Wasn't it only a couple years ago that 1.18's chunk blending between old and new chunks was, like... a cool and new feature? Do newer players not know that older updates usually caused chunk cliffs??
Also you skipped two entire phases of Minecraft. Alpha and Beta shouldn't be treated as single versions, especially their final versions which are more like prequels to the following development phase of the game... you used Alpha 1.2 (skipping the actual Alpha) and Beta 1.8 (skipping the actual Beta).
2:28 gotta love playing minecraft "aplha"
Fun fact: Only in 1.16.1 did they add any sort of 'good' transition between old and new terrain.
This is all actually happening in 2b2t cuz their world appears to be converted all the time the server updates we can see broken chunk due to its game updates
0:45 1.20.6 WTF
😂
2:27 Aplha
now generate a world in 1.21 and load it into all other previous versions to see how does stuff break
9:04 1.11, not 1.12.
It would be interesting to have a world-save where the middle section is the oldest version of Minecraft able to be kept through converting worlds and then from there make a ring around each converted world of the next updates, loading new chunks in concentric circles, like tree rings! That would make for an interesting way to show off each versions generation and it's like a slice/picture of history :)
you should learn how to make mods that sounds cool
cool video, should've used alpha 1.1 then 1.7.3
2:28 typo
according to minecraft wiki:
villages were added in beta 1.8, while villagers (as "testificates") were added in pre release 1.9, which then ended up being 1.0
I LOVE CHUNK ERRORS!!!
Actually 1.17 was very big update that completely changed graphic and java version also allowing shaders without mods and fixing some bugs. Due to big changes more bugs apeared than were fixed and optimalization was so bad that on my older pc 1.17 runs in 30fps with massive lag spikes and TEN secound latency while 1.20 runs smooth
I wonder what if you load a new words in the lowest Minecraft version?
You can't due to there being only 2 blocks in the old version, grass and cobblestone, in the newest version, 1.21 there is about... over 1000 blocks
No one wonders this since everyone has does this before.
1:03 you can save by pressing enter in your key oard
THE APHLA VERSION 💀
pre classic worlds are saved in AppData\Roaming\.minecraft as level.dat
ahh yeah the good old "Aphla"
gotta love watching people who have done not even the slightest bit of research on old Minecraft (it is super easy, like, ridiculously easy, there is no excuse except pure laziness), try and make videos with old Minecraft and make themselves look like total morons in the process, don’t get me wrong, i LOVE that more people are trying old Minecraft, but dear god, if you’re just doing it to follow a trend, which i see many youtubers do it even though they clearly have zero interest or passion in it, at least try not to make it so blatantly obvious you’re just doing it for the trend
Did you skip like the entirety of the damn pre-release stage of Minecraft?
Welp I'm sorry it's a dislike
2:28 aplha and not alpha
Now import the newest minecraft world into the oldest minecraft version /jk
I loaded my 1.17 world into 1.20 and the blossom trees were glitching out and some more like my build was ruined because of the blossom treesl
Im starting a minecraft mod review channel. How do I do the block drop effect at 12:43 & how did you make the minecraft animation played after it
whyd you say 1.12 twice, 1.11 was the exploration update
Wow I didn’t know this was translated to english from russian
Next challenge use the oldest can save world version and save the world and put the old world to newest world literally don't put on old but just put on new litterelly
2:29 "aplha" :P
THEY'RE CALLED CHUNKS NOT TERRITORY!!!!
however call it how you want
2:28 “APLHA” ???
Literally unwatchable lol
Why are so many weirdos overreacting in the comments? Get a life bro, a simple spelling mistake isn’t gonna be the end of you
@@a1m..
No, this egregious mistake cannot be overlooked
/s
i love mc aplha
old.exe -> new.exe??? (minecraft runs in a jar?)
dude this is way more boring than putting a early infdev world into the newest 1.21 update
I'm reaching out for your prayers and healing energy. Please keep me in your thoughts.
Ooh yes I love Aplha Minecraft
2:27 I sure do love me some Aplha Minecraft
2:28 aplha
Hey Transfer The world into The 1.21Update, The Trial Chambers
Would've atleast expected to see screenshot comparisons at the end of specific locations showing how it changed...
Oh that’s a really good idea, I didn’t think about that
etho have a world from 1.0 that has actually been played in for years.
has bro only 844 subs? this content is good af
It’s the new English channel of a Russian youtuber
Bro you made one mistake in your title, Minecraft uses .jar not .exe
man i miss the lite version
i really hate your limted knowledge on technology.
i was wondering that yesterday, im guess im lucky lmao
you misspelled "alpha" as "aplha"
1:15 The version in the official website is actually a recreation in HTML5, and a bad recreation at that.
Wow, didn't know that you also have an english chanel
3:06 what is that Russian video🤣
here before 900 subs and before this channel gets 1m subs
😂 I hope so
_beginning of video_ I'm literally expecting the most drastic and obvious world border glitch ever. Just flat terrain and then BOOM cherry blossom mountains.
2:27 Horrifyingly embarassing
What are you trying to? Do you want to make a video to see?
bro this is so underrated 💀💀💀
bro this is stolen💀💀💀
@@BendiCrazyGD how
2:29 i love video game aplhas ❤️
7:53 this was actually a well known bug in 1.7, i remember encountering these on my 1.7 worlds thinking it was herobrine lol!