uniqueitems

uniqueitems.txt defines every unique item in D2R: from The Gnasher (Hand Axe) to Tyrael's Might (Sacred Armor). Each row pins a unique to a base item via code, gates its drop eligibility, and encodes up to 12 stat rolls using the same property/parameter/min/max layout that magicprefix, magicsuffix, automagic, and runes all share.

439 rows total. The *ID comment column tracks original row order; the *ItemName comment column carries the display name string for human reading (the actual lookup key is index).

What's in a row

The 67 columns split into seven groups.

Identity & display

Drop eligibility & gating

The drop logic walks four independent gates:

Base item & character gating

Stat encoding — prop/par/min/max ×12

The familiar T1* /mod* encoding from runes, magicprefix, and magicsuffix, but renamed and extended to 12 stat slots:

This is the single shared property layer — granting +Strength via prop=str works the same on a unique, a magic-prefix item, or a runeword. Common codes: str, dex, hp, mana, res-all, dmg%, openwounds, crush, allskills, skilltab, skill, oskill.

Visual & audio overrides

The iconic gold-orange unique color comes from chrtransform / invtransform.

Economy & DClone

Worked example: The Gnasher

A simple ilvl-7 Hand Axe unique. Four of the twelve stat slots used:

Three of four stats are fixed (min == max); dmg% rolls 60–70 each spawn. When reporting unique-item rolls, always show the range, not the average.

Variable rolls

Many uniques have one or more min < max slots. Examples to keep in mind when reporting stats:

A "Shako with 30 MF" and a "Shako with 50 MF" are both Shakos; the variance lives in the min/max block.

Drop eligibility — when does it actually drop?

The pick walks the four gates in order:

1. disabled blank or 0? Yes → continue. No → never drops.
2. spawnable = 1? Yes → continue.
3. Ladder-season window matches? firstLadderSeason empty or current season ≥ first; lastLadderSeason empty or current season ≤ last → continue. Otherwise → not droppable this season.
4. Item ilvl ≥ uniqueitems.lvl? Yes → eligible for the rarity-weighted pick.

A unique with firstLadderSeason set and no lastLadderSeason is ladder-only and has not yet rotated off-ladder — same convention used by runes for runeword gating.

Common queries

-- All uniques on a specific base (Elite Diadem family)
SELECT "index", lvl, "lvl req", spawnable, disabled,
       prop1, min1, max1, prop2, min2, max2
FROM uniqueitems WHERE code = 'dib'
ORDER BY CAST(lvl AS INTEGER);

-- Ladder-season-gated uniques
SELECT "index", code, firstLadderSeason, lastLadderSeason
FROM uniqueitems WHERE firstLadderSeason != ''
ORDER BY CAST(firstLadderSeason AS INTEGER);

-- All +allskills uniques (any of the 12 prop slots)
SELECT "index", code, lvl
FROM uniqueitems
WHERE prop1='allskills' OR prop2='allskills' OR prop3='allskills'
   OR prop4='allskills' OR prop5='allskills' OR prop6='allskills'
ORDER BY "index";

Cross-references

• weapons / armor — code resolves into one of these (or Misc.txt for charms / jewels / circlets).
• itemtypes — base codes inherit from itypes; the same hierarchy walk applies for class restrictions.
• magicprefix / magicsuffix / runes — share the same property/parameter/min/max stat-encoding layer.
• itemstatcost — prop* codes ultimately resolve to stats here (via Properties.txt).
• Properties.txt — defines the property-to-stat mapping referenced by prop1..prop12.

Naming gotcha

uniqueitems is the unique items table. Despite the similar name, uniqueprefix, uniquesuffix, and uniqueappellation are unique-monster name pools — not item affixes. Item-side affix pools are magicprefix / magicsuffix / automagic.