Slots

Slots

Applies to Regalia Slots API 1.0.2 for Minecraft 1.21.1, and to 1.1.4 for 26.2.

The 11 defaults

Granted out of the box, to every player-like entity:

Slot	Order	Slot	Order
back	0	hands	7
belt	1	head	8
body	2	necklace	9
bracelet	3	ring	10
charm	4	feet	6
curio	5

Order controls the layout in the GUI, not priority.

Being granted is not the same as appearing. Slots are created on demand — a declared slot only becomes visible when there is something that can occupy it, or when you force it. That is the default behaviour and the reason a fresh install shows fewer than eleven.

Granting slots through the config

The slots option in the common config takes one entry per slot:

id=back,decode=slot.back,order=0,icon=regalia_slots_api:slot/back

Field	Meaning
id	The slot's identifier. This is what items are matched against.
decode	Translation key for the slot's display name.
order	Position in the GUI.
icon	Texture shown when the slot is empty.

The syntax is inherited from Curios and is documented upstream at docs.illusivesoulworks.com/curios/configuration#slot-configuration.

To change which slots exist, edit that list. You can empty it completely — the slots = [] case is supported and intended, for servers where they would rather every slot appeared only on demand.

Which items belong in a slot

Vanilla tags. An item goes in a slot because a data file says so, under:

data/regalia_slots_api/curios/slots/<slot>.json

Each such file declares an order, an icon and a validator — by default the tag validator, meaning the slot's contents are defined by an item tag.

This is deliberately the vanilla mechanism: categorising an item into a slot type is a matter of adding it to a tag, no code required. An item can be in as many slot types as you like, and a datapack can override the whole thing.

Eleven files ship by default, one per slot above. Deleting one removes that slot's tag data.

Who can have slots

By default, every player-like entity — defined by the entity type tag:

data/regalia_slots_api/tags/entity_type/player_like.json

Narrow that tag and slots stop being granted to the entities you removed. This is the supported way to restrict slots to players only, or to exclude mobs.

Commands

Slots can also be granted per player in-game, without touching the config. See Commands.

Customising appearance

Per slot, a developer can set a custom background, a different size, and whether the slot starts hidden or disabled. A disabled slot can be enabled per player; a hidden one simply does not draw until something needs it.

A note on the legacy preset API

Earlier versions exposed the eleven slots as a compiled-in enum, SlotTypePreset, with fixed priorities. That enum is deprecated and scheduled for removal in Minecraft 1.22.

It is not what grants your slots — the slots config list above is. If you are writing code against Regalia Slots API, use the SlotType builder in the API package instead; the enum is a legacy path kept only for compatibility.

For the record, that legacy enum lists ten entries and omits feet. It has no effect on the default set, which does include feet through the config list, but anything still calling the deprecated preset API will not see a feet slot.