[MC-3466] Texture Pack editing problem Created: 19/Nov/12  Updated: 13/Dec/12  Resolved: 19/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.4
Fix Version/s: None

Type: Bug
Reporter: idontwantthemtoknow Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None

Confirmation Status: Unconfirmed

 Description   

When editing a texture pack and putting the edit in the texture pack it fails

What I expected to happen:
The edit would go into the folder, overwriting the previous file and work fine

What actually happened:
It would screw up and not work

How to do:
1. Make a texture
2. Put the texture in the pack
3. Open Minecraft
4. Try to put an edit in the pack

Demonstration: http://youtu.be/lLIWEFqEqkQ (not my computer)



 Comments   
Comment by insomniac_lemon [ 13/Dec/12 ]

You need to use a texture pack folder. It's just like zipped only contained in a folder (not a .ZIP archive) and needs a pack.png and pack.txt for Minecraft to actually find it.

Then, you can modify and save the files while the game is running (even if you're in a world). After you make the changes press f3+t in game and the textures will reload from the folder, and you will see the changes occur right before your eyes!

Comment by Kumasasa [ 21/Nov/12 ]

But all texture pack files are locked while running Minecraft, not only the texture file currently in use.

Comment by [Mojang] Grum (Erik Broes) [ 19/Nov/12 ]

I do not see the issue; Windows 'locks' files for change when they are in use. Nothing you can do about that.

Comment by Jonathan Haas [ 19/Nov/12 ]

Editing a texturepack on the fly is only supported when not using a zipped pack. So unzip it first before starting the game.

Comment by idontwantthemtoknow [ 19/Nov/12 ]

You cannot put edited textures in the pack without closing Minecraft

Comment by Jonathan Haas [ 19/Nov/12 ]

Your descriptions are very unspecific. "It would screw up and not work" or "Put the texture in the pack".

Are you replacing files? Which? What exactly are you doing? What screws up and how?

Generated at Sun Jan 12 12:01:19 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.