"There are 16 types of wool but the colour scheme is off" Not off, that's what the colour scheme of wool is for Classic versions of the game. The "off" colours are Chartreuse, Spring, Capri, Ultramarine, Violet, and Rose. In my opinion, they should be added back into the game in addition to our current 16 colours.
3 - It's not a bug. When rendering graphics in the browser, requestAnimationFrame function is used and it only runs when it's the current selected tab in the browser. That's why when you get back it says 0. 4 - It's not a bug. Those were the colors at the time. 5 - It's not a bug. When you screenshot the game... you screenshot the game. So even in the browser it still just... screenshots the game (canvas element). 10 - It's not a bug. That's how sapling were at the time. 42 - It's not a bug. They simply didn't have a purpose back then.1
another bug i found independently: when on the world generation screen, quickly use the inspect function with right click, go to console, and type false. as soon as you finally enter your world, you can successfully alter the world, such as lakes having zero water, and rarely, you can freeze flowing water in time, leaving half a filled lake.
That console is more powerful than you think! About a year after I filmed this I started developing my own 2D game engine in JavaScript, and that console is the one thing that breaks it all. If you took the time to find the right variables you could completely screw up the game!
some of the things are just how minecraft used to be back in older versions (like the liquid physics and sounds) and the loading screen screenshot part is also not rly a bug (what else is supposed to happen)
It is also possible for the world to show glitched parts of the world if set to normal (possibly also huge), where it seems like a bunch of bedrock (including in the infinite ocean) is not covered in water when it should be, and under/near bedrock textures is some light blue (maybe also white). Also, something happened to me yesterday (whether it was related to bedrock or internet access in my case - can't say for sure): My own world became seemingly suddenly inaccessible, forcing me to instead make a new world that can ended up 1. corrupted, still having remains of my previous world 2. inaccessible upon reloading, which resulted in the same 2 things happening if you made a new world The corruption didn't happen once I opened a new world using the menu, but it seems I still had problems with saving worlds (still not working atm, so maybe it's a browser issue).
I have a December 2019 screenshot of a corrupted classic.minecraft.net world I loaded on a Chromebook. It's extremely similar to what you just described
Most of them, like that wool (CLOTH BRO IT IS CLOTH NOT WOOL UNTIL BETA 1.2), fluid physics, flowers and many more are wrong List: 0:06 That is just 0.0.23a_01 nothing special 0:17 Classic also didn't had a save button it saved automaticaly after a chunk update 0:44 Intended, and these are Cloths 0:57 Because the Classic "pause" menu is not exactly a pause menu, try playing Survival Test, go near a mob so it can attack you and pause, you will still die 1:04 Same as above, but without that Survival Test part 1:16 Intended, and they are called Shrubs 1:27 Intended 1:30 IDK 1:36 Intended, becouse it is a invinsible barier 1:51 Intended 1:55 Becouse that water does not exist is just a texture 4:05 That is the default sky texture 6:15 Intended
It's the kind of commentary you get when a 14 year old tries to sound like a nature show narrator while proving a bogus point that may or may not be valid😅
