Make sure to subscribe to help me reach 500k! Join the discord - discord.gg/WGc9UNM

I think if I remember correctly ender chests when first added were available to access with anyone on a server. So instead of having a personal chest that only you could access, it acted as a community chest.

There was another thing separating client and server internally caused that modder Shivaxi pointed out a year ago - taking damage used to cause your screen to 'flinch' away from the direction an attack came from. Since the client and server were separated processes, all damage assumes a single default 'flinch' direction. Mojang said they weren't going to fix it, but have indicated they are reconsidering it since modders have shown ways to fix it easily. (Also the experimental combat update is still in the works and would be perfect to fit this in when they think it's ready.)

Placing stairs upside down was added in 1.2 but it was only possible if you placed the stair from the bottom of a block. 1.3 changed this so you can place stairs upside down from the side of a block too. This is also for slabs as well.

As someone who has dealt with the technical sides of Minecraft a lot, I think this client-server separation is incredibly useful and a very great decision on the behalf of developers. People might naturally (and rightfully) assume, that running a server for a single-player game makes no sense and just makes everything run worse, but in reality it allows for server and client lag to be separated. For example, when generating new chunks, your entire game doesn't freeze, and instead you can still keep moving around with a smooth fps on the client while the server is doing the work for you. This becomes even more important for things such as complex redstone machinery, where in the past your FPS would drop down to single-digits, but now only the TPS is affected and you can continue playing the game at a very smooth frame rate.

1.3.1 also broke Forge (Mod-Loader). It took until Minecraft 1.4.2 for a stable Forge version. And while this does mean that there was a "dark age" for mods - in the end it improved things. Now almost all mods are multiplayer compatible - which was not a common thing in 1.2.5.

9:02 that is not ping to your internal server. Ping is the time packet took to travel, which in case of local server is almost always instant or less than 1ms. What you're showing here is how long game tick took to process on the internal server.

The internal server also meant 1 really cool thing: all mods from that point forward would need to support multiplayer, since it technically was always multiplayer, even on singleplayer worlds.

I modded Minecraft at the time and there used to be 3 different versions of Minecraft code. You have single player, multiplayer client, and multiplayer server. It was a massive undertaking for modders to support both single player and multiplayer because you needed to make 3 (or 2 if it is only graphical) separate versions of your code. This meant more work to support both but it also made it easier to enter the modding scene. You can start learning with single player and get predictable results before working on complex (and unpredictable because of the issues mentioned in the video) multiplayer versions.

I think it would be interesting to have a series like this documenting major updates and what people's reaction to them were at the time like this video

Slight correction. At 9:00 the "integrated server @ x ms" is called the players ping. It rather is the MSPT or milliseconds per tick value, which indicates how long a single tick takes. If this value exceeds 50, the 20 TPS or ticks per second can not be kept up.

This update also completely broke damage tilting! Nowadays whenever you get hurt, your screen tilts in the same direction every time, but prior to this update it would always tilt relative to what hurt you. 10 years and they still haven't fixed this!

Fun Fact: The reason Ruby's weren't added was because a Mojang dev was colorblind and couldn't tell the difference between Redstone Ore and Ruby Ore very easily.

I’m honestly surprised that you’re not at 500k yet, you deserve it man, keep up the great work!

Oh my god. It finally happened, a bigger content creator made a video about this issue. I thought I'd never see the day come. This issue has been in my brain for over 2 years now, and every time, I just chalked it up to being the fact that my pc was bad. Fun fact: my pc isn't bad. This video was like you read my mind. Everything I thought about this issue was basically said in this video. This issue really does need to be fixed. The elytra can't be used properly in singleplayer because chunks half the time won't load in front of or behind you, and once they do load, the mob and block lag is unbearable. Its kinda the same for starting a new world. You can't mine anything for like 30 seconds before it functions smoothly, not to mention delayed damaged and fire tick. I actually lost a hardcore world to this issue where I threw an ender pearl in the end. It lagged for a second, then didn't get an upward trajectory, it just instantly got a down trajectory and hit the side causing me to fall into the void. I will admit to cheating the world back in this one though as I saw that it was extremely unfair and was technically a "not the players fault" situation. This issue needs to be fixed ASAP, and I think Mojang should maybe put an update or two on hold to focus on the really important issues under the hood.

One interesting bug caused by the "Open to LAN" feature that not many people know is the animation for taking damage being broken. Before 1.3, when you'd get hurt your screen would tilt towards the direction from which you took the damage. However, after 1.3 the internal server would communicate the incorrect player position to the client side, making it so your screen would always tilt to the left. The saddest part is that it is a pretty simple thing to fix, but I guess Mojang and even us forgot about it because of all the other major issues.

I'm genuinely so confused how you manage to release videos so frequently, so much quality in such a short time. Thanks for making my days with your content. Good luck in future(hope you get to 500k soon)!

I remember before the 1.3.1 update. Man, I feel so old now as I realize that their are some kids playing this game today that are young enough to not even be alive for that. Edit: The old creative inventory that was one long list was the worst btw. Villager trading was the feature I remember wanting the most because I had a survival world in a superflat and that would become so helpful.

As a dedicated server host it pains me to know that even in singleplayer I cannot escape the hell that it is minecraft server hosting. The pain increases every update, and with more and more content updates I can hear my machines start to cry.

5:20 He went from "how do I port forward" to "fuck it, im playing hypixel"

One of the greatest reasons for syncing the Multiplayer version and Singleplayer was bug consistancy. Mojang over had to fix bugs double, not to mention that sometimes features would just not work on one version, for the longest time the Nether was singleplayer only. overall sure, it sucks to have multiplayer bugs creep into singleplayer, but in the end we got less bugs in general.

gotta love when u crash due to "internal server error"

I seriously hated this update, more so than 1.9. It broke the game so badly, plus the snapshots made me think we weren't going to be able to pause in singleplayer ever again. The mobs were so laggy, all multiplayer bugs were brought to singleplayer, and most singleplayer only bugs were gone. I'm so glad at least I know I'm not the only one who agrees that this update was hot garbage, despite the useful gameplay features.

I remember referring to Minecraft 1.3 as the "sound update" for a long time because the first thing I noticed upon updating from 1.2.5 was the change in the sound effects XD

Dude, this video brought so much nostalgia, this was the time I started playing Minecraft on SMP, I pretty much started playing on 1.2.5 and seeing that cluttered creative menu just flodded all the memories back. I really enjoyed it.

im so glad someone is finally talking about this. i remmeber this update vividly and how freaking annoying it was server lagging in a singleplayer world

The seperstion of client and server is pretty helpful for modders as you make your mods automatically multiplayer compatible, which otherwise would require 2 seperate mod versions

The only thing worse than Dream Stan’s…. Chunk errors.

There is an article on the Minecraft wiki titled "Java Edition 1.3.1/List of broken features" which I highly recommend reading. It's insane what things broke and were never fixed

this brings me back, i remember watching all of the snapshots back in middle school and being hyped for 1.3.1

i was under the impression that the internal server was like a multiplayer server but hosted directly on your device, the same machine running the client? i figured that this is what made "offline mode" possible?

There was a feature implemented then immediately broken by 1.3 The camera tilt from being hit was supposed to be based on where from you were hit, but that data wasn't sent in the server version so it only tilts to the left

1.3 was like a 1.9 or 1.13: a really good update in paper being clogged down by a single really big issue/feature. 1.3 was the internal server, 1.9 was the combat changes and 1.13 was the server performance. Why is it semi common? Edit: 1.3 > 1.9... 1.13 > 1.19...? I have a bad feeling there is going to be something inconvenient happening on 1.19...

I remember playing minecraft 1.2.5 with my friend in his house, we were playing in server but suddently his minecraft crashed (normal) an then when he started again it was on 1.3.1, but we did not know why his minecraft looks so different, bc he didint notice the update, an the when we noticed we were excited about the new things in

Your videos are so good! Perfect balance of information and entertainment, love seeing your videos pop up in my notifs!

And you know how this could be solved easily? Making every world you create a non-internal server world by default and then allowing you to change it to an internal server through a game rule or world settings. Means you still get the Open to LAN option if you want it, and if you don't you get a less laggy world

Fairly certain 1.3 also changed mob drops with food, beforehand, when you killed a pig or cow, there was a large chance it just dropped nothing. Those were the days lmao

The work you do is so interesting and must take a lot of work. Let’s get too 500k !

It was a great update, Because trading and desert temples, and jungle biome was introduced, Would say that I'll play it for the classic experience

9:02 i believe thats not the ping, thats the mspt: the time spent in milliseconds on how long calculating the current tick took. if it goes above 50 (because 1 second is 20 ticks and 1/20th of a second is 50ms), you will start to feel lag, because minecraft cant run at 20 tps anymore

I can't even fathom hiw many times I was building I placed a block and it disappeared almost immediately after being placed

Omg, I remember villagers just chilling and not doing anything. I was really excited somehow when they added villager trading.

Oh yeah, I remember this happening. It was the second, after the time Mojang upgraded LWJGL for the first time in the 1.4 times, time where I ended up being unable to play the game for months, until some updates later the "internal server" performance were brought somewhat to the playable state. Truly awful, also yeah, all the bugs that crept from the multiplayer to the singleplayer, some small stuff like portal sounds and death screen... angle thing, to stuff like block desync. I generally play on SMP now, even if I play a "singleplayer" world, because even on moderately modern rig I still find that the singleplayer can bug in an unexpected way that just dont happen if I play on a machine that dont need to worry about both client and "server" at the same time...

I think network optimisation, lag smoothing and general performance optimisation mods can smooth this out (just speculation). I havn't experience these issues much at all even on a garage computer.

I guess the reason for this might be due to how much extra work would have been introduced if single player was left how it was originally. With the way that it is now, Mojang only has do develop a server software, and a multiplayer client. Before single player was hosted on an internal server, Mojang would have to update the Single player client, Multiplayer client as well as the Server software. So in short, although the switch introduced some major bugs, it made it much simpler and less time consuming to add features to Minecraft.

7:04 Me at 1 am watching KZfaq videos and looking at the time:

in 2009 at the ripe age of 9 my brother, then 8, and i got a laptop to share from my dad's work. fell in love with it and pc gaming, the next year my brother got his own so we didnt have to share. soon after we discovered Minecraft and have been playing ever since. 1.3 was an absolute game changer, we'd be sat on the sofas in our own little worlds for hours everyday, but now there was a bridge between them. it was fantastic.

Not only did changing the way SinglePlayer works cause many bugs but the reason for changing it doesn’t even work all the time! Since 1.8.9 or some other version, LAN worlds fail to show up in the multiplayer list. I don’t know which bug report it was from but this is an open problem.

I remember being unable to play on several major versions because of the integrated server thing. I kept breaking blocks and they ended up returning and I was unable to even mine 1 block after 3 attempts.

I remember trolling my friends on multi on that version by flying using sand xD If you put a sand block and put another sand bloc below the first one while it was falling, it would glitch out and both stay mid air and return to your eq, so long you did not leave the chunk you could have walked on it while no other players could even see the blocks.

That open to LAN was a legendary update for me as a kid who couldn't port forward. Made connecting through hamachi way easier and actually possible.

the internal server was the best thing that came out as during that time as that time with the tools like Hamachi allows you to play with friends without required knowledge on how to portforward now 95% of the time I don't use the open to lan option as I am one of the few player that finally figure out how to portforward.. it is rather easy if you can figure out how to configure router and your PC internal IP

I think 1.3 is my favourite non-modern version of the game. It feels a little bit harder in terms of survival but still has that release polish

I remember trying the first 1.3 snapshot to introduce the internal server and seeing that the game would continue to run while on the pause menu. Feared that it would stay like that but fortunately it got fixed soon after. Although it introduced a lot of bugs it simplified development, which is why I don't think mojang is going to ever change that, even less likely now with problems being rare.

Nostalgia... I started with version 1.2.5 and 1.3 was my first update. Time flies...

I think the fact that infested stone/cobblestone comes up first has to do with the hierarchy of letters. In coding, characters are depicted using encoding, So (Blank Character) < A < B < C < D etc.

It is insanely hard to believe I was around to see this update happen

I still remember using _SinglePlayerCommands_ in 1.2.5 all the time and the pain of having to download separate mods for single- and multiplayer, with some mods never even receiving a multiplayer version. This became even worse if you wanted to use plugins, too, as you had to find an MCPC port of the mod to use on Bukkit servers, which were even rarer... Then, 1.3.2, or more accurate 1.4.7 happened and all mods were "universal" now, Bukkit wasn't needed anymore and you could just play modded however you liked - and SPC was gone, replaced by standard internal server commands and other cheating methods.

Omg, this was the first version of Minecraft that I ever played when I bought the game!

It's also annoying because after you've opened it to LAN whenever you hit 'esc' because your mum is telling you to do the dishes the game doesn't pause, because it's a server now and there's no changing back - unopening from LAN

I wish I never knew about LAN, whenever I get mad or rage or bad I use it and then I realized that I just ruined my survival world

Really nice video! Jeff!

I remember a popular youtuber being mad about the achievement level requirement buffs, because grinding for hours is definently better than only needing 30 levels, and then like 5(?) more each time you enchant something

To fix the internal server problem can be done by having the single player button not open an internal server and have an "Open World" button in the Multiplayer menu to open one of your worlds as a server for LAN. But this could have bad effects on modding again.

so i havent watched much of the video but i have heard of this before. so my question is that is the internal server running even when its not open to lan? because then cant they just start it when you open to lan?

the internal server simplified the game code and improved singleplayer performance, honestly it's a no-brainer from a development perspective.

The milliseconds is not server ping (that is less than 1ms, since it's just code talking to code) It is the time per tick (game tick, redstone updating, random tick firing). 50ms would be the max load before lag from a server, but in singleplayer you share the server load with the client rendering, etc.

this update also broke the ghast's fireball throw animation where they would expand before shooting, the nether portal client functions where now the entry animation and sound would play when exiting a nether portal, and the damage flinch indicator because all of these relied on the client and were old features that they forgot to fix while testing. while the portal issues are somewhat fixed (not really, the exit sound now plays when leaving a portal instead of on the loading screen like it's supposed to--the entry sound still plays as well regardless) a lot of quality of life features were broken in this update and mojang's stubbornness to fix them is really irritating to me

5:21 Same, portfowarding is such complicated! I put same ip etc... still wont work!

I recently started a hardcore world on this version for the nostalgia as it was the version active when joined the game.

Good video, keep it up!

"I still don't know how to port forward to this very day" so relatable, I tried for so long and didn't succeed and at the end I just used an aternos server like everybody else

I experience the Server desync and lag daily because me and friend we both play in a private Aternos server(My server is Vanilla 1.18.1). It was so annoying I wish Mojang fix it.

YOU NEVER MENTIONED - the injury animation was directional in singleplayer pre 1.3.1, but this has been permanently broken ever since then because mojang refuses to add one line of code (to tell the server that it's supposed to tell the player which direction the damage came from)

So many years have gone by, and just like you, i still don't know how to port-foward.

GOD I REMEMBER THE SHIT STORM THAT WAS 1.3 SNAPSHOTS

Personally, I think that the internal server is a good thing, because prior, the singleplayer chunk loading was kinda trash and inconsistent, so there were things that worked in multiplayer and not single player and vice versa. And the other parts of 1.3 were good too.

as a speedrunner, yeah… i’m thankful for 1.3 because my 1.7 pb was carried by a desert temple and i really like temple runs in general. i also like using a tower exit which relies on respawn invulnerability, initially a server feature but added to singleplayer in 1.3 as well. but my god the ghost buckets. we could build so many portals so much more consistently if not for ghost buckets. especially for portals in which you remove a lava block before allowing water to flow into its position such as the magma ravine portal cobble skips. if you can’t find another spot to build this portal, it’s not just a timeloss but the run is usually completely dead

Dude! You are soooooo informative!! Thanks for being soooooo EPIC!!

That xp enchanting one brought back both good and bad memories lmao

I feel you about port fowarding. Always been a pain in australia

Dude, when I was a kid, I remember playing Minecraft and it lagging when I was in single player but as an adult I always just figured my frames were bad. Now I know I wasn’t crazy as a kid and it actually was lagging. Thank you for making me feel sane 😂

I hate having to raise my shield sometimes over a full second in advance to block an attack

I think the problem with all these people asking for pre-internal server behavior to be restored is that they probably cannot even do that. Think about it, the internal server is such a massive change of Minecraft's internal code that they probably effectively removed what used to be done client-side from the client. Do people think they've maintained several years of additions to the codebase on a build of the game that has the old client structure just in case? That's a waste of time, manpower, and money. If they wanted to bring back the old behavior, they'd probably have to start over from 1.2 and rewrite ten years of updates. Can't imagine what the bug tracker would look like on release.

i swear that back in the day i once got disconnected from my singleplayer game

Fun fact: In the Beta (I checked 1.5_01) the Diamond tool material in EnumToolMaterial is actually called "EMERALD". Meaning that every tool crafted from diamonds is referenced as Emerald type in the game. Maybe Minecraft was supposed to have Emeralds instead of Diamonds in the first place.

As a primarily creative mode player, this was a REVOLUTION in gameplay. The new inventory and single player commands completely overhauled the game.

Is there a mod that removes the internal server and makes it run proper?

I was quiet new back then, only a few month i think, but i loved the update so many nice things. My problem it took away playing survival in Singleplayer, i can cheat at anytime. But the bugs i never saw cause i started lplaying on servers only

One time I put down water and it placed it, it was full of water then when I placed it there was no water and the only water that was there was the one I placed before so it did ghost water and one time when a mob ran over a block right when they did it the block disappeared then when I rejoined it was back in my inventory

i had a problem when i played on mine i5 2400 procesor with integrated graphic ( i was hosting server) i had pretty good modpack but i could not pick up liquids like lava to power generator so now i play on better pc with newer version and i didnt had that problem ever since.

If you are discontinued form your network does it still lauch an internal server? Couldn't we theoretically make a mod that disabled the internal server?

On my old computer minecraft ran like crap 30fps was the best I could get and the world constantly freezing up was awful, however when I played on multiplayer servers the game ran at 45-60fps and no freezing issues. So I tried hosting a server and running minecraft on the same computer finding the game was far more stable and responsive, over just running minecraft in single player.

New mic or audio settings?

1:30 "Trading being added was a big deal" literally haha

0:54 I don't know why but that sound hit way too hard man

One of the first updates I can remember

Hey I actually took like 6 months until i came to the answer for portforwarding: so you put your ipv4 adress in one of the spots in server.properties and also enter 25565 into the server port option there

never been this early man! I’m always cautious about this genre of content because sometimes someone’s channel comes across as trustworthy but they are actually feeding you false info basically wasting your time with a false narrative. I want to say I roughly began playing on Java in 1.6.4 but played on Xbox years before that. Good times.

Can you do a history of world generation?