Rendering API Breakdown
To link a given item to a specific AccessoryRenderer you will need to register such within the AccessoriesRendererRegistry class. By default all accessory items that have no renderer registered will get the DefaultAccessoryRenderer which attempts to render the block/item on the player in a position where the slot is located on the entity.
Default Accessory Rendering Behavior
All default slots have default renderers, but new slots will need to implement these on their own using the DefaultAccessoryRenderer#registerHelper method. Such helper is just a generic helper to transform the renderer to the slots location on the entity.
The only way for one to disable the Default Rendering for a given Accessory is by using the AccessoriesRendererRegistry#registerNoRenderer or adjusting the Data Component if actively toggled on. Furthermore the given default Render can be manipulated using the AccessoryRenderTransformations data component for use with Data driven Accessories.
If you need simple item rendering for your Accessory, then you could look at SimpleAccessoryRenderer. It provides a align method, which lets you transform the rendering to your desired location on the entity.
Transformation Methods¶
Accessories provides some helper methods to assist with transforming your AccessoryRenderer to various locations on the body with the primary method being transformToModelPart which will transform the given PoseStack (MatrixStack) to a given location on the targeted ModelPart.
Two overloads exist for this. The first method transforms the PoseStack (MatrixStack) to the center of the ModelPart while the other allows for more control on the positioning on the x, y, and z axis by providing a number between -1 and 1 as explained below:
| Axis | Negative Values | Positive Values |
|---|---|---|
x |
Left Movement | Right Movement |
y |
Bottom Movement | Top Movement |
z |
Back Movement | Front Movement |
This method of transformation allows for the Accessories renderer to follow the model parts better allowing for compatibility with mods like Entity Model Feature and is more precises than generic transformations to where given model part may be located.
Furthermore you can use transformToFace to target specific faces of a given model part by passing the given Side which such will transform the rendering to the outside of the given models face.
First Person Rendering
Accessories supports rendering within first person. By default anything on the humanoid entities arms is rendered this way. You can set this yourself by overriding the shouldRenderInFirstPerson method within your renderer.