Minecraft Forums

If you're reading this thread, it's likely you're either having problems with the new block and item animation format introduced in Minecraft 1.6, or, are new to making animations for Minecraft and want to learn how with as few problems as possible.

Tip: Watch for Green Text: When I write tutorials, I add little tidbits in green text lines. These are often helpful hints or little extras. Keep an eye out for them, as they may prove helpful.

Tip: Look Familiar?: Look Familiar?: If a lot of this tutorial looks familiar, that's because it should be. A lot of this is copy-pasted directly from the previous tutorial: "Making Animated Blocks and Items: The Minecraft 1.5 Way!" If you read that tutorial, and are familiar with the concepts shown in it, scroll down to "Understanding .mcmeta Files" below. Thats' where the bulk of the 1.6 changes are mentioned. Also, if I missed a mention of a .txt file, please point that out so I can edit it. I tried to get everything right, but I'm not perfect.

IMPORTANT: THIS IS ONLY FOR BLOCKS AND ITEMS: If you're trying to animate anything that is not a block or an item (including blocks whose textures are in the /entity/ folder which are rendered as entities and not blocks) you'll need to use MCPatcher and its animation format.

1. The Animation Strip Format:
The basic format of an animation is a column of frames. Each individual frame should be the same width and height as the texture you're attempting to animate. For example, if your texture pack is 16x16, each frame in the column should also be 16x16.

Tip: I'm working in 16x16: In all of the examples on this thread, all of the frames are supposed to be at 16x16 resolution. While some, like the image above, are kept at their native resolution (to save on scrolling), I've optimized most of the images for maximum visibility. Don't let this confuse you later on.

In this example, each frame is numbered so you can see its position in the stack. Animated in-game, it will look something like this:



Tip: Starting With Zero: Why is the top frame of an animations strip numbered 0? Because a programmer made the system. In the minds of programmers, zero is the first number in a sequence, preceding the number one. It takes us artsy types a little bit of practice to get use to starting a count with zero, but that's just how computers (or at least computer programmers) work so we'll just have to deal with it.

2. Understanding .mcmeta files:

Every animation in Minecraft must have an accompanying .mcmeta file with it. If it doesn't, Minecraft won't properly read the animation file, and you'll get something that looks like this in game:



Obviously, this is undesirable.

IMPORTANT: READ THE SPOILER ASSOCIATED WITH YOUR OPERATING SYSTEM: Certain operating Systems have behaviors that may prevent you from changing your file extensions easily. If you don't change your files properly, you will have files that have a hidden .txt extension at the end, which will cause Minecraft to ignore your file, believing that it is not a .mcmeta file. For example, you should have "obsidian.png.mcmeta", but with file extensions hidden you may actually have "obsidian.png.mcmeta.TXT" and not even know it. This is why a lot of .mcmeta file fail, so please don't make this mistake.

IMPORTANT: SAVE AS PLAIN TEXT: The simpler the the text editor you use to make these files, the better. Programs like Notepad and Notepad++, which have no text formatting, are best. Other programs, like Window's Wordpad and Mac's Text Edit require that you change the file format to Plain Text. Higher-end programs like Open Office and MS Word may have different names for this, or not work at all. Even if the file is a .txt, if the file format itself isn't correct, Minecraft won't read it, and it'll just as if you didn't have a .mcmeta file at all!

The name of this .mcmeta must match the name of your animation's .png file EXACTLY! This is REALLY important, and is different from how the 1.5 format worked.

For a .mcmeta file, the extension must be after the ENTIRE file name of the image. For example "obsidian.png" gets a file called "obsidian.png.mcmeta", but with file extensions hidden you may actually have "obsidian.png.mcmeta.txt" and not even know it. This is why a lot of .mcmeta files fail, so please don't make this mistake.

IMPORTANT: MATCH YOUR FILE NAMES EXACTLY: I can NOT stress how important it is to be studious about matching your file names. Minecraft is a program, and like most programs, will not try to guess your intentions. Just as you must match file names exactly if you want Minecraft to figure out which texture in a pack it's supposed to call, the .mcmeta file accompanying your animation's file must also match exactly. Capitalization, underscores, and the .png in the middle are ALL IMPORTANT!

Every .mcmeta file MUST be in the same folder as the .png file that it goes with. If you're animating a block, it should be in /textures/blocks/. If you're animating an item, it goes in /textures/items/.

The Basic Setup:

At it's most basic, the .mcmeta file will contain an instruction that let's Minecraft know that this is supposed to be an animation file. This is important as Minecraft has multiple types of .mcmeta files, and it is important the Minecraft knows which is supposed to do what. The obvious comparison is to the pack.mcmeta which is in the root of your resource pack. That file has a different, though similar, setup to an animation's .mcmeta

At it's most basic, an animation's .mcmeta will look like this:

{ "animation": { } }

With this setup, the animation will run from the first frame to the last frame, at the rate of 20 frames per second. This is the default behavior for all Minecraft block and item animations. To learn to change this, see the sections below.

Unlike in the 1.5 setup, you can not simply leave a .mcmeta file blank and expect that it is going to work.

Adjusting Framerate:

Not all animations are designed to run at a rate of 20 fps. You can adjust the rate an animation moves very easily in the 1.6 .mcmeta format. This is one of the big advantages of the new format, in that you can adjust timing without having to list every frame individually, saving a lot of time.

First, start with the basic setup shown above:

{ "animation": { } }

See the set of brackets after "animation":? That's where we're going to put our timing information. Add the following in between those brackets:

"frametime": 4

The entire thing together should look like this:

{ "animation": {
"frametime": 4
} }

Tip: Spacing Doesn't Matter: One thing that confuses people is the way that Dinnerbone's Texture Ender lays out the animation files. They wonder if the text needs to be laid out like that. The answer is "No, it doesn't". In many of these examples, I'll have the text layed out in an outline style to make it easier to read. This is totally unnecessary as everything can be put into a single line. For example, the above animation can be in three lines like it is above, or a single line like this: { "animation": { "frametime": 4 } } Both versions will work without issue.

Here are a couple of examples of how this will work with your animation:



This red animation uses the default timing of 1 frame per tick (20 frames per second). Notice how quickly it moves?



This blue animation, on the other hand, uses the frametime attribute to slow the animation down to 1 frame per 20 ticks (1 frame per second). See how it moves much slower? When adjusting frametime (or an individual frame's "time" attribute as shown below) higher numbers are slower and smaller numbers are faster. Keep in mind that 1 frame per tick is as fast as an animation will go, and you can only use whole numbers.

Changing Frame Order:

Going back to the first example, the yellow numbered block, you can see that frames are in order starting with frame number 0. What do you do if you want to change the order of these frames, or use a singe frame more than once in the course of an animation? Well, you could make a very long animation strip that has redundant frames... but that's very wasteful and will use up a LOT of memory needlessly. That would be a bad idea.

Instead, we can use the .mcmeta file to adjust the order of the frames. Here's an example:

By using these six frames, numbered 0 - 5, we can make an animation that fills the bar and then depletes it without having to actually animate the second half of the animation.

To adjust frame order, we'll need to add a new attribute where "frametime": was added in the previous section. This one is called "frames":, and is significantly more complicated.

Again, start with the basic setup, and add the following in the brackets after "animation":

"frames": [ ]

IMPORTANT: CHECK YOUR BRACKETS: It's important to note that for most things in these .mcmeta files, you'll be using curved brackets like these: { }. However, for the Frames attribute, you'll need to use square brackets like these: [ ]. Getting this one little detail wrong will cause Minecraft to disregard your .mcmeta file, and give you checkerboard blocks.

After you've added that, your .mcmeta file should look like this:

{ "animation": {
"frames": [ ] } }

This alone will not do anything. You must actually list the frames in the order that you want them to appear, separated by commas. Here's our green-block example:

{
"animation": {
"frames": [
0,
1,
2,
3,
4,
5,
4,
3,
2,
1
]
}
}

Tip: Watch the Ends: In the above example, notice how I don't end the sequence with 0? This is because the animation repeats starting with the beginning. If there were a 0 at each end, it would be in the sequence twice in a row and thus would display for double the amount of time. Be mindful of this if you cycling animations seem to hang on one frame. If you're having a problem, ask yourself "would this make sense if I put the exact same sequence of numbers in there twice?" If you answer "No, because a number would repeat without a good reason", then you have a redundant number at the end.

As you can see, the frames go in order starting with frame 0 until it get to the last frame of the strip (number 5), and then proceeds to decrease in number, running the frames backwards until it reaches 1. Here's the result in convenient animated format:

IMPORTANT: DO NOT GO BEYOND THE END OF THE STRIP!: What happens if you accidentally put a 6 after the five in that example? Well, there's no frame with that number in that strip (six frames means 0-5). This will most likely confuse Minecraft and cause the animation to fail. Remember that zero is your first number and that it counts as much as any other.

IMPORTANT: NO COMMA AFTER THE LAST NUMBER: An important thing to note is that there's no comma after the last 1 in that example. This is VERY important. The commas tell Minecraft that there's more to follow. By including a comma after the last frame, you're telling Minecraft that there's more frames... and then leaving it hanging. Minecraft is really picky when it comes to .mcmeta files, and adding that comma will cause the entire animation to fail, resulting in checkerboard blocks. Keep that in mind.

Adjusting Frame Delay:

Now you know how to change the speed that the animation runs, and how to change the order in which the frames are presented. But what happens if you want a single frame to be visible for a different amount of time than the rest of the animation? Well, you could list it multiple times in a row to drag it out... but that doesn't work if you want to make one faster.

Instead, you can use your handy .mcmeta file to adjust the timing of a single frame.

For starters, you will need to have your frames laid out in the same manner as above, with them listed in the order you want them to be displayed. You must do this even if you want them to run in the default order.

{ "animation": { "frames": [ 0, 1, 2, 3, 4, 5, 6 ] } }

Now that you've gotten that far, replace the frame number that you want with the following bit of code:

{ "index": 3, "time": 20 }

The number following "Index": is which frame of the animation strip you want it to display. This is basically the same thing you learned to do in the last section, but in a longhand variation. Obviously the number following "time": is how many ticks (1/20 second incriments) you want that frame to be displayed for.

So for this example, we want the animation to run in the default order, at the default speed... except for frame #3 which we want to stick around for a full second. The .mcmeta file would now look like this:

{
"animation": {
"frames": [
0,
1,
2,
{
"index": 3,
"time": 20
},
4,
5,
6
]
}
}

Notice that there's a comma after the bracket surrounding the index and time attributes. Effectively, everything between those two brackets is just replacing the number. This also means that if you're adjusting the last frame in this method, you will NOT have a comma after the bracket.

Putting It All Together:

As you can see, by adding various things to the basic setup you can adjust anything that you want to with your animation. You can make it run faster or slower, have the frames run in a different order than they are in your animation strip, re-use frames multiple times, and adjust the timing of an individual frame.

But can you do them all in the same .mcmeta file? YES! Actually, you can! Here's an example of that:

{ "animation": { "frametime": 2, "frames": [ { "index": 0, "time": 40 }, 1, 2, 3, 4, 5, 6, 4, 2 ] } }

In this example the animation runs at a rate of 10 frames per second (one frame every 2 ticks). The first frame, numbered zero, stays visible for two seconds. After that frame, the animation runs in order from frame 1 to frame five, where it runs in reverse skipping every other frame.

With these few basics, you can make animations WAY more complicated than this, but this is as far as we'll go for this tutorial. If you have any questions, don't be affraid to post!


3. Flowing Liquids:

While most animations follow the above format and rules, there are a few exceptions. The two biggest are Flowing water and lava. These two files follow a special set of rules when it comes to laying out your animation sheet. Don't worry, once you understand them they're pretty easy. It's just a few extra steps.

IMPORTANT: FLOWING LIQUIDS ONLY: This only applies to water_flow.png and lava_flow.png (and presumably other mod-added liquids). The still water and lava files follow the same format as any other block, as outlined above. Do NOT do the stuff in this section with your still liquids. It will end up looking really weird.

To make a flowing liquid animation, start by making your frames the same way you would any other animation. Don't organize them into strips like normal, though. Instead, take each frame and repeat it in a 2 by 2 block. This will make each frame in a flowing liquid animation twice the normal resolution of your texture pack. Don't worry, this is normal and won't affect the look of your pack at all.

Once you've done that, then you organize them into strips as shown above.

Here's a graphical representation of this:


This will also help you if you're converting your flowing water/lava animations from the pre-1.5 MCPatcher/Optifine format to the new Minecraft flowing liquid animation format.

Tip: Why the Double Tile?: If you're wondering the reason why the flowing liquid animations are different, it's because of how Minecraft renders the water textures. Flowing water tiles are placed in the middle of the 2x2 area. This saves Minecraft from having to tile the texture in real time. If your animation looks different than expected, remember that the tile is actually in the middle of your frame, and not lined up with the single tile in the corner. A 25% offset is required to fix this if it's an issue.

When making the .txt file for these animations, remember that your frames are now twice as large as they normally would be. When you go to figure out the number of frames you have, remember to divide both dimensions of your animation strip by 2 to get your 'real' resolution.

Note the basic clockwise motion of the blue dot. Having it at the top of the circle represents noon, while at the exact bottom it represents midnight. It then returns to the top along the other side. However you choose to have your animation represent time, have it follow this same basic movement.

Compass

With the compass, the top frame should be with spawn directly at the player's back. If you're animating a traditional style of compass, this would be with the needle pointing strait down.

On a traditional compass (like the one used in vanilla) the needle progresses in a clockwise direction as you move down the animation strip. Half-way through the animation it should be pointing with spawn directly in front of the player. It then proceeds down the opposite side of the circle, still in a clockwise movement. The last frame should be nearly at the player's back again, although slightly to the player's right.

Tip: That last frame... again: Again, be mindful not to have to top and bottom frames of your compass sequence be the same lest it confuse players using your texture pack. Only the top frame should have the player facing directly away from the spawn. The bottom frame should be slightly off center.

Here's a simple example of this:

Note where the red dot starts (at the bottom), and the general flow of its movement in a clockwise fashion ending up nearly back at it's starting position in the last frame. These are the important things.

As always, you don't have to represent your compass in this fashion, but make your version represents the same movement.

As with the clock, you don't have to have a specific number of frames. The game will divide your frames evenly among the 360° of rotation a player can be standing at.

• Make sure that what you're animating is a block or an item. Entities, mobs, GUIs, etc. cannot be animated with this method.
• If you are using Optifine, make sure that Animations are enabled.
• Windows Users: Make sure you have Windows set to show known file extensions. You may have a hidden .txt extension at the end that's throwing Minecraft off.
• Make sure all of your brackets are of the correct type. Most brackets will be curved brackets ({ }), but the frame order uses squared brackets ([ ]).
• Make sure you have opening and closing brackets. For every { there is a }. For every [ there is a ]. A common mistake is to have too many or too few brackets. Make sure to count them.
• Do NOT put a comma after your last frame. If you're listing your frames for any reason, make sure not to put a comma after the last one.
• Check the number of frames you've specified in your .mcmeta file. You MUST have only frames that actually exist. Remember that the count starts with "zero" so your last frame will be numbered one less than the total number of frames you have if you start counting with "one" like a normal human being. For example {17 total frames} = {frame 0 though frame 16}.
• Make sure to put a comma between the "frametime": and "frames": attributes, but not after the second one. Again, a comma is your way of telling Minecraft that there's more to be looked at. If you put a comma and there's nothing more that Minecraft needs to look at, it will give up and cause the animation to fail.
• Make sure your .mcmeta file is in 'UTF-8 without BOM' format. This should be automatic for most simple text editors, but not necessarily all.
• If all else fails, try changing everything in your .mcmeta file to be a single line. Rarely, Minecraft will just not like the way you hit the enter key, and the file will be invalid as a result.

7. Any Questions?

If there's anything that you don't understand, want clarified, or just can't figure out feel free to post in this thread and someone (maybe even me) will try to help you out.

Please be clear about what you're having problems with. Saying "it's not working" doesn't help anyone to help you. Provide screenshots if possible. Also, be prepared to offer a download of the animation files that aren't working. Sometimes we just have to see what you've done in order to tell you what you did wrong.

Hopefully this thread helps some of you who are having problems with this new format out.