An item answers to the numeric id the game publishes and to its slug, and
a name is slugged before it is tried, so /items/3031 and
/items/Gold Coin are the same item. The id wins where the two collide.

Eight rows of 837 answer to the id alone. Three names are shared — music sheet by four rows, sword ring and inkwell by two each — and the
import gives every row in those groups a null slug rather than handing
the bare name to whichever id sorts lowest, so /items/music-sheet is a
404 because no name names one of them.

Every reverse relation comes with it unasked, where the listing takes
?include=: which creatures drop it and how often, which bosses drop it
and how rarely, which hunts list it, which quests award it, and which
imbuements it is a material for.

Fifteen fields moved into four objects and category became a pair, which is a
breaking change on this endpoint. Nothing was renamed beyond the moves, no value
changed and no field was dropped:

• required_level is requirements.level, vocations is requirements.vocations
• attack, defense, armor, range, two_handed, attack_skill, elemental_type
  and elemental_damage are the same names under combat
• speed_bonus is bonuses.speed, magic_level_bonus is bonuses.magic_level,
  skill_bonuses is bonuses.skills
• npc_buy and npc_sell are the same names under trade
• category was the shelf's slug and is {slug, name} now, the slug unchanged

slot, weight, imbuement_slots, resistances and tibia_item_type did not move,
and neither did any filter or sort — ?filter[min_required_level]=, ?sort=armor and
?filter[category]=helmets all read columns and take exactly what they took before.

The groups are four questions rather than a tidying: whether a character can equip it,
what it does in a fight, what it adds while worn, and what it costs. They are typed
numbers throughout — this is deliberately not Tibia's attributes map, which is a
pivot of free-text wiki values and publishes "armor":"17" as a string.