This is a client entity file;

• "identifier" is your entity's identifier. It means the same as in blocks or items. For example, I can summon my entity via the command /summon tut:skele_yaklin.

• "materials" control how the entity is rendered. For now, we'll assign the Vanilla "skeleton" material(which allows texture transparency) to the shortname default.

Note: Entities that have a single model, a single texture and a single material, do not require custom shortnames and render controllers for all of these. Instead, we can set all of the shortnames to "default" and use a default render controller, like "controller.render.skeleton", which automatically renders everything with shortnames set to "default". We'll create a custom render controller nevertheless.

• "textures"/"default" needs to be set to the texture's directory; If this is done incorrect, the texture will be switching uncontrollably.

• "geometry"/"default" needs to be set to your model's identifier. If this is done incorrect, your entity will appear invisible.

• In "animations" one can simply define shortnames for animations and animation controllers - Along with our custom "walk" animation, I've defined the Vanilla "humanoid_big_head" animation for baby entities and the "look_at_target" animation. They are both already in Minecraft, no need to create them. Name your head bone head to make sure they'll work.

• "scripts"/"animate" control how animations are run without Animation Controllers. - The "walk" animation will be run when the entity is moving (query.modified_move_speed returns true when speed is higher then 0);- The "humanoid_big_head" animation will be run if query.is_baby returns true, in other words, if the entity is a baby. - And, finally, "look_at_target" will be always run. A more advanced way of controlling animations are Animation Controllers, which will be covered next.

• Queries are a part of MoLang, a simple language developed specifically for controlling MC animations. Queries will be used later on in Animation Controllers, Server Animations and Render controllers as well. For more info and/or the list of entity queries, see the documentation page on bedrock.dev/c/MoLang.

• "render_controllers" define the render controllers of an entity, which in it's turn, defines which texture shortnames are to be rendered. "controller.render.skeleton", for example, renders everything with the shortname "default". More about Render Controllers below and in the next tutorial: Render controllers.

• "enable_attachments" defines whether armor and equipment will be rendered on this entity.

• "spawn_egg" automatically creates the spawn egg item (which will be found in the creative inventory). You can either set the two colors to different hex codes or set "spawn_egg">"texture" to an item texture's shortname. - For example, the creeper's spawn egg "base_color" is set to green, and it's "overlay_color is set to black.