intermediate TileEntity Animation System Explanation

Animefan8888 · July 12, 2018

There is a WIP PR for documentation on this that has everything that is on this tutorial, and will soon have more such as Items and Entities. Here is a link to the PR.

In this tutorial I will be explaining how to use the Animation State Machine or Forge's Animation System on a TileEntity, though this can be applied to Items or Entities as well.

Let's start off easy, with the code for the Block, TileEntity and the binding of the TESR.

Block

Spoiler


public class AnimatedBlock extends Block {

	public AnimatedBlock(Material materialIn) {
		super(materialIn);
		// Set registryName, unlocalizedName, etc.
	}
	
	/**
	 * Creates the ExtendedBlockStateContainer that is needed for the AnimationProperty.
	 * 
	 * Properties.StaticProperty allows for the block to render a normal model and then animate a second model within AnimationTESR. 
	 * This property is not required and anything specifically used just for this property is not required if it is not in use.
	 * 
	 * Properties.AnimationProperty stores the IModelState to be rendered/applied by AnimationTESR.
	 */
	@Override
	public BlockStateContainer createBlockState() {
		return new ExtendedBlockState(this, new IProperty<?>[] { Properties.StaticProperty }, new IUnlistedProperty<?>[] { Properties.AnimationProperty });
	}
	
	/**
	 * Required to override as the game will throw an exception since there are properties within the BlockState. Note it does not have to return 0.
	 */
	@Override
	public int getMetaFromState(IBlockState state) {
		return 0;
	}
	
	/**
	 * Forces the state that is rendered to use the model AnimationTESR will not animate.
	 */
	@Override
	public IBlockState getActualState(IBlockState state, IBlockAccess worldIn, BlockPos pos) {
		return state.withProperty(Properties.StaticProperty, true);
	}

	/**
	 * Let's the world know that this block has a TileEntity associated with it.
	 */
	@Override
	public boolean hasTileEntity(IBlockState state) {
		return true;
	}
	
	/**
	 * Returns a new instance of our TileEntity to be placed in the world.
	 */
	@Override
	public TileEntity createTileEntity(World world, IBlockState state) {
		return new TileEntityAnimated();
	}
	
	/**
	 * Override these two methods if your block is not a solid opaque cube used in rendering.
	 */
	@Override
	public boolean isOpaqueCube(IBlockState state) {
		return false;
	}
	
    @Override
    public boolean isFullCube(IBlockState state) {
    	return false;
    }
    
    /**
     * Only overrode to explain that if your block doesn't have a model that is not animated, it should return EnumBlockRenderType.ENTITYBLOCK_ANIMATED.
     */
    @Override
    public EnumBlockRenderType getRenderType(IBlockState state) {
    	return EnumBlockRenderType.MODEL;
    }
	
}

TileEntity

Spoiler


public class TileEntityAnimated extends TileEntity {
	
	/**
	 * This is the thing that makes everything work. It is loaded from a JSON we will make later. 
	 * This will be exposed as a capability instance.
	 */
	private final IAnimationStateMachine asm;
	
	/**
	 * You can also wrap this method in your ClientProxy class and call ClientProxy#loadASM instead of checking the side of FMLCommonHandler.
	 */
	public TileEntityAnimated() {
		if (FMLCommonHandler.instance().getSide() == Side.CLIENT) {
			asm = ModelLoaderRegistry.loadASM(new ResourceLocation(YOUR_MODID, "asms/block/animatedblock.json"), ImmutableMap.of());
		} else asm = null;
	}
	
	// If you don't know about getCapability and hasCapability please read the forge documentation about them.
	
	/**
	 * Exposes the instance of the IAnimationStateMachine to be used in AnimationTESR.
	 */
	@Override
	public <T> T getCapability(Capability<T> capability, EnumFacing facing) {
		if (capability == CapabilityAnimation.ANIMATION_CAPABILITY) return CapabilityAnimation.ANIMATION_CAPABILITY.cast(asm);
		return super.getCapability(capability, facing);
	}
	
	/**
	 * Informs that this TileEntity has the CapabilityAnimation.
	 */
	@Override
	public boolean hasCapability(Capability<?> capability, EnumFacing facing) {
		return getCapability(capability, facing) != null;
	}
	
}

TESR Binding

Spoiler


/**
* This needs to be done on the client only. Either put this in your ModelRegistryEvent or in your ClientProxy.
*/
ClientRegistry.bindTileEntitySpecialRenderer(TileEntityAnimated.class, new AnimationTESR<TileEntityAnimated>());

This is where the confusion comes from for the animation system. The armature and ASM JSON files. The ASM file has it's own "grammar" which is outlined by fry, here. This is a little vague so I will try to explain this a bit more, so that it is easier to understand with what I have come to know through my own attempts at using this system.

Armature File

Spoiler

NOTE: The armature file has to have the same name as the model that it will be applied to, IE if the model is animatedblock.json then the armatures file needs to be animatedblock.json. Also, it needs to be in assets/modid/armatures/block

The armature file is made up of two sections joints and clips. Joints are like groups. They allow you to group elements of models together, elements are essentially the cubes that make up a model. They are referenced by the order they come in(indexed at 0). So if I had a model with three elements this could be what my joints section looks like.


"joints": {
	// I am unsures as to why the element is bound to an array. But only the first value matters as it is used as a multiplier.
	"group1": { "0": [1.0] }, // Element 1
  	"group2": { "1": [1.0], "2": [1.0] } // Element 2 and 3
}

The clips section is a bit more hectic, but this is where you put your desired animations. This holds more JSON objects that specify what happens. Each object here contains three different parts, the names are loop, joint_clips, and events. Loop just specifies if the clip repeats over and over to the model until the clip is changed. Joint_clips is where the specifications on the animation are, and they are specified to the joint. Events are ways to let code run when the animation has reached a certain point in its life-cycle. This is what an example clips section might look like.


"clips": {
  	"default": {
    	"loop": false, // DO not loop
      	"joint_clips": {}, // No change to the model
      	"events": {} // No events
    },
	"moving": {
    	"loop": true, // Loop animation
      	"joint_clips": {
        	"group1": [
              {
              	"variable": "offset_y", // Specifies what transformation that needs to happen.
                "type": "uniform", // The only type that exists is uniform, not sure why this is included.
                "interpolation": "linear", // Linear is smooth between switches, and nearest is choppy and instant.
                "samples": [0, 0.5, 0] // The values applied, based on the life-cycle of the animation. 
              }
            ],
          	"group2": [
              {
              	"variable": "scale",
                "type": "uniform",
                "interpolation": "nearest", // Scale happens instantly instead of a growing animation.
                "samples": [1, 2, 1] // 1 is normal scale and 2 is times two scale.
              },
              {
              	"variable": "axis_z", // Provides a multiplier for the angle variable
                "type": "uniform",
                "interpolation": "nearest", // Applies the changes instantly
                "samples": [1, 2, 1] // Since there is no other axis declared their samples are 0, any value is treated as a 1.
              },
              	{
                "variable": "angle",
                "type": "uniform",
                "interpolation": "linear", // Smoothly rotates
                "samples": [0, 180, 0]
                }
            ]
          		
        },
      	"events": {
        	"0.5": "halfway" // Sends an event at halfway through the life-cycle due to the 0.5.
        } 
    }
}

The whole armature file.

Spoiler



{
	"joints": {
		// I am unsures as to why the element is bound to an array. But only the first value matters as it is used as a multiplier.
		"group1": { "0": [1.0] }, // Element 1
  		"group2": { "1": [1.0], "2": [1.0] } // Element 2 and 3
	},
  	"clips": {
  		"default": {
    		"loop": false, // DO not loop
      		"joint_clips": {}, // No change to the model
      		"events": {} // No events
    	},
		"moving": {
    		"loop": true, // Loop animation
      		"joint_clips": {
        		"group1": [
              		{
              			"variable": "offset_y", // Specifies what transformation that needs to happen.
                		"type": "uniform", // The only type that exists is uniform, not sure why this is included.
                		"interpolation": "linear", // Linear is smooth between switches, and nearest is choppy and instant.
                		"samples": [0, 0.5, 0] // The values applied, based on the life-cycle of the animation. 
              		}
            	],
          		"group2": [
              		{
              			"variable": "scale",
                		"type": "uniform",
                		"interpolation": "nearest", // Scale happens instantly instead of a growing animation.
                		"samples": [1, 2, 1] // 1 is normal scale and 2 is times two scale.
              		},
              		{
              			"variable": "axis_z", // Provides a multiplier for the angle variable
                		"type": "uniform",
                		"interpolation": "nearest", // Applies the changes instantly
                		"samples": [1, 2, 1] // Since there is no other axis declared their samples are 0, any value is treated as a 1.
              		},
              		{
                		"variable": "angle",
                		"type": "uniform",
                		"interpolation": "linear", // Smoothly rotates
                		"samples": [0, 180, 0]
                	}
            	]
          		
       		},
      		"events": {
        		"0.5": "halfway" // Sends an event at halfway through the life-cycle due to the 0.5.
        	} 
    	}
	}
}

1

ASM File

Spoiler

Note: The ASM file can be anywhere within the assets/modid package, but convention would dictate it goes in assets/modid/asms/block/. It;s position is denoted when loadASM is called, its path is within the ResourceLocation.

The ASM file is contains five main things: the parameters, clips, states,transitions, and the starting state(start_state). Parameters(JSON object) are essentially variables that you can modify using the arithmetic operations stated in the grammer file that was linked earlier. They are used in the clips section, speaking of which; the clips section(JSON object) stores references to the clips in the armature file along with operators for the clips. States is just an array that contains all of the clip names. Transitions is a JSON object that just maps each state to which state it can transition to. The start_state is a string that gives the name of the starting state when the ASM is loaded.

Parameters Section


"parameters": {
	"raw_anim_time": [ "+", 0 ], // Percentage of animation time using the add arithmatic operator.
  	"slowed_anim_time": [ "/", 4 ], // Percentage of animation time divided by 4 using the division arithmatic operator.
	"four": [ "/", "#slowed_anim_time" ] // Just using the division operator with another parameter.
  	// You can also reference parameters passed in from code when the loadASM method is called. ImmutableMap.of(String, ITimeValue);
}

Clips Section


"clips": {
	"default": "modid:block/animation_block@default", // Just a reference to the clip in the armature file.
  	"moving": [ "apply", "modid:block/animation_block@moving", "#slowed_anim_time" ] // Applies the slowed_anim_time to the moving clip in the armature file.
}

States Section


"states": [
	"default", "moving" // As seen above these are our two states, these must match clip names.
]

Transitions Section


"transitions": {
	"default": "moving", // default state will be able to transition to moving
  	"moving": "default" // mocing state will be able to transition to default state
}

Starting State


"start_state": "moving" // The ASM will start in the moving state

Whole ASM File

Spoiler



{
  	"parameters": {
		"raw_anim_time": [ "+", 0 ], // Percentage of animation time using the add arithmatic operator.
  		"slowed_anim_time": [ "/", 4 ], // Percentage of animation time divided by 4 using the division arithmatic operator.
		"four": [ "/", "#slowed_anim_time" ] // Just using the division operator with another parameter.
  		// You can also reference parameters passed in from code when the loadASM method is called. ImmutableMap.of(String, ITimeValue);
	},
	"clips": {
		"default": "modid:block/animation_block@default", // Just a reference to the clip in the armature file.
  		"moving": [ "apply", "modid:block/animation_block@moving", "#slowed_anim_time" ] // Applies the slowed_anim_time to the moving clip in the armature file.
	},
	"states": [
		"default", "moving" // As seen above these are our two states, these must match clip names.
	],
  	"transitions": {
		"default": "moving", // default state will be able to transition to moving
  		"moving": "default" // mocing state will be able to transition to default state
	},
  	"startstate": "moving" // The ASM will start in the moving state
}

Sample BlockState File

Spoiler


{
	"forge_marker": 1,
  	"defaults": {
    	// Declare your defaults
    },
  	"variants": {
    	"normal": [{}],
      	"inventory": [{}],
      	"static": { // Remember this is optional.
        	"true": { }, // Non animated model.
        	"false": { } // Animated model.
        }
    }
}

I'm sure there are typos or possibly something I have missed or not explained well enough, so I would love some feedback even on formatting issues. I will also post my raw notes on this stuff that might contain extra information.

Spoiler


Armatures File

Note: File name needs to be the same as the model files name or else it will not work!

joints: obj
	joint: obj
		model element(referenced by declaration in model file): name, value array(what's inside doesn't seem to matter.)
		
clips: obj
	clip name: obj
		loop: boolean(whether the clip should continuously run)
		joint_clips: obj
			joint name: array
				obj
					variable: string(which variable; offets_x/y/z, scale/_x/y/z, etc)
					type: string(uniform is the only option; not sure what the point of this is)
					interpolation: string(linear or nearest; linear seems smooth, while nearest is choppy/instant)
					samples: array(values that will be applied, multiple allows for animation)
	events: obj
		time event is fired(decimal; percentage of animation complete): string(name of event used in AnimationTESR#handleEvents)
			
			
ASM File
	Best reference
	https://gist.github.com/RainWarrior/964ed4692f4da1fd4964
	
	parameters: obj
		parameter name: array(uses arithmetic operations outlined in the link above and code parameters are referenced with a # and the key in the parameters map)
	clips: obj
		clip name: array or string
			string(simply just references the clip from the armatures file, doesn't apply a parameter value)
				"modid:block/filename@armaturesclipname" or "modid:item/filename@armaturesclipname"
			array of strings
				"apply"(animation call; the clip is modified by the parameters value), string from above, "#parametername"
				"slerp"("spherical linear blend between to clips"-Fry), string from above(initial clip), string from above(final clip), "#parametername"(input), "#parametername"(progress)
				"trigger_positive", "#clipname"(not from the armatures file), "#parametername", armatures event name or "!transition:clipname"(not from armatures file)
	states: array(contains clip names)
	transitions: obj
		state name: string(state name to transition to)
	start_state: string (state name for the animation to start on)

Code
	Properties.AnimationProperty in an ExtendedBlockState
	TileEntity needs to expose the CapabilityAnimation.ANIMATION_CAPABILITY in hasCapability and getCapability
	ClientRegistry.bindTileEntitySpecialRenderer(TileEntityClass, new AnimationTESR<TileEntityClass>());

Edited August 6, 2018 by Animefan8888

yurifag · August 6, 2018

Thank you for this tutorial.

However, you made a small but significant typo in your ASM json file which crashes the game.

The key "start-state" should actually be "start_state" as annotated in AnimationStateMachine.java:74.

@SerializedName("start_state")
private final String startState;

It took me quite a while to figure out what's wrong, because this kind of typo is particularly hard to notice.

Animefan8888 · August 6, 2018

Just now, yurifag said:

However, you made a small but significant typo in your ASM json file which crashes the game.

The key "start-state" should actually be "start_state" as annotated in AnimationStateMachine.java:74.

Oh, thank you I wrote this late at night after finally getting my animation to work. I will change that.

Sign In

intermediate TileEntity Animation System Explanation

Recommended Posts

Animefan8888

yurifag

Animefan8888

Join the conversation

Announcements

Recently Browsing

Posts

Topics

Who's Online (See full list)

Browse

Activity

Important Information