You can specify the version of Java the game uses in the profile settings (click on "more options" and you'll see an option for the Java executable). Note that it is very strongly recommended to always run separate versions in separate profiles and game directories (this will also prevent settings from being reset as well as errors, crashes, and corrupted worlds from being opened in the wrong version. You can even run multiple modded instances in separate directories, each with its own "mods" folder) so this will not conflict with newer versions (1.12+ will not work with Java 7). Also, the latest version of Forge for 1.6.4 was patched for Java 8 (according to the creator themselves, if you really need an older version because a mod is incompatible there is a "LegacyJavaFixer" mod (see second link), not sure about a download but many 1.6-1.7 modpacks still include it).
- TheMasterCaver
- Registered Member
-
Member for 9 years, 11 months, and 19 days
Last active Tue, Sep, 26 2023 13:14:38
- 284 Followers
- 13,164 Total Posts
- 4698 Thanks
-
Oct 31, 2020TheMasterCaver posted a message on JAVA Account Migration: What You Need to KnowPosted in: News
-
Oct 24, 2020TheMasterCaver posted a message on JAVA Account Migration: What You Need to KnowPosted in: News
What's this "decline" that everybody is talking about? You mean the supposed "decline" that followed Microsoft's acquisition of Mojang back in 2014? Certainly not evident in player counts or sales, which have increased for the better part of a decade, if not since the game came out, especially player counts. You mean Google Trends? Not even close to a reliable source, as if it was correct it would still be far less popular right now than it was in 2013 - while player counts are around 10 times higher - likewise, the number of YouTube videos has little bearing on the number of players (and might even reduce play time if they spend more of their free time watching than playing; granted, I found Minecraft through YouTube but it has likely become less important as the game has become mainstream):
https://www.theverge.com/2016/6/2/11838036/minecraft-sales-100-million ("Microsoft's video games revenue has been climbing steadily since the Minecraft acquisition, and it increased by $367 million in the 2015 financial year "mainly due to sales of Minecraft.")
https://www.statista.com/statistics/680139/minecraft-active-players-worldwide/ (note that 2019 was skipped; recent growth is not much different from 2016-2018, the "dark days" according to some)
Of course, this is for all editions of Minecraft, of which Java is a tiny minority at this point, and has been since 2012 (the rise of other editions hasn't really hurt it though, but it hasn't seen their exponential growth):
https://www.gamesbrief.com/2013/01/minecraft-grosses-over-250-million-in-2012-but-which-platform-dominated/ (PC/Java was only 16% of end of the year sales, 28% for the entire year, despite Pocket Edition (now Bedrock) being in its infancy and only one console)
The only issue I have is that I'll have to make yet another account for a site/service which I never use, much like how I had to make a Twitch account to keep using these forums, which I've never touched for any other reason. Even the cape offer is useless since I play on an older version which can no longer access the skin server so I'll never be able to see it (I just replaced the default skin with my own, and even disabled the skin download code to prevent wasteful attempts at connecting).
-
Jul 14, 2020TheMasterCaver posted a message on Java Edition: SNAPSHOT 20W28APosted in: News
I always find it interesting when Mojang fixes "bugs" that I didn't even know were bugs; a while ago I modified how Thorns works so it only takes away durability (+1 or 2 total) when reflecting damage, along with lowering the cost from 8 to 4 per level to balance it (with the 1.6.4 repair mechanics it is insanely expensive, adding 24 levels to the repair cost by itself for something that only has a chance of dealing 1-4 damage), never having known about MC-34661 until now (I don't play newer versions but I look at the fixes for any potential bugs that I can fix in my own version as bugs can be far older than the report might indicate; I also previously fixed MC-185925, also without knowing that there was an actual report for it, only a mention on places like Reddit, in my own rewrite of the ore generator, along with many other examples of the form (double)((float)posX + 8.0F) instead of (double)posX + 8.0D, which based on other reports, e.g. MC-167042, somehow persists in newer versions (they knew about and fixed other issues caused by this long before they added campfires so there is no excuse).
-
Jun 18, 2020TheMasterCaver posted a message on JAVA EDITION: 1.16 PRE-RELEASE 8 & Release Date for Java and Bedrock!Posted in: News
I'm still wondering when/if Mojang will ever get around to fixing the following bugs, which I fixed myself, some many years ago and some quite serious (I'd never play on a game that can randomly corrupt the world), and many with community-provided and verified fixes?
MC-2025 Mobs going out of fenced areas/suffocate in blocks when loading chunks (perhaps the most infamous bug of all time based on the votes/duplicates - I used fixes given in this report, same for many others)
MC-9568 Mobs suffocate / go through blocks when growing up near a solid block (related to MC-2025, I literally just copied this code with a few changes to the names)
MC-43968 Ambient occlusion bug (With partial fix)
MC-138211 Incorrect Smooth Lighting (Ambient Occlusion)
MC-68129 Smooth lighting doesn't work properly underwater
MC-176743 Smooth Lighting doesn't work on water
("fabulous" graphics?)
MC-161823 Chunk corruption in 1.15 & 1.16 Snapshots (the release of 1.16 needs to be postponed indefinitely until this is fixed, as verified by extensive testing. Every day this report gets several more duplicates, soon it will have more than the far older MC-2025, and it is just the latest in a string of "resolved as fixed" reports going back 8 major releases, with most reports since 1.14. I've never actually experienced this in 1.6.4 but I've made fixes to chunk saving/game shutdown that may cause some forms of corrpution)
Of course, a cave update also can't happen until Mojang fixes MC-7200 and MC-125033 (these are much worse when you have huge caves, compare to my own fix, which might seem a bit odd when rivers float over them but I'd rather have intact caves) as well as serious issues with the seeding of the RNG (in particular, 1/3 of all seeds have 1/3 of all sign-reversed chunk coordinate pairs having the same chunk seed, meaning that if you explore around 0,0 a third of all caves you find to the north will be identical to the south, same for east vs west. It is also very easy to use a true 64 bit RNG instead of Java's obsolete Random class for improved randomness). -
Feb 9, 2020TheMasterCaver posted a message on JAVA Edition: Snapshot 20W06APosted in: News
Diamond used to be as good or better than Netherite - my Sharpness V diamond sword does 14.25 attack damage (displayed as +13.25 in vanilla 1.7-1.8 as this is added to your unarmed damage of 1) compared to 11 for Netherite, which also only deals the same amount of base damage (assuming Mojang doesn't nerf it, as a combat snapshot nerfed diamond down to 6 damage, so Netherite would then be 7). Likewise, armor has the same number of points and its higher "toughness" only reduces the effect of armor penetration (any damage at all will reduce it to below the constant 80% that versions before 1.9 had. For example, a creeper deals up to 49 damage on Normal difficulty, which will penetrate (damage / (totalToughness / 4 + 2) ) armor points, or 24.5 (limited to 80%) in most armor (0 toughness), 12.25 in full diamond (8 toughness), and 9.8 in full Netherite (12 toughness), the latter reduces the overall protection to 40.8%, allowing a lethal 29 damage through (49 * 0.592) - while prior to 1.9 you could survive a point-blank hit even on Hard (73 * 0.2 = 14.6 damage).
If anything, it isn't much different from TMCW's amethyst items, which mostly have the same stats as diamond in vanilla (more durability is the main difference, and even then the pre-1.8 repair system, which based costs on durability and enchantments, makes it so expensive I had to raise the anvil limit to 49 for these items only for them to get reasonable enchantments and be repairable), which was in turn nerfed along with everything else (e.g. all weapons do 1 less damage, diamond armor is only as protective as iron in vanilla, which in turn is worse, etc), requires finding an extremely rare ore/chest loot (8 times rarer than diamond in caves, 2 times rarer at y=1 (above flat bedrock at y=0), forcing you to mine below lava level in a world with double the lava-level caves as 1.7+), and is nonrenewable aside from very rare mob drops (only raw diamonds are nonrenewable in vanilla, I made Giants drop one when killed with Looting). You also need to keep finding more to maintain your gear since you have to repair them on the anvil, while now you can just slap Mending on your gear and call it a day (prior to 1.8 you could simply rename an item and the cost wouldn't increase; my own version of Mending works the same way). Of course, it is in the Overworld; the only thing I really do in the Nether is mine quartz for XP, which I only do once (after I'm done with them I delete the Nether and End to reduce the size of backups). -
Oct 16, 2018TheMasterCaver posted a message on Minecraft 1.13.2 Pre-ReleasePosted in: News
It is worth noting that MC-91621 is far older than indicated by the affected versions - pretty much any version of the game (even Alpha/Beta, if not earlier) with the current mob (de)spawning algorithm can be affected since it happens when mobs spawn more than 128 blocks from the player and immediately despawn, which will happen constantly when you are more than 128 blocks away from any water or land, with a theoretical maximum rate of 18,000 mobs per second for each of hostile, water, and ambient mobs (I inadvertently fixed this myself a couple years ago when I changed the mob despawn radius from a sphere to a cylinder for unrelated reasons, otherwise, I never noticed it since you must be high above the surface and older versions perform better).
Aside from that, "performance improvements" do not impress me when they need to improve performance by up to 1000% (10x faster) to offset the performance differences I saw with 1.13 and TMCW (e.g. startup and world generation time) - and that will certainly never happen with the current codebase (since 1.8), and when major releases are involved (e.g. 1.12 to 1.13) they always seem to translate to the opposite. -
Jun 15, 2018TheMasterCaver posted a message on Minecraft 1.13 Pre-Release 2Posted in: News
I haven't. The rarity of packed ice is what makes ice spikes biomes valuable...
Not everything should be craftable, farmable or automatable. Some resources like packed ice need to be left up to the player to get. If you can just craft packed ice, it's not rare anymore... (It'd be one thing if they added a compressing machine of some kind that required fuel, but just being able to craft a rare resource from a resource that you can get for pretty much free is not my idea of good gameplay design.)
I don't like the idea of having to destroy a biome just to get a rare resource though, which is why I made it craftable in my own mod years ago; I even reduced the recipe cost from 9 to 4 regular ice (2x2 instead of 3x3, which I first had). I don't see anything special about packed ice other than not melting and have never actually used it, nor have I ever found an ice spikes biome despite my modded worlds not having climate zones as 1.7+ does.
Likewise, I made various biomes replace stone, dirt, and gravel with biome-specific blocks - you'll never run out of them or have to strip the surface to get them, craftable or not (I've since added more than shown and made them extend deeper underground). You can also make ice and/or packed ice generators with dry ice in the same manner as a cobblestone generator (dry ice can only be found in Ice Plains Spikes though).
While they are at it they could also make podzol craftable (2 dirt + 2 spruce leaves = 2 podzol in my mod); they already made it easy to obtain by leaving in the bug where 2x2 spruces converted grass into podzol (marked as WAI so they consider it to be a feature). -
Oct 20, 2017TheMasterCaver posted a message on Merge Your Minecraft Forum Account With TwitchPosted in: News
The game is not even close to "dead" if you believe the stats that Mojang claims (122+ million sales and 55+ million active users per month, the latter up 37.5% over 9 months) - but the forums most certainly are - and have been dying for 5 years, even as the number of copies sold (including the supposedly even deader Java edition, which just hit 27 million sales) and players has increased by around 6-fold (and oddly enough, the forums continue to gain members at the very healthy rate of a quarter million+ per year - what do all of those members do? Or maybe they are just spam accounts).
I may soon stop posting as well, not because of the Twitch merge (seriously, it only took like a minute to create and merge an account) but because these forums have become incredibly boring - the only problem is there are no other forums like these that I know of and places like Reddit or chat sites/apps like Discord (or the forum chat, which I've never used) do not have the same attraction as a forum. -
Dec 14, 2013TheMasterCaver posted a message on Saturday with Sach: Whats In a NameMy name comes after my username on Totaljerkface.com, which as you can guess, comes from the game Happy Wheels, which I used to play a lot back when I registered for Minecraft; the clothing on my skin similarly comes from a character in that game.Posted in: News
- To post a comment, please login.
0
My own take on a "mega taiga" biome, prior to adding the "vanilla" variants (which coexist with my own version) included adding gigantic trees with 3x3 trunks, which generate along with normal sized trees and spruce "bushes" at ground level:
I also added a "mega forest" biome with trees up to 64 blocks tall and a similar layered structure (much like a real forest):
There's also a "mixed forest" variant with all types of large trees:
Both variants can be seen here (mixed on the left, normal on the right):
There is also "mega tree plains", similar to how plains have the occasional single tree:
In 1.7 Mojang removed big oak trees from most world generation due to "lag" - I fixed them and dedicated an entire biome to them as a memorial, including an unused 2x2 variant hidden in the code (they did re-add them later. I also wonder why Mojang still hasn't incorporated all-bark logs in trees, as I think all the exposed ends look ugly, to not interfere with wood gathering I made them require Silk Touch, in a similar manner to the raw 1.8 stone types):
These biomes were all added way back in 2014; more recently, I added "big birch forest", with a new variant of birch tree with 2x2 trunks which split into 4 single trunks, as well as a "poplar" shaped variant (both large and small sizes, along with vanilla birch trees, and in various combinations with birch forest):
Another biome is "great forest", with larger variants of oak and spruce trees in new forms, whose mix varies from region to region:
There's also a "mushroom forest" biome; I also added more variants and colors of mushrooms and giant mushrooms (these also generate on mushroom islands, with mooshroom variants to match, and in random areas underground):
0
On each of three consecutive days I found a witch hut, desert temple, and a village, and if you think they count as a structure, a desert well, with the desert temple, well, and village close enough to be seen in the same view, which may be the closest in time that I've found 3-4 structures in this world; these are also the 7th desert temple and 16th village I've found, and the first village I found in 6 months of playing (two play periods since October 2021) and first desert temple since January 2018, with around 400 sessions elapsed since then:
While they were relatively close together I did not see the village until later since this temple was technically past the edge of which I'd explored (underground) and I only made a special trip to check it out, not checking further into the desert until the next day (the fact I said this shows just restrictive I am at what I explore outside of caving):
The desert temple had a couple diamonds and 24 gold, quite a lot from what I can recall finding (this may not be so unusual for newer versions; since 1.9 loot is much less random and there can be more stacks per chest; I've seen people post screenshots of loot chests with all 27 slots filled; of course, I put all the loot into a single chest to take a screenshot. I also took the bones for bonemeal, I never take saddles once I've collected several):
I also later ran into the basement of the desert temple exposed in a cave:
Deserts are actually the "flattest" biomes in 1.6.4, flatter than Plains, yet as seen here they can still have a fair amount of elevation changes (I had to dig out or build staircases to several of the houses; not visible in this view is a field which had a 8-10 block drop to the surface below on one side). Another major difference from newer versions (or TMCW) is that there are no surface cave openings since caves can only cut through stone, dirt, and grass (I did semi-fix this fro this world by adding mycelium to the list; in TMCW I actually have no list, just anything goes, except for water, which has a separate check so they do not run right into it, and bedrock at y=0, by limiting the minimum y-coordinate to 1):
A view (taken at max FOV showing the village (left) and desert temple (right):
If you look closely you can also see a desert well near the center, shown zoomed-in here (similar to witch huts I never kept track of how many I've found in this world, which would be similar to other structures given a 1/1000 chance per chunk, compared to 1/1024 for structures):
I also recently found the largest complex of mineshafts since exploring the southeast map, when I found complexes of 8 and 9 mineshafts one after another, with a total of 5 mineshafts embedded between several large cave systems; surprisingly, despite the amount of caves there were no additional mineshafts in vanilla (due to my code that excludes them from near dense cave systems), so this is pretty much the most extreme case of intersection between caves and mineshafts that I may find:
This is an analysis of the area (the image was slightly cropped to fit the mineshafts):
There were also two fairly large caves, which can be seen on the map (the first one is the largest green area towards the lower-left, which cuts it off above y=62, while the volume accounts for the part above as it was still underground, and the second is near the right-center):
Also, this is what happens to caves in deserts prior to 1.8, which allowed them to cut through more blocks (contrary to widespread belief caves can only cut through a small list of blocks, and even if any block is allowed, as in TMCW, they can't cut through non-terrain features, such as strongholds, which simply don't replace air blocks):
Also, these are screenshots I took of my maps while exploring, showing my general progression from day to day, and how far I may go into "explored" areas; also notable is that land has extended much further east than I expected, to at least x = 4200:
This was taken from were I took a screenshot of the witch hut:
This is the furthest east I've explored at any point so far (I might have gone further east from the northern landmass if I'd found caves in that area):
This was taken from where I took a screenshot of the desert temple, which is near the northern edge of the same desert my latest base is in, 576 blocks south from the northern edge of the map, and from the looks of it, the village as well (this would be several "biome units" merged into one larger biome, common when there are only 7 biomes to choose from):
0
Bottles o' enchanting used to be far cheaper - in 1.6.4 (before 1.8) you can buy 4 for a single emerald and I've actually done this in order to get a bit of extra XP for enchanting items (at 1 level each though, I just enchant the items I sue to repair my gear with level 1 enchantments, same for the iron pickaxes I collect from mineshaft chests, combining them to higher levels, and use to dig rail tunnels/secondary bases). Whether that was too cheap (apparently Mojang must have thought so), in 1.8 they increased their cost to 3-11 emeralds each - or up to 44 times more expensive - no doubt the biggest nerf to any tradable item (that can't be obtained in any other manner, or removed outright). Even now they are shown to cost 3 emeralds each - still up to 12 times more expensive (or 4 after maxing out their discount).
Also, many of the things you list have been rendered "useless" due to newer additions - ocelots? In 1.6.4 you tame them in order to get cats, something which I haven't changed (except for black cats spawning in witch huts) and cats themselves can keep creepers away (if only useful sat down in front of your base, not taken along with you, certainly not with my playstyle - I remember taking a wolf along with me while caving and needless to say it didn't go well).
I also see nothing wrong with more "wildlife" in general - polar bears? I added them, as well as brown and black bears (texture/size change) just for more variety, and even a bit of a danger (brown bears spawn in any forest while black bears spawn in an "autumnal forest" biome based on this suggestion, and are always hostile until fed meat, which makes them neutral). Likewise, glow squid add ambience to caves and I find their drops to be very useful - ever make a map wall and noticed the inconsistent lighting, unless you place them on glowstone? I did use to do that but the wall must be 2 blocks thick if you don't want the other side to be exposed - glow ink sacs solve that (yes, some say you could have just used glowstone dust) - I even added the ability to make paintings glow for similar reasons.
Also, what about Giants? Or you you not even think about them? I don't blame you since they haven't naturally spawned since InDev (if ever, the Wiki doesn't seem to say), but 1.8 made them literally useless by removing their AI (which had various issues, mainly because they still used a much older AI system, which I replaced with the more modern one, enabling them to properly pathfind and all that, with their damage reduced to 10 as 50 damage is too overpowered, considering even creepers deal less and can only do so once. I also recently figured out why their attack reach/attacking them was so inconsistent and fixed it (they could only damage you from feet level, likewise, you could only consistently hit them at their feet, depending on where they were within a chunk section. A similar bug causes tiny magma cubes to only damage your from above, which I fixed so touching their bounding box deals damage, making them a lot more dangerous, partly offset by limiting their attack rate to once per second like other mobs).
Also, one of the most insane things about Giants? Look at the history - in 1.14 they gave them a proper AI over multiple snapshots - only to throw it all away - and that is why it takes them so long to release new updates.
Or killer rabbits - a complete waste of code if you ask me - much like an early 1.8 snapshot I made them naturally spawn, and much more often (1/256 chance, though I only encountered one in over a year of playing on a world, more certainty spawned though, as they are small and don't render/aren't easily recognizable from far away).
Why did they remove endermites spawning when an enderman teleported, also present for a short time in 1.8 snapshots? I even made them naturally spawn, like any other mob, as well as "cave" spiders and silverfish, all below sea level (the last can only hide in blocks if attacked by a player, or spawned from infested stone or a spawner). Even husks and strays - why only on the surface? I'd almost never actually encounter them while playing - I made them spawn everywhere as 50% of zombies/skeletons, and I added various colors of husks for more biomes (red for red sand/mesa biomes, white for "quartz desert" and "volcanic wasteland" biomes, pink for the Nether, which also has pink "nethermites").
All of this, along with much more varied world generation on a local scale, and the fun features of slimes splitting into magma cubes when they die in lava, "cave spider jockeys", and baby skeletons/strays (just as you might think - baby zombie + skeleton), and armored/weaponed mobs being much more common (in part because I removed regional "difficulty", a useless feature which only made the game easier, with 1.8 making it even worse, at least in 1.6 you can still get armored mobs, etc on the first day even on Easy, which never happens since 1.8, and takes a while on other difficulties) greatly increases the variety of mobs I regularly encounter, even if there aren't as many as in the latest versions (the main reason I haven't added more is because of the models and AI; when I added fish I even created my own model from scratch instead of trying to decipher Mojang's model system).
Beetroot also still has to be more useful than poisonous potatoes, otherwise, much like gold items in chests or enchantments like Bane of Arthropods they probably just added them to nerf villages (i.e. less of the more desirable crops, even before wheat was the most common). They can also be used as food for breeding pigs or villagers (though arguably potatoes are the most ideal for both, and when cooked make a decent player food, with Fortune giving over 4x the yield per crop; they (slightly) nerfed the hunger value of baked potatoes in 1.8 since they were so broken, but even beetroot soup (6x beetroot, requires 7 slots for a stack) is barely any better).
0
Prior to 1.8 there was an interesting quirk in how mobs spawned - the initial location chosen as the center of a pack had to be an air block - nothing else - or the pack completely fails (individual spawn attempts could occur in any non-colliding transparent block), and this actually resulted in no mobs spawning whatsoever in e.g. a Superflat world with a layer of snow at the top:
I even noticed this myself the first time I found an Ice Plains (since then I made my own modifications similar to 1.8); Plains is affected to a lesser degree due to the tall grass, same for Taiga (the lack of snow under trees allows packs to spawn, otherwise, the pack center can also be an air block next to a hill, spawning individual mobs on it, and trees ensure the section height is above ground level (prior to 1.8 the game used chunk sections, in multiples of 16 blocks, instead of the height of the highest non-air block, a consequence of this is that even with no transparent blocks mobs would not spawn if the surface was at the top of a section), with other non-desert biomes either having too many obstructions (trees or water) or uneven terrain:
Another benefit of deserts is the lighter color of sand, which increases visibility at night and contrasts with mobs; beaches can work just as well but are often small and uneven, while deserts (not hills) had the lowest height variation of any land biome (pack spawning is most efficient on flat surfaces since individual spawn attempts are all on the same layer, this remains true as of the latest version).
1
This is most likely due to "level.dat" becoming corrupt for any number of reasons and can easily be fixed by copying and renaming "level,dat_old" to "level.dat"; failing that, create a new world with the same settings (seed, etc) and copy its level.dat file over (you will lose your inventory - just cheat your items back in, and you'll be back at the world spawn point, again, /tp to wherever you were). It used to be that you could just create a new world with the same name but they recently changed it so the game will not reuse an existing directory (as a workaround to fix MC-315 Chunks do not delete properly remaining in a newly created world if the same world name is reused - but this was a useful way to recover a "deleted" world. The root cause of this specific issue (when legitimately deleting a world) was caused by the client attempting to delete the files while the internal server was still saving, with the true fix being to force the client to wait for it to fully shut down).
Also, this should never just happen; I've only ever experienced this after the game crashed, and interestingly, not recently in any of my modded versions (where I've had plenty of crashes during development, otherwise, the game should never crash, ever. I've seen people who think it is normal, even for modded versions - unacceptable, which is why I debug things so thoroughly - not a single crash in over a year of playing on a heavily modded version), likely due to changes to make sure the game shuts down as cleanly as possible; various other forms of world corruption have been linked to the fact that in singleplayer the game runs an internal server on its own thread and the client does not properly shut it down. Another major cause of corrupted worlds is likely user error due to not shutting the game down properly - never, ever click the close window button (X) when in a world, and to be safe, at all - always use "save and quit to title", then "quit game".
The same is also likely true of MC-161823 Chunks can occasionally be misplaced upon loading a world - most of the cases are (hopefully) caused by user error or faulty hardware, else there is a serious issue with how the game saves, and has been for many years based on the trail of reports, all closed as fixed only to be re-opened (I never experienced this in 1.6.4, vanilla or otherwise, only level.dat becoming corrupted, though a full drive has been reported to cause it in older versions, newer versions are also slower so there is more time for issues to occur). Either way, even if user error is the primary cause the game has to cleanly shut down, just as if you tried closing a word processor and it just closed without asking if you want to save (even something as basic as Windows Notepad does ask), or terminated itself without waiting for the file buffer to be fully flushed to disk.
0
This can only be caused by a resource pack - there is no way just the eyes of entities could be affected by CPU/GPU drivers, or anything else (like how even? One look at the texture of an entity is all you need to know, sure, if the eyes were some separate texture, but they aren't and other pixels (and textures) should also be affected, not the very specific ones where the eyes are, with the exception of spiders and endermen).
See this Reddit post from somebody who had a similar issue, it was caused by using a resource pack in a game without support for custom entity models (which requires Optifine, even the latest version still doesn't support custom entity models):
https://www.reddit.com/r/Minecraft/comments/oyolld/the_mobs_in_my_minecraft_world_have_weird_eyes/
In particular: https://www.reddit.com/r/Minecraft/comments/oyolld/comment/h7vqqn4/
0
Villagers do not despawn but they can certainly be killed by zombies, which actively seek them out - you must build a wall around and thoroughly light up any village you want to keep alive (example of what I do with villages, in an older version so not as much lighting is needed, I'd still do that for visibility though; example of how much zombies want to get to them, outside of a base which has villagers inside). Some people say that iron golems are enough but I would never rely on them (they are supposed to spawn much more often in newer version, even too much, they are no match for baby zombies in particular though, too slow and bulky). The fact that a creeper got into a boat which formerly had a villager in it proves that you did not do this (and no, mobs do not turn into other mobs, except if a villager is killed by a zombie, then it may become a zombie villager, depending on difficulty; the creeper just happened to wander into the now empty boat).
1
According to the Wiki carpet is (still) fully transparent to light (I say "still" because there have been some changes to how blocks block/transmit light in newer versions). You can also verify this by looking at the light level in the debug screen; opaque blocks like soul sand cause it to read 0 since the game is attempting to read the light level in the block, which is 0 (such blocks set a "use neighbor brightness" flag to make the method that gets the light level when rendering a block use the light level adjacent to it).
Also, I fixed this myself (F3 displaying the light level as 0) by checking the light level of the block above when in an opaque block (I'm surprised this is still an issue in vanilla, it started in 1.8 when they changed the light level to be read at your feet instead of eye level, a change I also made since it is usually more relevant, e.g. mob spawning):
0
Did your really post in a 12 year old thread just to say that? And not even a new user (based on join date)?
That said, this still happens in the latest version of the game as it is caused by the way the game places decorations, which overlap between chunks and many have specific requirements (for example, trees only generate on grass or dirt blocks with a direct view of the sky, meaning adjacent trees can block their growth), and since a single RNG, which is seeded once per chunk, is used to seed all decorations any changes will cascade to affect all subsequent decorations, and this will vary with the order chunks were generated in, which is consistent with the varying spawn locations given in the OP.
Given that the world spawn point is well-defined in newer versions it is much less likely for their to be significant differences in the area immediately around spawn but areas further away will only be identical if you explore the world in the exact same manner, and there could still be differences due to various post-world generation changes (e.g. fires randomly spread and when near the edge of generated chunks can change things enough to affect the placement of decorations).
MC-55596 Some chunks in the same world seed seem to have different versions
An example that is quite reproducible, depending on the direction you approached the area from (I had only tested two directions, north and south, but it is entirely possible that east and west could produce different results):
https://imgur.com/a/hkCz5t4
Another example which shows changes in a localized area near the bottom, as well as a spot near the lower-left ("new" and "new2"; the original world is more different since this was showing the impact of changes I'd made to my mod since I created the original world, as well as an example of inconsistent world generation between two instances of the same seed in the exact same version, even with my own code changes that make it less likely to cascade (each decoration step uses a new "chunk seed", so e,g. ores were unaffected, unlike the example above for vanilla):
0
This might have been a side-effect of the internal server limiting the view distance to 10 when you set it to "Far" so loaded chunks don't cover it; I don't see it appearing in any screenshots taken from high up, even when looking down from very high up (as you go higher up the game shifts it down until it disappears into fog, but still cuts off the sun/moon/stars, until you go so high up it goes outside of the view frustum (far plane distance), but that is impossible in Survival (even the terrain eventually disappears if you go high enough).
0
Somebody recently posted a similar thread in Support and said that updating their "MB drivers" (which I think means "motherboard") fixed the issue for them; as I also noted, a report on the official bug tracker seems to say that everybody with the issue was from northern Europe, so it could be affecting a regional computer brand (if not necessarily exclusive to the region):
https://www.minecraftforum.net/forums/support/java-edition-support/3187243-extended-loading-and-saveing-times
0
I don't get why these suggestions are still so popular; want an early game backpack? Make an ender chest, and Mojang is not going to make it as easy as crafting some leather and string to greatly expand your inventory (54 slots? Even if you could only carry one, e.g in the chestplate slot, as a backpack mod I once used had as an option?) Not only that, Mojang has in fact attempted to add such backpacks, only they called them "bundles" and they could only carry more types of items in one slot, not more total, and they have yet to make them a non-experimental feature after years (no idea why but balance might be one reason, even if they don't actually increase the total number of items you can carry; they also seem unintuitive to use, instead of working by right-clicking while holding them to display a GUI / inventory, as with any other container and as the backpack mod I used).
0
I've seen you mention this before but they really didn't make fog darken when underground? I find it to immersion-breaking to see light fog and even the sky in unloaded chunks, which is why I made it so that they both turn pitch black (the sun/moon/stars also fade to darkness). This also used to happen in vanilla prior to 1.8 (just the fog though), when they removed "void fog", citing non-existent performance issues which were entirely the fault of the particle effect (the fog darkening and reduced distance involved a simple check for the sky light level at the player - which is being done anyway when rendering the player (or arm/held item):
Examples:
A different angle with no sky light:
This was taken back when I used Optifine to disable void fog, which also disabled the darkening effect (not just the particles or closing in):
For comparison, it would now look like this - not much clues as to large it might be until I've actually gone in to explore it:
A view from a similar angle (and a higher render distance) after I'd explored it:
Similar to sky light, going above sea level does disable the darkening effect; this also shows another feature which has been missing since 1.8; the area below the horizon used to be blue and helped oceans blend in with the edge of loaded chunks, both in color and by hiding the sub/moon (which became visible above the water, not the seafloor, as they do in newer versions):
While deepslate does have twice the hardness of stone it takes less than twice as much time to mine, especially once you add an additional 0.3 second delay between consecutive blocks (with an iron pickaxe the raw mining times are 0.4 and 0.75 seconds respectively; consecutive blocks take 0.7 and 1.05 seconds; the differences are less with better/enchanted tools, an Efficiency V diamond or netherite pickaxe takes 0.4 and 0.45 seconds per block). Then again, I do notice a speed increase when upgrading to iron, then diamond as soon as I find them respectively (I don't bother getting Fortune before mining more diamond), I even enchant the pickaxes I use to repair my main pickaxe with Efficiency I (level 1 enchant) as I use them for a bit to maximize the durability per pickaxe (the anvil bonus of 12% corresponds to 187 additional uses, 374 if they happen to get Unbreaking; if they only get Unbreaking I use a book to add Efficiency to them).
Diamond is the second most common ore near bedrock, and is far more common than it used to be, both overall and relative to other ores:
(original source)
By contrast, this is what ore distribution was like before 1.18; note that this is more comparable to figure A (total blocks) than figure C (percentage, as these are) since they are out of all blocks, not just "ground", so you can see how much they nerfed coal and iron, I don't see much impact of the greater terrain variation either (compare the drop-off in coal above sea level, even as 1.18 increased the percentage as a percentage of ground), the Wiki claims that a 515,000 chunk area was analyzed in 1.18 so it should be quite representative:
1.6.4 (based on my own analysis):
Coal: 155.6
Iron: 88.6
Redstone: 25.3
Gold: 8.5
Lapis: 3.53
Diamond: 3.19
1.17 (also based on my own analysis of a 1.8 world, with no changes until then)
Coal: 185.5
Iron: 111.5
Redstone: 29.1
Gold: 10.4
Lapis: 4.1
Diamond: 3.7
1.18 (based on an analysis somebody posted on Reddit)
Copper: 68.7
Coal: 62.0
Iron: 53.5
Redstone: 24.5
Gold: 17.6
Lapis: 16.3
Diamond: 10.4
Also, for good measure this is a chart I made of the ore distribution in TMCW, including data on ore exposure, which can be quite significant (over 20% of coal between layers 10-30 is exposed; the amount is higher due to its larger veins, and vice-versa for ores like emerald). There is also a noticeable drop in totals in the lower layers due to the volume of caves (I'd seen people complain about caves in 1.18 reducing the amount of ore due to less solid ground but the opposite is true if you consider exposed ores, and there is still plenty of solid ground, considering that the peak air fraction is less than 15% and a lot of that is concentrated in large open caves):
Also, the Wiki has an analysis (very old, from 2012, so based on ore generation before 1.8, and to a lesser extent, 1.7) where they concluded that as much as 1.7% of mined blocks could be diamond ore, with the biggest factor being how far apart you spaced your tunnels (interestingly, it continues increasing past a spacing of 3, which is enough to ensure 2 block wide veins are never exposed by two adjacent tunnels, and is always what I've used, and my efficiency does match what they show for this spacing, about 0.9%):
https://minecraft.fandom.com/wiki/Tutorials/Mining#Efficiency_vs_Thoroughness
An example of how I make my mines; they are 250-300 blocks long with tunnels every 4th block, and located on layer 1 due to my amethyst ore being most common on that layer (about half as common as diamond, decreasing to 1/8 as common on layer 3 and above, which are exposed in caves; in this case I found 91 diamond and 23 amethyst out of about 5 km of tunnels):
0
This seems to be a widespread issue all of a sudden; I wonder if somebody released a faulty driver update of some sort:
https://www.minecraftforum.net/forums/minecraft-java-edition/discussion/3186987-autosave-lag-1-20-1 (numerous replies that it is also happening to them)
MC-265470 Autosave lag in single player vanilla (mentions multiple other reports on Reddit, seems to mostly/only affect northern Europe, which suggests a particular brand/model of computer is at fault)
0
Backports aside, I see mods as a way to create your own unique experience, rather than just being "add-ons" to the base game, as I noted in this post on Reddit; future vanilla updates are completely irrelevant and may even clash with your modded content, or require major requites (which in my case means of the vanilla game; instead of rewriting my code I'd rewrite vanilla. e.g. add methods that use xyz variables or an "index" instead of BlockPos, a "block state" as a simple int instead of an object, arrays storing a numerical block ID instead of references to block/blockstate objects, and so on):
https://www.reddit.com/r/feedthebeast/comments/tc60yc/do_you_see_mods_as_updates_or_addons_to_vanilla/
Mods like TMCW are actually fairly popular for older versions (note that these are all different from your usual "add-on" mod; many completely change the game and purport to be "updates" with some even calling themselves e.g. Beta 1.7.4 (as if Mojang had continued the Beta 1.7.x series). TMCW itself just started as a collection of various changes to world generation, hence its name):
https://www.reddit.com/r/GoldenAgeMinecraft/comments/wd1k0o/any_obscure_overhaul_mods/
Also, referring to the discussion about terrain being independent of biomes, most biomes in TMCW actually have the same height variation, aside from "special" biomes like Plains, which are flatter, with "hilly" and "mountainous" biomes generating in all sorts of combinations (not just your old "hills in the middle of a biome, but you can also find the opposite, or half-normal/half hills; and yes, I have "hills" biomes generating as full-sized biomes, not just sub-biomes; note the various shades of orange in this "desert"):
"regional height variation" refers to the use of a large-scale noise field (wavelength about 1000 blocks) to modulate the heights, which e.g. range from 0.7 to 1.0 for the "max height"; for comparison, vanilla 1.6.4 Extreme Hills has a min/max height of 0.3 and 1.5 and most other biomes are 0.1 and 0.3, and 0.3 and 0.7-0.8 for hills, so this gives most biomes a similar or greater height variation than vanilla's "hills".
I also apply special treatment to the noise field for various biomes, most notably rivers and beaches, fixing the issues of rivers drying up (except where it is intentional) and beaches "crawling" up hillsides; in an upcoming update I've added an additional manipulation of biome heights when deserts are adjacent to other biomes to reduce the same thing happening with them (the height is forced downwards / adjacent hills are pushed back from deserts; overall my terrain generator is extremely complex and it is impressive that worlds generate 2-3 times faster than vanilla 1.6.4 despite all this).