Minecraft Forums

Okay i wasn't thoroughtly with all the links. Some of them do work.

I tried the links from the version beta 1.6.6 on because that's the first version where i see that it's stated that it supports HD textures without needing the MCPatcher. The version "OptiFog 1.6.6_F_HD" for example and the downloads for the versions after that. But the links for those versions just give me an ad infected page that redirects me to a broken mediafire or 2shared or whatever download that doesn't work.

So if i guess right i don't need the MCPatcher for any version from b1.6.6 on. Now i just need to somehow get those optifine versions and know with which version of the Patcher i need to patch from b1.0.2 till b1.5.2. But thank you, i think i am getting closer to solutions.

Thank you. But i've already tried those links. They sadly don't work anymore. The site always says that the file i want to download doesn't exist. So the guys from optifine probably removed it by themselves for whatever reason.

Quote from TheMasterCaver»

The reason why worlds are sometimes not fully deleted is because the game runs an internal server on a separate thread and the client doesn't check to see if it is still running (or wait until it shuts down) before it lets you try to delete the world, resulting in a failure to delete files that are still in use, and/or the internal server creates new region files with chunks that were modified since the last save (hence why there are often a lot of random chunks left; failure to delete a whole region is more likely to leave a solid area of chunks behind):

MC-315 Chunks do not delete properly remaining in a newly created world if the same world name is reused

(note that the server thread is saving chunks at the same time the client thread is trying to delete the world. This won't always cause errors to be reported, like in the case the client already deleted a region file before the server saves its chunks, creating a new file)

The same mechanism also explains many other oddities/world corruption, and is somehow still not fixed despite being so simple; I fixed it in the first version of TMCW - released more than 5 years ago - and the fix itself was actually taken from Forge 1.6.2 - with this fix it is impossible to replicate any sort of saving/deletion bugs, short of an actual crash):

Vanilla:

if (this.theIntegratedServer != null)
{
    this.theIntegratedServer.initiateShutdown();
}

this.theIntegratedServer = null;

TMCW (this forces the client ahead to wait for the server thread to terminate; this also prevents the client thread from setting the server object to null mid-save, causing world corruption. This does have the (small) disadvantage in that if the server locks up (such as after certain crashes) you have to force-quit the game as it will hang on the shutdown screen indefinitely; on the other hand, without this fix I've had such cases leave a Java process running without any visible window):

if (this.theIntegratedServer != null)
{
    this.theIntegratedServer.initiateShutdown();

    if (this.loadingScreen != null)
    {
        this.loadingScreen.resetProgresAndWorkingMessage("Shutting down internal server...");
    }

    while (!this.theIntegratedServer.isServerStopped())
    {
        try
        {
            Thread.sleep(10);
        }
        catch (InterruptedException ie) {}
    }
}

this.theIntegratedServer = null;

Otherwise, the game won't be able to see a world if level.dat becomes corrupted and it will simply reuse any files with the same names (a simple way to recover a corrupted world is to create a new world with the same name, and ideally, seed; due to level.dat storing special information about the world in newer versions, such as the locations of End gateways and the status of the dragon fight, you should try to rename level.dat_old (a backup from the last save) to level.dat first). This also presents a risk that you could overwrite non-Minecraft files, although that is rather unlikely (you'd need a folder with the same name as the world containing files with the same names as Minecraft data files).

But wasn't that internal server thing only implemented somewhere late in the full release?

I don't know all the details of how Minecraft stores it's worlds, but there are lots of files, a few general ones containing the seed and other info about the world and a file for each block of chunks that store all the blocks.
When Minecraft starts to delete a world and is closed it doesn't check that it has deleted everything before closing down so some files can be left.
When you create a new world with the same name it reuses the directory and any chunks that weren't deleted will still be there.
I don't see how this would happen if you had actually deleted the whole thing but maybe you only deleted some of the files?
Or maybe the file(s) that define the world was/were deleted or corrupted so Minecraft couldn't find the world even though most of the data was still there?
Glad you got your world back!

Yeah i probably didn't delete the whole .minecraft folder. If i try hard to remember i think i really just deleted the world ingame, i was stupid and clicked very fast and accidentally clicked the confirming button, then i was angry and punched on the table or something lol.

You may not believe me, but what happened back in beta 1.8 was some nostalgia dream stuff.

In beta 1.5 until 1.7 i played the game normally. Had a house in the middle of a lake surrounded by some mountains and stuff.

I named the world after my name.

I was young and stupid so some day, i accidentally deleted my worlds somehow, i guess i deleted the .minecraft folder or something because of crashing or mods or something without making a backup of my saves folder.

A few weeks or months later when beta 1.8 came out, i played on a new world for a while already.

That world had also my name exactly like my lost world from 1.7.

Now on that 1.8 world i went out to explore the world generation a bit.

After a while i find that big slice in the world generation. (You know the one you often find when you play a newer version on a world that was created in an alpha or beta version, because the world generation was different between older and newer versions. Here's an example.)

However it didn't make sence for that slice to appear since i was playing on 1.8 on a new 1.8 world.

However i went along to see what's on the other side and what do i find?

The exact landscape of my world that i lost in 1.7. It was that island on the lake and even my old house was there.

I basically found my lost beta world inside my newer world. I don't know what caused this and how to replicate it but i guess my old world was still lingering somewhere in my minecraft directory and was placed in my newer world because it used the exact same name.

It's like i used McEdit to paste it there but i didn't do anything like that.

Would be cool if someone can explain this.

Hello, first of all, sorry if i made this thread in the wrong category.

I am currently playing on a new world, that i created in the old alpha version 1.2.6. What i want to do, is to play on that world and version for some time and after some weeks or month, update to the next version bit by bit, so after some time i would change the version from a1.2.6 to beta 1.0.2 to b1.1_02 to b1.2_02 and so on. And i am taking my time with that. And because of that i would like to sometimes use different texture packs.

(I'm calling them texture packs in this thread because they where called that way back then.)

So until now i made myself a 16x16 Painterly Pack and a 64x64 Misa Pack for a1.2.6 and managed to use the Misa Pack with that version by making a custom version of a1.2.6 in \.minecraft\versions and Patching its jar with the HDTextureFix_v1.1.10 from McPatcher.net. Everything works fine except i can't change the animated textures like water, lava, fire etc., which i think wasn't possible in that version anyway back then.

Now i am having a few questions and/or problems that i hope you can help me with.

Is there a certain way to tell, which version of the HDTextureFix is compatible with which minecraft beta version? I was just assuming and lucky that the HDFixv1.1.10 is working with a1.2.6.

I can't use any version of the HDTextureFix between 2.0.0 and 3.0.4_02 because i get an error message, saying that Minecraft was not found in C:\Users\MyName\Appdata\Roaming\.minecraft and then asking me to locate the game myself, which obviously doesn't work.

I am guessing that this is because the current launcher and the one we had before doesn't use the bin folder to contain the minecraft.jar file.

Also i can't make the HDTextureFix find the game by creating a bin folder and putting a minecraft.jar in it myself.

And because the even older launcher, that looks like this doesn't work anymore to download and install the game in the old way and format, it seems impossible to use the versions between 2.0.0 and 3.0.4_02.

HDFix versions after 3.0.4_02 don't work for me with the current launcher because of and error message saying

"java.io.IOException: Could not get list of launcher profiles".

I can't use OptiFine instead, because looking on the OptiFine site, the oldest version you can get is for full release 1.7.2.

So in conclusion:

1. Is there any known way or workaround to HDPatch any minecraft.jar file from version beta 1.0.2 to full release 1.6.4?

2. Can you explain or show me a good tutorial on how to change the water/lava/fire textures via texturepacks in the old formats?

3. If there is a way to get HD textures working and stuff, what about stuff like random mobs and what else the MCPatcher made possible back then?

Any good explanations or tutorials on how to do that with those old texture pack formats?

4. Yes i know, there are SOME tutorials/threads scattered around the internet about all of that but i am unable to find any definitive solutions.

I hope i was clear enough with everything and that you can help me here.

I will try to explain anything unclear and sorry if the text was unnecessarily long, but better too much than too little.