The download doesn't work anymore, so I did some Googling and found the Beta 1.8 version of the texture pack. I uploaded it to MediaFire so that anyone who comes across this post like I did can get a copy of the texture pack or possibly continue the pack since it has been abandoned.
I am trying to create custom step and dig sounds for my slime block. I can get the same sounds to play with a direct method call to playSoundAtEntity. Those sounds are located in assets.slimycraft.sound, but the dig and step sounds are located in assets.slimycraft.sound.dig and assets.slimycraft.sound.step, respectively (they're a copy of the same files). Right now, it is silent when digging up or walking over the block. You can view the code that I have at my GitHub repository in Slimeycraft.java, BlockSlime.java, and Slimycraft_EventSounds.java. Does anyone have any ideas as to how i could make this work? I have a hunch that it might have to do with the syntax of
Thank you for your response! I got the ash to have the thinness of snow by copying over the call to setBlockBounds. Now it responds to gravity and is thin. This created a new problem, though: when an ash block falls on top of another, it drops the ash block as an item, just like sand falling onto a torch. I want the ash block to be unobtainable in survival, so is there a way to change that behavior so that it drops an ash item which is not a block? The anvil replaces the block, which is not what I want, but demonstrates that it doesn't have to drop the block as an item even though it extends Block.Sand. I cannot find anything in the Block.Anvil class that accomplishes this, however. Does anyone have any ideas?
Finally, I cannot find the onBlockDestroyed method. I did find onBlockDestroyedByPlayer and onBlockDestroyedByExplosion, but those don't work for fire.
I am trying to make a Forge mod that makes it so that when fire burns a block away the block is replaced with an ash block from my mod rather than air. How can I do this without editing the base class Block.Fire? I also want to have the ash block have the thinness of snow (not the crafted snow block, the snow that falls) and the gravity-response of sand. I have the gravity worked out by making the block an extension of Block.Sand, but how can I also make it have the thinness of snow? I can't seem to find which part of Block.Snow makes it thin. Also, if I did this, would I need a new entity that extends Entity.FallingSand so that the entity model is thin as well?
Thanks so much When I edit there is a picture with blocks all on it sprites I guess do I edit them on that?
Yes. Some of the texture files are redundant, so I just edit all of them in case it changes in an update. The 'terrain.png' holds the textures that are used on the blocks in the world and in your hand. The 'gui_blocks.png' holds the textures that show up in your hotbar and in the block selection screen. The 'gui.png' has the textures for the hotbar and block selection screen themselves, as well as the buttons. Some of the textures are just there because this is a port from the Pocket Edition, so you don't need to edit those, such as the buttons that would be used on a touchscreen to move around.
Nice! I'm getting into making Texture packs. How do I get started?
When I started out, I downloaded a few different texture packs that I liked and tried tweaking them a bit. Then I messed around with various image editing tools until I got to the point where I could make textures that were almost halfway-descent representations of what they were supposed to be. It takes time and skill. The problem for me is that I have neither. If you have one or both of these things, you might be able to create a texture pack that you can release (I can't release mine because I have adapted textures from other packs for the textures that I couldn't get to look right). Go with what feels right and looks good to you. Also, try to update it frequently and as soon as possible after the Minecraft updates. This isn't too hard if you download and test the snapshots. Most importantly, make sure that it is something that you enjoy. If you find that you don't like spending endless hours tweaking that one pixel to get it right, then don't. I don't. I go for a "it's good enough" approach. Oh, and by the way, good luck. You'll need it.
Some HD textures will work with Minecraft Pi Edition without a patcher. As far as I know, no one has released a patcher for MCPI. I have not tested any packs, but it looks like at least 32x textures will work for at least the 'terrain.png'; it doesn't look like other files have been tested. More info at this link: http://www.minecraftforum.net/topic/1620010-texture-packs-for-mcpi/ If you try an entire HD texture pack on the Pi edition, please post back here with the results as I (and probably many other people) would be interested in seeing what you can do with it. Maybe try it with the 64x pack you are working on?
Extract the archive. If you're on Linux, you can most likely use the built in archive utility. If you're on Windows, you need to download a 3rd party program. I used 7-Zip for this.
Copy the 'images' folder to somewhere else so you can edit it. It is in 'mcpi/data'.
Edit the textures to your liking, or copy and paste from a texture pack that you have already made. Minecraft Pi Edition includes textures in the 'terrain.png' and 'items.png' files, for instance, that do not appear in the PC version so make sure that you edit it to include these textures if you just copy the files over. Also, you can use some of the files from a Pocket Edition texture pack as it is very similar to Minecraft Pi Edition (but not identical).
The biggest difference in the textures between the Pi Edition and the PC edition is the 'gui_blocks.png' file. Like the Pocket Edition, the Pi Edition uses this file (located in the 'gui' folder) to hold textures of 3D views of each block for the GUI. There is a great tutorial for how to create these textures easily at http://www.minecraft...locks-properly/.
IMPORTANT: When you save the png files after editing them, make sure that they are in 32-bit format. I tried to use a 24-bit format and it used the textures incorrectly. You can use a program such as Paint.NET (Windows only) or GIMP to do this.
Copy the contents of the images folder with the edited files that you have created to the 'images' folder in the location where you extracted the rest of the game files to in step 2.
Launch the game. Your textures should now be applied. If the game doesn't use your textures the first time, try restarting it. If this doesn't work, you probably did something wrong. If you have problems, try deleting all of the other terrain files in the 'images' folder except for the png.
For distribution, you can compress the textures into a zip file. Be sure to tell your users how to install the pack (step 7). Delete any metadata files from the archive (such as Thumbs.db).
If you have problems and you are sure that you followed all of these steps, feel free to post your issue in this thread. I will try to respond as soon as possible and help you to the best of my abilities.
Edit: Make sure that your image editor supports transparency. Don't use Microsoft Paint because it doesn't support it.
The concept isn't bad, but the brightness of those colors is too intense. If you toned it down a little but kept the cartoon-ish elements, I think you would get much broader appeal.
Reason number 4 is not really a reason. We can't censor everything just because there are people out there who don't like it. We have to decide which things are legitimately offensive, and which are not. Things that are legitimately offensive are things which attack people. We could just as easily say that redstone must be removed because it is too much like electricity and this offends the Amish (not that they would play Minecraft anyway for obvious reasons). And by the way, there aren't any real witches to offend with the stereotype. Witches aren't real. End of story. Wiccans also aren't witches. You know that they can't actually do magic, right? It's just a religion. And no, I don't have to respect anyone's belief that they can do magic any more than I have to respect the beliefs of people who believe in unicorns, leprechauns, Bigfoot, astral projection, hypnotism, alien abductions, astrology, dowsing, tarot, or the Loch Ness monster. There is no evidence for any of those things, so I can legitimately say that they aren't real. It wouldn't offend me if any of those things were added to Minecraft anyway because it's a game, it's not supposed to be real. End of story. Can we move on, please to the real discussions about whether or not witches fit with the mechanics and feel of Minecraft?
This texture pack has been removed by me (the creator) because it used many textures appropriated from other packs even if they specifically requested that no one use their textures and that no permission would be given. I believe that things that are free like free beer should be free like free speech. Since I am not making any money off of their work, I should be able to redistribute and modify anything they release for free as much as I want as long as I give them credit, which I do. Unfortunately for those of us whose minds are not enslaved by the abusive system that is intellectual property law, our overlords do not agree. With this in mind, I have removed the pack from this forum post. If you still want it, feel free to send me a message on the forums. So far, the courts have ruled that I can tell you where to get this content, but I can't host it here. Fine. And to the makers of these packs: Really? Are you really so insecure that you think that my using your textures would hurt you because people would abandon your texture pack for mine? And is that a bad thing? You get credit for the texture, and people get a pack that they like better (or not, and they like yours better and you have nothing to complain about). What ever happened to freedom of choice? I will not sacrifice quality for uniqueness. I will not bow down to these people who think that they are better than us because they can make a 16 x 16 square look pretty. If you don't like that I am still using your textures or derivatives of them, sue me. Bring it on. I'll be ready.
0
0
Download Link
0
event.manager.addSound("slimycraft.dig:slime1.ogg");0
Finally, I cannot find the onBlockDestroyed method. I did find onBlockDestroyedByPlayer and onBlockDestroyedByExplosion, but those don't work for fire.
Thanks for your help.
0
0
Yes. Some of the texture files are redundant, so I just edit all of them in case it changes in an update. The 'terrain.png' holds the textures that are used on the blocks in the world and in your hand. The 'gui_blocks.png' holds the textures that show up in your hotbar and in the block selection screen. The 'gui.png' has the textures for the hotbar and block selection screen themselves, as well as the buttons. Some of the textures are just there because this is a port from the Pocket Edition, so you don't need to edit those, such as the buttons that would be used on a touchscreen to move around.
0
When I started out, I downloaded a few different texture packs that I liked and tried tweaking them a bit. Then I messed around with various image editing tools until I got to the point where I could make textures that were almost halfway-descent representations of what they were supposed to be. It takes time and skill. The problem for me is that I have neither. If you have one or both of these things, you might be able to create a texture pack that you can release (I can't release mine because I have adapted textures from other packs for the textures that I couldn't get to look right). Go with what feels right and looks good to you. Also, try to update it frequently and as soon as possible after the Minecraft updates. This isn't too hard if you download and test the snapshots. Most importantly, make sure that it is something that you enjoy. If you find that you don't like spending endless hours tweaking that one pixel to get it right, then don't. I don't. I go for a "it's good enough" approach. Oh, and by the way, good luck. You'll need it.
0
Some HD textures will work with Minecraft Pi Edition without a patcher. As far as I know, no one has released a patcher for MCPI. I have not tested any packs, but it looks like at least 32x textures will work for at least the 'terrain.png'; it doesn't look like other files have been tested. More info at this link: http://www.minecraftforum.net/topic/1620010-texture-packs-for-mcpi/ If you try an entire HD texture pack on the Pi edition, please post back here with the results as I (and probably many other people) would be interested in seeing what you can do with it. Maybe try it with the 64x pack you are working on?
1
- Download Minecraft Pi Edition from http://pi.minecraft.net/
- Extract the archive. If you're on Linux, you can most likely use the built in archive utility. If you're on Windows, you need to download a 3rd party program. I used 7-Zip for this.
- Copy the 'images' folder to somewhere else so you can edit it. It is in 'mcpi/data'.
- Edit the textures to your liking, or copy and paste from a texture pack that you have already made. Minecraft Pi Edition includes textures in the 'terrain.png' and 'items.png' files, for instance, that do not appear in the PC version so make sure that you edit it to include these textures if you just copy the files over. Also, you can use some of the files from a Pocket Edition texture pack as it is very similar to Minecraft Pi Edition (but not identical).
- The biggest difference in the textures between the Pi Edition and the PC edition is the 'gui_blocks.png' file. Like the Pocket Edition, the Pi Edition uses this file (located in the 'gui' folder) to hold textures of 3D views of each block for the GUI. There is a great tutorial for how to create these textures easily at http://www.minecraft...locks-properly/.
- IMPORTANT: When you save the png files after editing them, make sure that they are in 32-bit format. I tried to use a 24-bit format and it used the textures incorrectly. You can use a program such as Paint.NET (Windows only) or GIMP to do this.
- Copy the contents of the images folder with the edited files that you have created to the 'images' folder in the location where you extracted the rest of the game files to in step 2.
- Launch the game. Your textures should now be applied. If the game doesn't use your textures the first time, try restarting it. If this doesn't work, you probably did something wrong. If you have problems, try deleting all of the other terrain files in the 'images' folder except for the png.
- For distribution, you can compress the textures into a zip file. Be sure to tell your users how to install the pack (step 7). Delete any metadata files from the archive (such as Thumbs.db).
- If you have problems and you are sure that you followed all of these steps, feel free to post your issue in this thread. I will try to respond as soon as possible and help you to the best of my abilities.
Edit: Make sure that your image editor supports transparency. Don't use Microsoft Paint because it doesn't support it.0
The concept isn't bad, but the brightness of those colors is too intense. If you toned it down a little but kept the cartoon-ish elements, I think you would get much broader appeal.
0
0
0
0