Armor-set bonuses and cosmetics
Obsidrel distinguishes equipment mechanics from visual cosmetics.
An armor set under resources/armor-sets/ points to existing Obsidrel item IDs and defines bonuses by piece count:
ruby_guard:
enabled: true
pieces:
head: obsidrel:ruby_helmet
chest: obsidrel:ruby_chestplate
legs: obsidrel:ruby_leggings
feet: obsidrel:ruby_boots
bonuses:
'2':
activate-actions: [ruby_guard_2_on]
deactivate-actions: [ruby_guard_2_off]
The referenced items and actions must exist. The source documentation states armor bonuses update on equipment changes rather than through a global polling task.
Cosmetics
A cosmetic definition in resources/cosmetics/ references an Obsidrel item and a slot (HEAD, CHEST in the sample). Cosmetics are visual and do not replace the player's actual armor server-side.
If a bonus is missing, check the exact item IDs, the piece threshold and whether the referenced activation action is defined.
Applying this in your project
Verify every armor-piece ID exists, and the 2-piece and 4-piece activation/deactivation actions also exist. Cosmetics only change the visual selection: compare with real equipped armor.
Back up before modifying production. Run /obsidrel reload, inspect warnings and test in game. Rebuild the resource pack for model or texture changes.
See the field reference for documented sample options.