Step 1: If you are using any mods that require the mod loader then the mod loader MUST be installed first. This also includes the sound mod. If you don't know how to install the modloader all you have to do is locate the minecraft.jar in the bin folder of the minecraft folder. If you are running windows you can find this folder by clicking the start button and typing run. When the next window pops up type "%appdata%\.minecraft" without quotations and it will open the minecraft folder. Then navigate to the bin folder and open it. Find the minecraft.jar and open it with a decomplier(or unzipper) like winrar or winzip. Do the same with the modloader.zip. Then transfer the files from the modloader to the minecraft.jar and delete the Meta-INF folder.
Step 2: Patch with MCpatcher but DO NOT patch each individual texture pack. The older versions of MCpatcher used to work like that.
Step 3: Drop and and all texture packs that you want to use into the texturepack folder in the minecraft folder
Step 4: Then install any other mods. If you are using a mod like the yogbox that comes with it's own installer Then you must use Optimine/Optifog instead of MCpatcher.
Note: Installing optimine/optifog is just like installing the modloader
This is awesome. Mind if I put this on the first post?
I just installed the newest version of the 128x pack, and I am having absolutely no problems. No white signs, armor, mobs, anything. Everything looks spot on. Even . . .
The ever present wheat pixels are gone! Thank goodness! Great job Dr. K! I don't know what is causing the white mobs, but there is no sign of it here!
Thanks, man! Those pixels were the devil. :dry.gif:
This is awesome. Mind if I put this on the first post?
Go ahead, it might help some people before they have to ask questions.
Oh, and I checked today. MCpatcher still creates a separate .jar file. It is now called Minecraft1.7.3.jar. So the order of installation is correct. :biggrin.gif:
One more update. Optimine/Optifog is now called OptiFine and it works even better than it did before, at least for me it does.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
Actually no, because I always have the latest version of MCPatcher. Even with Optifog/Optimine, I still have these issues. Now, I'm not saying I have the best of video cards, but this pack is the only pack that has those errors for me. I even installed a [different] 128x128 pack and everything including the entities was running perfectly normal. Also, I know how to run MCPatcher and install mods...I have been doing that forever. It's just this pack. I don't know why.
The tutorial was not aimed at you specifically. There seems to be a lot of people having issues that they are bringing here. That is why I wrote it. I apologize if I offended you. As for you issue...I have no idea. Like I said earlier, if it were a bug with the pack it self then it should appear with everyone. It is weird that you are having issues. Texture packs don't rewrite code or anything. Is there any chance you could upload a screenshot/s of what you are talking about?
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
The tutorial was not aimed at you specifically. There seems to be a lot of people having issues that they are bringing here. That is why I wrote it. I apologize if I offended you. As for you issue...I have no idea. Like I said earlier, if it were a bug with the pack it self then it should appear with everyone. It is weird that you are having issues. Texture packs don't rewrite code or anything. Is there any chance you could upload a screenshot/s of what you are talking about?
I'd love to. I'll edit this post once I get them.
These are just examples, all other mobs/entities are also white. Here they are:
Sheep:
I went back about 7 pages and couldn't find your original post so I am going to have to ask some questions that you have probably already answered. Just bear with me though, I have to ask them.
1) Do you have the latest version of either MCpatcher or Optifine?
2) Did you check the .zip file to make sure the .pngs were not corrupted?
3) (with MCpatcher) Are you patching the texture pack separately or dropping the pack into the texture pack folder?
I have a feeling the the answers will be; yes, yes and dropping in folder. If that is true then we have stretched the extent of my knowledge and ability to help. Sadly I don't know much about java or codeing in general, just what I have learned trouble shooting my own issues. Slothy would probably be able to help better but he seems to be temporarily unavailable.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
1.) I don't use Optifine, and yes, I have MCPatcher 2.1.0_02...like I said before, every other texture pack works.
2.) .png's are not corrupt.
3.) I just drop the pack into the the Texture Packs folder.
These are just examples, all other mobs/entities are also white. Here they are:
*snip* (stuff)
OK, it is clear you are using other mods other than just patching for HD textures. I have a couple questions for you not just "Are you up to date"
1. Exactly which mods are you using? I want to know EVERY single mod.
2. What order do you install the mods/patch?
3. HOW do you install the mods, with the patcher? or manually copying files into the MC.jar
Answer me this, then I will have more questions :biggrin.gif:
I found that the order in which the mods are installed is very important (ModLoader should be the absolute FIRST thing you install, even before the patcher (it does not overwrite your minecraft.jar, it simply copies it and ADDS to it. So any changes you make before patching will carry through, and also be backed up in the minecraft-1.7.3.jar (or what ever version you patch)
As I said in my earlier post, I briefly experienced the white mob bug after I reinstalled everything on my PC, and turned out I'd not quite installed the mods in the right order.
The reason order matters, is because various mods modify the same classes in the mc.jar. And if you install the wrong one first, or overwrite an important class from a mod you installed earlier, you will break things.
Lets get to the bottom of this shall we? Also please be aware that it is NOT the packs fault. The fact you are modding someone elses game instantly makes you responsible :biggrin.gif: (pretty sure most modders including the MCPatcher have a clause stating this :wink.gif: )
OK, it is clear you are using other mods other than just patching for HD textures. I have a couple questions for you not just "Are you up to date"1. Exactly which mods are you using? I want to know EVERY single mod.2. What order do you install the mods/patch?3. HOW do you install the mods, with the patcher? or manually copying files into the MC.jarAnswer me this, then I will have more questions :biggrin.gif:
*snip*
Let me tell you this. I just got a fresh new .jar, installed modloader, and then patched. Modloader was the only thing I manually installed—dragging it into the jar—so that was the only thing installed.
Now, I loaded up Minecraft, selected Bordercraft, went into my world and everything was exactly the same. All mobs/entities were all white. To answer your other questions, with my original jar, I drag in ModLoader first and then all of the others next. I don't load up Minecraft to let Modloader load first, because all of the datafiles Modloader uses are still there. Here is the usual installation order:
• Modloader
• Xray
• TooManyItems
• SlimeMod (finds slime-friendly chunks)
• SinglePlayerCommands
• Optifine (If I want to use it. I backup all my jars for easy access, so I don't have to install the mods again every time I don't want one.)
• Rei's Minimap
But this time, I just installed modloader. I even loaded up Minecraft before I patched. (Of course I closed it before I patched too :tongue.gif:)
Edit: I have just found out something quite interesting. I compared the Pig skin from SPHax's PureBDCraft (64x64), and then I put that on top of the Bordercrafts pig, and well, take a look at this.
Here it is by itself: (Dimensions 320x160)
Here it is with the SPHax pig on top (SPHax Dimensions 256x128)
Now, to me, it looks like the Bordercraft pig is the 128x128 version? And I'm using the 64x64! I'm sure this is the same way with all mobs/entities!
hmm, That shouldn't effect things. Before you could have multiple resolutions in the same pack. Otherwise incomplete packs, like mine, would look even worse.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
The last time I checked it's the same way as the terrain.png has to be: a set size.
I'm not quite sure though.
Wait... so you're using the 64x pack? hmm..
Ooo look what I found, seems the Mobs for ALL Packs are the wrong resolution all together :blink.gif:
in the vanilla textures, the pig is 64x32 (16x packs)
so in theory, the resolution of the 128x pig should be 512x256 when its actually 640x320 which is 10x the vanilla size, not 8x
and following the same logic, the 64x pig should be 256x128 as you had in Sphax's pack. BorderCraft is 320x160 (5x instead of 4)
Not sure why it still works sometimes and others not, as the resolution is just wrong :huh.gif: probably to do with the way the MCPatcher handles varying resolution packs, as you can have part 64x part 128x packs that work properly, but these are reading as 160x and 80x packs :laugh.gif:
Dr.K you will need to recheck the scale of your textures, particularly the ones with the white bug:
- Mobs
- Signs
- Boats
- Minecarts
- Rain I think
- Sun/Moon
make sure that the scale is right, so 8:1 for the 128 pack, 4:1 for the 64 and 2:1 for the 32
Seems to effect pretty much all the textures in subfolders except GUI and Armor.
Similar to the issue 42&19 had with his fonts :biggrin.gif:
EDIT: So it WAS the packs fault.. Just didn't seem like it as a few of us have never had the issue on ny of the packs
Nice to know we solved it and it wasn't just me! I would also like to confirm rain and snow, as they are white blocks as well and you can't see anything.
Nice to know we solved it and it wasn't just me! I would also like to confirm rain and snow, as they are white blocks as well and you can't see anything.
Works as intended. :tongue.gif:
In any case, I should be able to fix that by tomorrow. XD Sorry about that. I'm usually not terrible at math. :/
That's good to hear! I'd also like to report a bug with redstone wiring as there are purple particles in some of the corners.
Edit: Instead of replacing the Armor/Health bars, you should make alternate ones...like actual hearts or something. :tongue.gif: I would be easier for some of us. Edit 2: Also, I would also like to add arrows to Slothy's list. Basically anything that has a .png file XD besides terrain and items. You know what I mean. :tongue.gif:
This is awesome. Mind if I put this on the first post?
Thanks, man! Those pixels were the devil. :dry.gif:
Go ahead, it might help some people before they have to ask questions.
Oh, and I checked today. MCpatcher still creates a separate .jar file. It is now called Minecraft1.7.3.jar. So the order of installation is correct. :biggrin.gif:
One more update. Optimine/Optifog is now called OptiFine and it works even better than it did before, at least for me it does.
The tutorial was not aimed at you specifically. There seems to be a lot of people having issues that they are bringing here. That is why I wrote it. I apologize if I offended you. As for you issue...I have no idea. Like I said earlier, if it were a bug with the pack it self then it should appear with everyone. It is weird that you are having issues. Texture packs don't rewrite code or anything. Is there any chance you could upload a screenshot/s of what you are talking about?
I'd love to. I'll edit this post once I get them.
These are just examples, all other mobs/entities are also white.
Here they are:
Sheep:
Chicken:
Player w/ armor on:
Sun:
Moon:
Boat, Sign, Arrow, Minecart
Zombie
1) Do you have the latest version of either MCpatcher or Optifine?
2) Did you check the .zip file to make sure the .pngs were not corrupted?
3) (with MCpatcher) Are you patching the texture pack separately or dropping the pack into the texture pack folder?
I have a feeling the the answers will be; yes, yes and dropping in folder. If that is true then we have stretched the extent of my knowledge and ability to help. Sadly I don't know much about java or codeing in general, just what I have learned trouble shooting my own issues. Slothy would probably be able to help better but he seems to be temporarily unavailable.
2.) .png's are not corrupt.
3.) I just drop the pack into the the Texture Packs folder.
This is the only pack that has these problems.
OK, it is clear you are using other mods other than just patching for HD textures. I have a couple questions for you not just "Are you up to date"
1. Exactly which mods are you using? I want to know EVERY single mod.
2. What order do you install the mods/patch?
3. HOW do you install the mods, with the patcher? or manually copying files into the MC.jar
Answer me this, then I will have more questions :biggrin.gif:
I found that the order in which the mods are installed is very important (ModLoader should be the absolute FIRST thing you install, even before the patcher (it does not overwrite your minecraft.jar, it simply copies it and ADDS to it. So any changes you make before patching will carry through, and also be backed up in the minecraft-1.7.3.jar (or what ever version you patch)
As I said in my earlier post, I briefly experienced the white mob bug after I reinstalled everything on my PC, and turned out I'd not quite installed the mods in the right order.
The reason order matters, is because various mods modify the same classes in the mc.jar. And if you install the wrong one first, or overwrite an important class from a mod you installed earlier, you will break things.
Lets get to the bottom of this shall we? Also please be aware that it is NOT the packs fault. The fact you are modding someone elses game instantly makes you responsible :biggrin.gif: (pretty sure most modders including the MCPatcher have a clause stating this :wink.gif: )
Let me tell you this. I just got a fresh new .jar, installed modloader, and then patched. Modloader was the only thing I manually installed—dragging it into the jar—so that was the only thing installed.
Now, I loaded up Minecraft, selected Bordercraft, went into my world and everything was exactly the same. All mobs/entities were all white. To answer your other questions, with my original jar, I drag in ModLoader first and then all of the others next. I don't load up Minecraft to let Modloader load first, because all of the datafiles Modloader uses are still there. Here is the usual installation order:
• Modloader
• Xray
• TooManyItems
• SlimeMod (finds slime-friendly chunks)
• SinglePlayerCommands
• Optifine (If I want to use it. I backup all my jars for easy access, so I don't have to install the mods again every time I don't want one.)
• Rei's Minimap
But this time, I just installed modloader. I even loaded up Minecraft before I patched. (Of course I closed it before I patched too :tongue.gif:)
Edit: I have just found out something quite interesting. I compared the Pig skin from SPHax's PureBDCraft (64x64), and then I put that on top of the Bordercrafts pig, and well, take a look at this.
Here it is by itself: (Dimensions 320x160)
Here it is with the SPHax pig on top (SPHax Dimensions 256x128)
Now, to me, it looks like the Bordercraft pig is the 128x128 version? And I'm using the 64x64! I'm sure this is the same way with all mobs/entities!
I'm not quite sure though.
Wait... so you're using the 64x pack? hmm..
Ooo look what I found, seems the Mobs for ALL Packs are the wrong resolution all together :blink.gif:
in the vanilla textures, the pig is 64x32 (16x packs)
so in theory, the resolution of the 128x pig should be 512x256 when its actually 640x320 which is 10x the vanilla size, not 8x
and following the same logic, the 64x pig should be 256x128 as you had in Sphax's pack. BorderCraft is 320x160 (5x instead of 4)
Not sure why it still works sometimes and others not, as the resolution is just wrong :huh.gif: probably to do with the way the MCPatcher handles varying resolution packs, as you can have part 64x part 128x packs that work properly, but these are reading as 160x and 80x packs :laugh.gif:
Dr.K you will need to recheck the scale of your textures, particularly the ones with the white bug:
- Mobs
- Signs
- Boats
- Minecarts
- Rain I think
- Sun/Moon
make sure that the scale is right, so 8:1 for the 128 pack, 4:1 for the 64 and 2:1 for the 32
Seems to effect pretty much all the textures in subfolders except GUI and Armor.
Similar to the issue 42&19 had with his fonts :biggrin.gif:
EDIT: So it WAS the packs fault.. Just didn't seem like it as a few of us have never had the issue on ny of the packs
Works as intended. :tongue.gif:
In any case, I should be able to fix that by tomorrow. XD Sorry about that. I'm usually not terrible at math. :/
Edit: Instead of replacing the Armor/Health bars, you should make alternate ones...like actual hearts or something. :tongue.gif: I would be easier for some of us.
Edit 2: Also, I would also like to add arrows to Slothy's list. Basically anything that has a .png file XD besides terrain and items. You know what I mean. :tongue.gif:
Like I don't get it? I have the 128x128 Version working PERFECTLY.
And my friend has the 64x64 working PERFECTLY again..
I simply just don't get the Logic and why you guys are getting bugs D:
Neither do I mate, I've had all 3 work fine (except the pixel bugs) on multiple machines.. So there must be other things that trigger it.
But at the same time, as I posted above, turns out there are reasonable explanations behind it all