The Meaning of Life, the Universe, and Everything.
Join Date:
10/22/2012
Posts:
43
Minecraft:
JoeyBaboeyMan
Xbox:
Joey The Baboey
Member Details
This may not belong in Resource Pack Help, as it is relating to a texture pack, but I am playing in beta 1.7.3, and I am trying to make my own texture pack. How would I implement my own water and lava(with the flowing animations), if it is possible. I believe I have seen it done somewhere on YouTube. I already have MCPatcher installed, if it is required.
BETA 1.7.3? Whoo! Now there's something I haven't thought of in a while!
First, yes, MCPatcher IS required so good job on getting that done.
In your resource pack you'll need to create a folder called /anim/. Inside that folder you'll need vertical strips of frames named "custom_water_flowing.png", "custom_water_still.png", "custom_lava_flowing.png", and "custom_lava_still.png". If you need to change how the animation works, the MCPatcher animation format hasn't changed that much over the years. Just remember that you don't need to worry about any of the location stuff since the .properties file will be in the same folder as the animation it's using.
If you run into any problems they should be easy enough to address. I hope that helps you!
The Meaning of Life, the Universe, and Everything.
Join Date:
10/22/2012
Posts:
43
Minecraft:
JoeyBaboeyMan
Xbox:
Joey The Baboey
Member Details
It seems that I do have a problem. When I go into my world, I see the water textures for about a split second. Then I see the default Minecraft texture for the water.
It seems that I do have a problem. When I go into my world, I see the water textures for about a split second. Then I see the default Minecraft texture for the water.
That's weird. Are you sure you're using the correct version of MCPatcher for your Minecraft version? Also, are you sure you installed it correctly? Those old MCPatcher versions aren't designed to work with the current launcher you know.
Beyond that, please post the relevant files so that I can check to see if you made any mistakes.
The Meaning of Life, the Universe, and Everything.
Join Date:
10/22/2012
Posts:
43
Minecraft:
JoeyBaboeyMan
Xbox:
Joey The Baboey
Member Details
Which version should I have used? I have 5.0.3 running on my desktop right now, in case I need to patch again/ patch something else. Should I have JUST the custom textures in the anim folder, and nothing else? I can (hopefully) get the files of the textures if you need them (If I did, they would be very basic, as they are only placeholders). I am probably missing something important.
Which version should I have used? I have 5.0.3 running on my desktop right now, in case I need to patch again/ patch something else. Should I have JUST the custom textures in the anim folder, and nothing else? I can (hopefully) get the files of the textures if you need them (If I did, they would be very basic, as they are only placeholders). I am probably missing something important.
If there's even a version that runs on Beta 1.7.3 it would likely be MCPatcher 2.4.5 which is the oldest one I can find. Good luck getting it to work, though. As I said, it wasn't designed to work with the current laucher so there will be lots of moving about of jars and editing of json files involved.
I'm reasonably sure that the current MCPatcher doesn't support those old versions, though I could me wrong. If it does, make sure you've selected that profile when you go to patch.
For my file structure, would it be something along the lines of:
.minecraft
texturepacks
MyPack (zipped when used)
anim
?
Yea, that folder structure should be correct.
As for MCPatcher... yea... the current version isn't going to work. Check in the archive on Github for the older versions. I'm not sure I can help you beyond that, though, since I don't quite understand how the version .json files work... which will be important to understand if you're using the modern launcher.
May I ask why you're making a pack for Beta in the first place?
The Meaning of Life, the Universe, and Everything.
Join Date:
10/22/2012
Posts:
43
Minecraft:
JoeyBaboeyMan
Xbox:
Joey The Baboey
Member Details
About MCPatcher, I am using (what I hope to be) version 2.1.0_02, and it still won't work. I believe I am out of luck.
As for the pack, I am trying to divert my attention to the older Minecraft versions. I am doing a sort of "experiment". I am going to try my best to stay away from the new Minecraft updates, and I will go back and play the new versions after I feel a few updates have passed and that there have been many, many changes. I am not really planning to release it to the public. (It is also good experience for the future!)
Aside from that, I wonder. If I would manage to find an old version of the jar(hopefully they never used to need Json files), and patch that, would that work?
IT WORKS!!!!!!!! I am overjoyed! (Or should I say OverJoeyed?)
About MCPatcher, I am using (what I hope to be) version 2.1.0_02, and it still won't work. I believe I am out of luck.
As for the pack, I am trying to divert my attention to the older Minecraft versions. I am doing a sort of "experiment". I am going to try my best to stay away from the new Minecraft updates, and I will go back and play the new versions after I feel a few updates have passed and that there have been many, many changes. I am not really planning to release it to the public. (It is also good experience for the future!)
Aside from that, I wonder. If I would manage to find an old version of the jar(hopefully they never used to need Json files), and patch that, would that work?
Technically you already have that .jar file... it's just in the wrong place. If you take it from /.minecraft/versions/b.1.7.3/, rename it "minecraft.jar" and put it into /.minecraft/bin/, then MCPatcher (the old one) should detect and patch it normally. Where the hickup comes is putting it back since if you just reverse the process Minecraft will detect that the .jar file isn't the way it's supposed to be and just re-download it for you; believing it to be corrupt.
That's where editing the .json files comes in. You'll need to change something to tell the launcher that the weird .jar is fine and that it doesn't need to do anything. How to do that... I don't know. If you patch a newer version with the newer MCPatcher and look at the folder and .json file it generates you might be able to figure it out by comparing them. Best wishes on that.
The Meaning of Life, the Universe, and Everything.
Join Date:
10/22/2012
Posts:
43
Minecraft:
JoeyBaboeyMan
Xbox:
Joey The Baboey
Member Details
I thought it would use the custom_blablablawhatever files. I wish I could have been on Minecraft since then. Unfortunately, however, the Old Launchers cannot connect to Minecraft.net, so no logging in for me:(
I need to invent time travel, so I could go back in time to those old versions.
And thanks for all of the help
I was inspired to do all of this because of one of the firstMinecraft videos I have ever watched.
(And then I rewatched it today, after relentlessly searching for it)
I thought you meant the textures in general. My bad.
If it's not showing the custom files then it's not patched with MCPatcher. This is what I meant. You patch it, run it, the laucher sees that the .jar is different from what it expects, and so it downloads a fresh copy for you. The game still runs, but it's no longer patched. You either need to use the old laucher (which means no login) or mess with the .json files to prevent a redownload.
Old versions of Minecraft will use the base textures from the terrain.png when they detect a texture pack. This is why people who really liked their custom animations used to write "Use MCPatcher N00b!" in those spaces instead of having an actual water texture.
This may not belong in Resource Pack Help, as it is relating to a texture pack, but I am playing in beta 1.7.3, and I am trying to make my own texture pack. How would I implement my own water and lava(with the flowing animations), if it is possible. I believe I have seen it done somewhere on YouTube. I already have MCPatcher installed, if it is required.
Image Removed
BETA 1.7.3? Whoo! Now there's something I haven't thought of in a while!
First, yes, MCPatcher IS required so good job on getting that done.
In your resource pack you'll need to create a folder called /anim/. Inside that folder you'll need vertical strips of frames named "custom_water_flowing.png", "custom_water_still.png", "custom_lava_flowing.png", and "custom_lava_still.png". If you need to change how the animation works, the MCPatcher animation format hasn't changed that much over the years. Just remember that you don't need to worry about any of the location stuff since the .properties file will be in the same folder as the animation it's using.
If you run into any problems they should be easy enough to address. I hope that helps you!
It seems that I do have a problem. When I go into my world, I see the water textures for about a split second. Then I see the default Minecraft texture for the water.
Image Removed
That's weird. Are you sure you're using the correct version of MCPatcher for your Minecraft version? Also, are you sure you installed it correctly? Those old MCPatcher versions aren't designed to work with the current launcher you know.
Beyond that, please post the relevant files so that I can check to see if you made any mistakes.
Which version should I have used? I have 5.0.3 running on my desktop right now, in case I need to patch again/ patch something else. Should I have JUST the custom textures in the anim folder, and nothing else? I can (hopefully) get the files of the textures if you need them (If I did, they would be very basic, as they are only placeholders). I am probably missing something important.
Image Removed
If there's even a version that runs on Beta 1.7.3 it would likely be MCPatcher 2.4.5 which is the oldest one I can find. Good luck getting it to work, though. As I said, it wasn't designed to work with the current laucher so there will be lots of moving about of jars and editing of json files involved.
I'm reasonably sure that the current MCPatcher doesn't support those old versions, though I could me wrong. If it does, make sure you've selected that profile when you go to patch.
For my file structure, would it be something along the lines of:
.minecraft
texturepacks
MyPack (zipped when used)
anim
?
Image Removed
Yea, that folder structure should be correct.
As for MCPatcher... yea... the current version isn't going to work. Check in the archive on Github for the older versions. I'm not sure I can help you beyond that, though, since I don't quite understand how the version .json files work... which will be important to understand if you're using the modern launcher.
May I ask why you're making a pack for Beta in the first place?
About MCPatcher, I am using (what I hope to be) version 2.1.0_02, and it still won't work. I believe I am out of luck.
As for the pack, I am trying to divert my attention to the older Minecraft versions. I am doing a sort of "experiment". I am going to try my best to stay away from the new Minecraft updates, and I will go back and play the new versions after I feel a few updates have passed and that there have been many, many changes. I am not really planning to release it to the public. (It is also good experience for the future!)
Aside from that, I wonder. If I would manage to find an old version of the jar(hopefully they never used to need Json files), and patch that, would thatwork?IT WORKS!!!!!!!! I am overjoyed! (Or should I say OverJoeyed?)
Image Removed
Technically you already have that .jar file... it's just in the wrong place. If you take it from /.minecraft/versions/b.1.7.3/, rename it "minecraft.jar" and put it into /.minecraft/bin/, then MCPatcher (the old one) should detect and patch it normally. Where the hickup comes is putting it back since if you just reverse the process Minecraft will detect that the .jar file isn't the way it's supposed to be and just re-download it for you; believing it to be corrupt.
That's where editing the .json files comes in. You'll need to change something to tell the launcher that the weird .jar is fine and that it doesn't need to do anything. How to do that... I don't know. If you patch a newer version with the newer MCPatcher and look at the folder and .json file it generates you might be able to figure it out by comparing them. Best wishes on that.
I found a beta 1.7 jar file here: http://www.minecraftforum.net/forums/minecraft-discussion/discussion/173960-minecraft-jars
I renamed it, and I patched it. Sure enough, it works. For some reason, however, I believe it is using the textures from terrain.png
But if it isn't broken, don't fix it!
Image Removed
Glad it worked for you!
Also... where did you expect it to draw textures from? That's how we used to make texture packs back in the day.
I thought it would use the custom_blablablawhatever files. I wish I could have been on Minecraft since then. Unfortunately, however, the Old Launchers cannot connect to Minecraft.net, so no logging in for me:(
I need to invent time travel, so I could go back in time to those old versions.
And thanks for all of the help
I was inspired to do all of this because of one of the firstMinecraft videos I have ever watched.
(And then I rewatched it today, after relentlessly searching for it)
Image Removed
I thought you meant the textures in general. My bad.
If it's not showing the custom files then it's not patched with MCPatcher. This is what I meant. You patch it, run it, the laucher sees that the .jar is different from what it expects, and so it downloads a fresh copy for you. The game still runs, but it's no longer patched. You either need to use the old laucher (which means no login) or mess with the .json files to prevent a redownload.
Old versions of Minecraft will use the base textures from the terrain.png when they detect a texture pack. This is why people who really liked their custom animations used to write "Use MCPatcher N00b!" in those spaces instead of having an actual water texture.
Wow, thanks for all of the information and help! (That is probably a generic response, oops!)
Image Removed