i was making my texturepack... and i updated an already in use texturepack, like i use to be able to do before 13w09a/b.
Steps to re-produce error...
Select texturepack and load a world.
go into texturepack selection menu in-game. and leave it open.
copy texturepack.zip to desktop and edit a texture.
copy back the edited file to the mc texture folder.
game crashes, as soon as used file is updated...
(it never use to do this before 13w09a/b)
Attachments
Comments 11
its not modded tho... it was downloaded and i started playing it straight away...
i havnt added anything or taken anything away from the .jar file
Sir, i can assure you, i have not modded the file... i can give you a download if you want, to prove it...
it was downloaded from mojang website and placed in /.minecraft/bin folder
It is impossible to trigger that message without a modded minecraft. Unless the crash says probably not, it is not a vanilla jar.
You have "JVM Flags: 2 total; -Xms3072m -Xmx3072m".. Care to elaborate how you have achieved that? Perhaps you have a modified launcher or a startup .bat-file, and maybe those end up starting different minecraft.jar than what you installed?
Just to be sure, I just downloaded that snapshot and force-crashed to see "Minecraft Version: 13w09b", "JVM Flags: 2 total; -Xms512m -Xmx1024m" and "Is Modded: Probably not. Jar signature remains and client brand is untouched." as expected. So you definitely have something non-standard going on.
Other than that, the activities you're doing with the texture zip are pretty much asking for trouble. By the reproduction instructions, you seem to use windows' own zip-support, which is known to be like few other side-features M$ does, crap. That is, the bundled support for zip-files in Windows is known to sometimes produce corrupted zip files.
Always manipulate the files in a directory where the zip is fully extracted into. Then compress with real programs meant for it, like 7-zip.
I am also a bit suspicious of the way you apparently update a texture "in use" on the fly, but I haven't studied that part of Minecraft at all; maybe it has been programmed to support that, it would definitely be helpful for texture pack creators.
You can reload the textures and it even supports folders for texture-packs meaning you could indeed edit in place. However windows is notorious with 'locking files' when it has them open, something any other OS doesn't have unless explicitly requested (and checked).
As the internal structure of the zip changes when you edit it, there is absolutely no way we'll ever consider this a valid bug report. We open the zip once, if you want to do things similar to this then simply unpack the texturepack into a folder and use the folder as a texturepack.
@Markku i use a .bat file to allocate more ram to minecraft... but i didnt think that would affect the minecraft.jar file... and it hasnt caused a crash before either..
and i just winRAR to compress my .zip files and i edit my texturepack in winRAR.
@Grum i did not know you could use open folders instead of .zips...
and what i do is, have a copy on the desktop of the pack that i edit, and after the file is edited. i close the .zip on the desktop, right click & copy.
then paste it in the texturepack folder, replacing the existing texturepack...
(this is how i've done texturepack making for ages now) and this is the first time i've had an error...
if my .jar file was edited would this line show it??
"Suspicious classes: No suspicious classes found."
This ticket is invalid as it relates to a modded or 3rd party client/server.
Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang.
Any plugin issues need to be addressed to the plugin creator.
This site is for addressing issues related to the base unmodded MineCraft.