[MC-17947] 13w24b - Animation Metadata Array out of bounds

I ran a search for "Animation Metadata" and did not return any results for this particular message.

Upon loading the game, with my resource pack, some, but not all animations return errors due to an Array out of bounds. Those particular textures will appear as missing (purple/black) when in game.

Error:
"Unable to parse animation metadata from minecraft:textures/blocks/redstone_block.png
java.lang.ArrayIndexOutOfBoundsException"

This was my texture pack converted with the Ender tool and it does work in 13w24a with out any errors. Only since 13w24b, some animations return this error.

Attached you will find the dump from the dev console after the game is launched with the resource pack loaded, one .png texture thats offending and its mcmeta file.

Linked issues

duplicates 1

MC-17936 Some animated textures only show the placeholder texture Resolved

is duplicated by 1

MC-17869 Animated textures not following original settings Resolved

Attachments

13w24b - Animation Metadata Array out of bounds.txt

redstone_block.png.mcmeta

Comments 4

Jonathan Vernon 2013-06-15T01:49:27Z

I do believe there is no '0' frame (At least it was like that before)

kumasasa 2013-06-15T09:46:44Z

~~You have a trailing comma after the "2":~~
Disregard this comment... Was a wrong information.

Ron F. 2013-06-15T11:16:18Z

Thanks Kumasasa. My animations were converted by the ender tool. I'm still getting used to this new format. Ill follow up on that thread.

Ron F. 2013-06-18T11:31:54Z

Kumasasa - After removing the trailing comma, I received a different error.

Jonathan - You lead me in the correct direction. Apparently, snapshot 13w24a and prior allowed mcmeta (and texts) files to list more frames than there were in the image. In the example above, I had 0-7 (8 frames), where as the image only has 7. Removing the reference to 7, resolved the issue. So as of 13w25a, 0 is still a valid index start.

Thanks to both of you for your help.