# SpineDrawableBatch ### Introduction The SpineDrawableBatch class is responsible for drawing Spine in your FlatRedBall game. If you have used Tiled in your FlatRedBall projects, you can think of the SpineDrawableBatch as being similar to a Tiled Layer. In other words, the SpineDrawableBatch has the following characteristics: 1. It can be positioned explicitly, although this is typically done through attachments in generated code 2. It has a Z value which controls its sorting 3. It produces a new render break (this may change in the future) By contrast, normally Tiled maps are added to Screens; however, SpineDrawableBatches are typically added to Entities. ### Adding Spine Files Spine files are needed to draw a SpineDrawableBatch. Conceptually you can think of these files similar to how you might think of a .achx file - it needs to be loaded as part of an entity or screen before it can be used to display any graphics. To add a SpineDrawableBatch to an entity: 1. Create an entity that will contain the SpineDrawableBatch. This example uses an Entity called Soldier 2. Drag+drop the texture file (.png) used by the Spine atlas into the Entity's files 3. Drag+drop an Atlas file (.atlas) into the Entity's files 4. Drag+drop a Spine skeleton file (.json) into the Entity's files 5. Select the Skeleton entry in FlatRedBall, click on the Spine tab, and change the Atlas property the desired Atlas file. It should appear in the dropdown.

Setting an AtlasName on a Spine skeleton

**Important**: At the time of this writing, the three files must be loaded in the proper order. The order is: 1. Texture file (.png) 2. Atlas (.atlas) 3. Skeleton (.json) You can re-order the files by holding down the ALT key on the keyboard and pressing the up and down keys.

This requirement may go away in the future as the Spine plugin gets better at tracking dependencies. Note that the texture file (.png) is loaded when the atlas is created and ultimately uses a FlatRedBall content manager. This means that if your png is already loaded (such as by being in Global Content Files), then you do not need to also have the png in your entity. This is especially useful if your atlas references a shared sprite sheet which is used by other screens and entities. ### Adding a SpineDrawableBatch Object Now the Spine files have been added to the entity, we need to add them as an object. By adding an object we can control properties such as position (offset) and scale. Also, each individual object can be independently animated. To add and attach the SpineDrawableBatch: 1. Drag+drop the skeleton file from Files onto Objects 2. Change the Source name to **Entire File (SpineDrawableBatch)** 3. Enter a name such as SpineDrawableBatch 4. Click OK

Creating a new Object from a loaded Spine Skeleton

You should now have all three files in your Entity as well as a SpineDrawableBatch in the Objects folder.

Spine files and SpineDrawableBatch object

### Adding an Entity Instance to a Screen To see the entity instance in-game, drag+drop the entity onto a Screen, such as GameScreen. Run the game and the Spine Drawable Batch should appear.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.flatredball.com/flatredball/spine/spinedrawablebatch.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.