So you have finished your model and want to save it, its textures and it's animations, simply follow the steps below for each asset.
Hinweis
Keep your .bbmodel project file as well. Hitboxes, sockets, IK, spring bones and the other features from the AzureLib Rig panel are saved only in it, not in any exported file.
Exporting the geo.json model.
Open File and then select Export and choose Export Azurelib .geo Model
Achtung
This file MUST be saved in the geo folder
Hinweis
You can save these files into sub folders of the geo folder to help organize your assets.
Examples:
Entities: /assets/modid/geo/entities
Block Entities: /assets/modid/geo/blockentities
Items: /assets/modid/geo/items
Armor: /assets/modid/geo/armors
Now save this file to your projects geo assets folder (Example: /assets/modid/geo/)
Exporting the Item Display Settings
If your model is one that will be used an item or reused as an Item, you will want to export your Item Display Settings file then.
Achtung
This file MUST be saved as the same as items resource name, so if it's called yourmodid:superitem in game, it must be saved as superitem.json in your /assets/modid/models/item/ folder
Open File and then select Export and choose Export Azurelib Display Settings
Exporting the texture file
Hinweis
You can save these files into sub folders of the textures folder to help organize your assets.
Click confirm to save your JSON file to your projects animations assets folder (Example: /assets/animations/geo/)
Generating the Rig Code
If you've set up hitboxes, sockets, IK, look-at, constraints, spring bones or blend spaces in the AzureLib Rig panel, generate the Java for them:
Open File and then select Export and choose Generate AzureLib Rig Code (or press Code in the panel).
Choose your AzureLib branch and enter your entity class name, then press Confirm.
Press Copy, or Save .java to save the code to a file, and paste each section into the class named in its header.
Hinweis
Press Check AzureLib Rig (in the same menu) first to catch renamed or missing bones, so the code matches your model. See Generating the Code for what each section contains.
