Daedalus Young
Assigned
Reported
Comments
Hah, seems I fixed this issue myself. And looks like it actually is a Minecraft bug after all. But since you didn't even consider the possibility and are merely focused on closing as much issues as you can, marking them as "not our problem", not even interested in attempting to locate the source of the problem, I don't know if I can be bothered making a bug report on the issue.
Congratulations, you succeeded in people not wanting to contribute anymore.
I cannot update Java, I already use the latest version that is available for Mac OS X 10.6 and lower.
Sure, I don't think it gives any clues to why the game crashes, as this of course is not the crash itself, but here it is.
I updated lwjgl in the meantime (as suggested on forum, could've just told me here to try that, I know this is not support, but come on, we're not bureaucratic or anything are we?), that did not fix the issue.
"Something" in the game must trigger that crash however. It is not random, I have never seen it on other Java programs, it happens only in the Nether, is fairly repeatable. If I stay in the Overworld, all is fine, but "something" in the code must trigger something in Java which makes it crash. If that something was not in the game, then it would not crash. So it is caused by something that Minecraft does, otherwise it would be a random Java crash. And it clearly is not.
Well that's the last time I volunteered in helping make software better.
This is a bug. Game crashes - that is a bug.
This is the only report there is.
There is no crash report, I already pasted the excerpt showing the crash.
How is this, which is clearly intended behavior, not being closed and marked as such, while the missing colours on the map, which is clearly an unfinished feature, is closed and marked as intended (again, which not entirely so)? This does not make sense, dear mods.
I think it's technically possible, you can specify an order of versions applications can follow to find the first compatible version. Applications > Utilities > Java Preferences.
However, I think some applications don't do that properly, and I do believe Minecraft is one of them. I do remember having to change the order to have the latest version on top, otherwise malfunctions may occur.
Well I don't really agree with that. It may not be a bug in that blocks are misidentified, but it certainly is highly inconsistent. Why have a separate colour for clay, for example, one of the blocks you're hardly ever really looking for nowadays, and a separate colour for wood, but make obsidian the same as stone? Or why make mushroom blocks, pumpkins, dandelions and roses all green?
With there being 14 base colours and 56 actual colours (of which 14 are duplicates anyway), this doesn't fit with the 8bit/binary style of numbering everything else has, and is clearly unfinished or meant to be expanded. Originally maps only had 1 zoom level, but with the option for more built in. That shows the maps were not yet completely done when they were released. This too simplified palette obviously needs to be expanded.
So, no bug, maybe, but inconsistent behavior and clearly not fully done.
Also happens with just the spider's eyes, even when not hitting them.
I don't really see it either.
It may look like it, because of the contrast between the pot and the background. The eye plays lots of tricks.
Your old world may still be there, because Minecraft actually doesn't appear to delete worlds completely. Go to your Minecraft saves folder and see if your old world folder is still there. Make a backup of it. Go back into Minecraft and create a new world, with the exact same name (and seed, if you remember) as your old one. You may spawn in a completely different location, but should find most (if not all) of your old world still there.
If that didn't work, try to copy the contents of your backup back to the newly created world and see if that brings back anything of your old world.
I hope that helps at least. And for the future, always make regular backups of your worlds, just in case the game glitches out.
For some reason, probably Minecraft didn't update its list of worlds when you deleted the temporary one, so when you tried that again, it deleted your regular world, is my guess.
The issue here is that worlds do not get completely deleted when attempted to delete from within Minecraft. Then when a new world is created with the same name as the one supposedly deleted, features of the old world will show up.
A workaround is to delete worlds not from within Minecraft, but in the OS, like in Finder on Mac. Preferably though, when one clicks the Delete World button, the entire world's folder gets deleted, with all its contents. At this moment I see no reason why Minecraft should not do this.
I told people the solution. Those that were helpful in the first place. Even if their suggestion didn't fix it. They took the time to listen to me and suggest a possible fix, so I repay them by telling how I probably fixed the issue. They didn't just say "not our problem, go away".
Why should I care about filing bug reports if it's all tossed in the bin without being looked at?