[[ UPDATE : 1.6.2 ]]
[Error]
"Hot-Patching" a Resource Pack makes it unusable in until the Client Closes.
[Notes]
Same instructions as below, but without the crash.
----------------
[Error]
If you "Hot-Patch" a Resource Pack, the Game Crashes when you try to render the new Data.
[Duplication]
• Open Minecraft and Select a Resource Pack (Example "ZIP")
• Start a Single Player Game / Join Multiplayer****
• Edit a "Out-of-Folder" copy of Resource Pack.
• Copy new zipped file to Resource Pack directory (Confirm Override0
• Minecraft : Open Resource Pack Menu
• Select Default
• Wait for Workload to complete
• Select Zip Resource Pa-CCCCCRASH (Sad Faces all around)
[Notes]
• This used to work before 1.6
• My process / workflow for edits is this :
Fire up Minecraft and look at Textures (usually in Flat World)
Edit the files one by one as needed
Re-Zip file in my Development Directory
Copy Zip File to Minecraft Directory
Switch to Default, wait a few Seconds, Switch Back
View new Content
Adjust as needed (Repeat Steps until pack is updated)
• Completely logging out and quitting the Game works, but the process is FAR to long, especially for super fast edits to tweak the smaller things (like Pixel adjustments)
• 2x Crash Notes Attached (Yes, my Resource Pack is called Zip until done and ready to be shipped).
[Resource File Notes]
• 16x16
• Textures Only (No Sound, Lang, etc)
• FileList Mirrors 1.6.1 FileList (Textures only)
• PNG Files are 32-bit/unCompressed
[Notes]
• If you need anymore data, let me know.
Linked issues
is duplicated by 4
Attachments
Comments 4
@Ezekiel
It doesn't crash but it still locks out the Resource Pack. I can click to another Pack, such as Default or another, but won't let me reSelect the file I had overwrote. (I'll update the ticket after this is posted).
Use a folderbased resourcepack (just unpack your Zip.zip into a folder called: "Zip" inside of the resourcepack folder). Windows locks files while you have them open, we keep them open ingame to read from.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.