Huntera's hunting places as the game publishes them — 60 on the capture being served,
each keyed on the id the game files it under. A hunt carries the creatures it fields,
the loot they drop, and a ladder of three or four difficulty steps naming which of
those creatures and which of those drops each step is worth.

The loot table is opt-in here and comes unasked on the detail route. Ask for it with
?include=loot.item and every hunt carries its lines, each naming the item it drops
and how often. It is left out by default because it is three fifths of a page's bytes —
78,833 against 30,831 for a page of 25, and 95,580 against 34,125 on the heaviest page
— and a client browsing places should not pay for every drop table at once.

tiers is where this track's one trap lives, and creature_count is the field to read
carefully: it is how many creatures a step fields, not how many kinds it lists. The
two differ on 166 of the 182 captured tiers, and not in one direction — 157 steps
publish a count larger than their list and 9 publish one smaller. Neither derives the
other.

Three field names moved in this release, which is a breaking change on this
endpoint. monsters is creatures, tiers[].monster_count is
tiers[].creature_count, and tiers[].item_client_ids is
tiers[].loot_item_client_ids. Nothing else changed about any of the three: same
values, same order, same nesting, and creature_count is still the quantity the
paragraph above says not to read off the list beside it. The tables keep the word
monster — huntera_hunt_monsters and huntera_hunt_tiers.monster_count — and no
filter or sort took it as a name, so nothing in a query string moved.

A tier's name is now a difficulty object, which is a breaking change on this
endpoint. tiers[].name was the bare label; it is tiers[].difficulty.name now, with
difficulty.slug beside it and difficulty.rank — 1 to 5 — saying where the rung sits
on the game's whole ladder. position is unchanged and still counts from 0 within one
hunt, and the two answer different questions: issavi-south-hunt starts at Reckless,
so its position 0 is rank 3, the rung 57 other hunts reach at position 2.

Five labels appear over the 182 tiers — Cautious, Bold, Reckless, Suicidal,
Hardcore — and they are one ladder in that order. Only three sequences are published:
57 hunts run Cautious → Bold → Reckless, two add Suicidal, and one runs
Reckless → Suicidal → Hardcore with no Cautious and no Bold at all. Read as ordering
constraints those force that order and no other. Sorting the label as text still gets
the published order wrong on all 60, so use rank or position and never the word.

Three groups Tibia's own /v1/hunts publishes are absent here and will stay absent.
That endpoint carries requirements by vocation, and experience and loot as a
quality and a star count. Every one of those nine numbers comes from a column the
capture has no counterpart for — no level, no skill, no defence, no rating — so they are
missing rather than null, and reading a Suicidal tier as a level requirement is the
substitution this note exists to refuse.

A tier names its creatures and its drops by handle — creature_keys and
loot_item_client_ids — rather than repeating the objects above it. They point into the
hunt's own creatures and loot lists, in the order those lists are published in.

tibia is null on 49 of the 60 hunts, which is this track's ordinary state rather
than a broken import: 11 resolve against Tibia's 443 hunt articles, the lowest rate of
any linking track on this surface. Huntera names some places its own way — the hunt it
files as ab-bonelord-hunt it calls Braindeath Caves, which Tibia's hunt list calls
something else — and it hunts places Tibia's hunt articles do not cover at all. Nothing
is ever borrowed from the counterpart, so fallbacks is empty on every row.