Huntera's outfits as the game publishes them — 75 on the capture being
served, each carrying the pair of looktypes the client draws it with.

looktypes is a pair and not a male/female split, because the game
publishes no field saying which is which and the arithmetic does not
settle it: the gap inside a pair is Tibia's canonical 8 in only seven of
the 75. The key is therefore this API's own, folded from the name, which
makes outfits the one track on this surface not keyed on an identifier the
game itself publishes.

store, premium and no_addons are three independent flags rather than
one state: 54 outfits are store-sold and nothing else, 14 are premium and
nothing else, 3 carry all three and 4 carry none. All three say how an
outfit can be got and none says anything about one character.

Nothing here is borrowed from tibia.dev, so fallbacks is empty on every
row and the tibia object beside it carries the counterpart's name, its id
and its sprites, and no quantity at all. Unlike the other tracks it carries
no image_url: a Tibia outfit's renderings are a gallery keyed by sex and
addon rather than one path, so tibia.images is what it has instead —
8 sprites on every one of the 73 that resolve, four addon levels for each
of female and male.

Those keys are Tibia's and say nothing about looktypes above them. The
game publishes no field saying which half of a pair is drawn for which
model, so the pair stays unordered and the sexes stay inside the object
that quotes tibia.dev.

Two of the 75 have no counterpart at all: Tibia calls Noble and
Retro Noble Nobleman and Retro Nobleman, and a different name is not a
match this API will guess at.

?include=quests answers which quests reward an outfit. Three of the 75 are
rewarded by one — demon, wayfarer and yalaharian — and the other 72
answer an empty list, the game handing the rest out through the Store, a
premium account or an addon.