Guide

Game item rarity and affix systems explained

Harbor Siege's first dungeon tier dropped swords labeled “Iron Blade” with identical grey icons whether they rolled +3 attack or +12 with a crit bonus. Players vendored upgrades because the inventory grid looked like duplicate junk. Support tickets asked “is this better?” on every third pickup. The loot tables were generating varied stats — but the presentation layer hid the variance. Rarity tiers, color beams, and affix text existed only in a spreadsheet designers never shipped to clients.

Item rarity and affix systems are how players read power at a glance and how designers budget stat inflation across content tiers. Rarity is the coarse signal (common through legendary); affixes are the fine-grained rolls (prefixes, suffixes, implicits, and uniques). Together they connect drop tables, distribution rules, and equipment loadouts into a loop players can learn without a wiki. This guide covers tier taxonomy, affix pools and roll math, color and UI conventions, item-level scaling, unique and set bonuses, the Harbor Siege refactor, a technique decision table, pitfalls, and a production checklist.

Rarity tier taxonomy

Most action RPGs and loot shooters converge on a similar ladder. Names differ (“Masterwork” vs “Epic”) but the slot budget pattern repeats: higher tiers unlock more affix lines and wider roll ranges.

Tier	Typical affix budget	Player read
Common / white	Base stats only, no random mods	Vendor trash unless early-game gap filler
Uncommon / green	1 minor affix or fixed small bonus	First meaningful upgrade tier
Rare / blue	2–4 rolled affixes within ilvl bands	Build crafting starts here
Epic / purple	4–6 affixes, higher roll ceilings	Endgame chase for many MMOs
Legendary / orange	Fixed unique effect + rolled stats	Build-defining; chase items
Unique / named	Hand-authored effect, often fixed rolls	Collectible; may break normal rules
Set / tiered set	Per-piece stats + threshold bonuses (2/4/6)	Horizontal progression; raid goals

Tier is not the same as item level (ilvl). A rare blue at ilvl 12 can beat a purple at ilvl 8 if your content bands are wide. Document both on the tooltip: tier communicates affix count; ilvl communicates roll range.

Affix pools and roll resolution

Affixes are drawn from tagged pools per equipment slot. A bow might pull from ranged_damage, crit, and utility pools; a chest piece pulls defense and resist. Keep pools data-driven so balance patches do not require client rebuilds.

Prefix, suffix, and implicit

Prefix — usually offensive or primary stat (“Vicious” +% damage).
Suffix — usually defensive or utility (“of the Bear” +vitality).
Implicit — fixed property of the base item type (sword base crit, wand spell power).

Roll resolution typically runs: (1) pick tier from table weight, (2) roll affix count from tier budget, (3) for each slot pick pool then affix then value within ilvl min/max, (4) reject duplicates and incompatible pairs (two +% damage lines may be forbidden), (5) serialize to item instance ID for server authority.

Power budget math

Assign each affix a budget cost in points. A rare item might have 100 budget points split across four lines. If “+15% crit” costs 40 points, the remaining lines must be weaker. This prevents god rolls that break encounter tuning and gives designers a single knob when ilvl bands shift.

Color coding, beams, and UI readability

Players decide pickup priority in under two seconds. Visual language must be consistent across ground loot, inventory grids, and vendor panels.

Name color matches tier (white/green/blue/purple/orange).
Loot beam on drop — vertical pillar visible at distance; tune height and pulse per tier.
Compare tooltip — green up / red down arrows vs equipped item; show delta on primary stat.
Affix ordering — fixed uniques first, then sorted by category so scans are predictable.
Accessibility — do not rely on color alone; add tier icons or patterns for color-blind modes.

Harbor Siege's refactor added tier-colored nameplates on ground items and a compact affix summary line (“+Crit, +Haste”) under the item name before players opened full tooltips. Pickup-to-equip latency dropped because the grid no longer looked like 20 identical grey swords.

Item level and content banding

Item level sets the min/max roll range for affix values, not just the base damage number. Zone 3 enemies drop ilvl 28–32 gear; Zone 4 drops 33–37. If a player farms Zone 3 at character level 40, their rares cap below Zone 4 blues — intentional friction that pushes content progression.

Pair ilvl bands with enemy scaling so stat inflation stays legible. When you raise ilvl ceilings in a patch, re-run Monte Carlo sims on affix budgets so old epics do not become vendor trash overnight unless that power reset is deliberate.

Unique effects and set bonuses

Legendary uniques

Uniques trade some rolled flexibility for a fixed effect: “Your third hit explodes for 200% weapon damage.” Design them as build enablers, not strictly better rares. A unique that is BiS for every spec homogenizes loadouts and kills chase variety.

Set bonuses

Sets reward collecting multiple pieces. Threshold design (2pc / 4pc / 6pc) should front-load value: the 2-piece bonus must feel good alone or players abandon the set before completing it. Set pieces often drop from specific encounters — coordinate with loot distribution so personal loot does not starve set completion.

Harbor Siege loot presentation refactor

The Siege team split item data into three client-visible layers:

Base template — icon, weapon type, implicit (unchanged).
Tier envelope — rarity color, affix slot count, beam VFX.
Instance rolls — serialized affix list with budget validation server-side.

They added a “quick compare” chip on hover: if any affix beats equipped gear in a tagged category, the item border glows. Vendor sell price now scales with tier and total budget points so players rarely trash blues by mistake. Post-patch, mistaken vendoring reports fell 62%; build guide forum traffic shifted from “is this good” to actual synergy discussions.

Technique decision table

Approach	Best when	Weak when
Flat stat items (no affixes)	Roguelites with short runs, clear numeric upgrades	Long MMO grinds where variety drives retention
Full random affix rares	ARPG endgame, build theorycrafting communities	Casual mobile sessions; analysis paralysis
Fixed uniques only	Looter-shooters with small chase pools	Players want incremental gear treadmill
Crafted determinism (re-roll one affix)	Reduce bad-luck frustration in competitive modes	Over-customization kills drop excitement
Tier without affixes (color = base power)	Co-op games with young audiences	Min-max communities; shallow build space
Procedural name generation	Flavor and meme shareability	Tooltip clarity; localization cost

Common pitfalls

Stats without tier visuals — players cannot sort loot; everything gets vendored.
Too many tiers — seven colors between common and legendary dilutes meaning.
Affix soup — twelve lines on one tooltip; mobile UI breaks.
God affix combos — budget validation missing; one item obsoletes content.
Ilvl invisible — players equip down-level blues and blame “broken RNG.”
Color-only tier signal — fails accessibility; use icons and text labels.
Unique power creep every patch — old legendaries become souvenirs; trust erodes.
Set bonuses too back-loaded — 6-piece only reward; 95% of drops feel useless.
Affix names without stat translation — “of the Whale” means nothing to new players.
Client-side roll authority — cheaters spawn perfect items; always server-seed.

Production checklist

Data-driven tier table: affix count, budget points, drop weight per content band.
Per-slot affix pools with exclusion rules and duplicate prevention.
Ilvl min/max bands per zone or activity; documented in player-facing patch notes.
Server-authoritative roll with logged seed and instance ID.
Name color, beam VFX, and inventory border consistent per tier.
Compare tooltip with green/red deltas vs equipped item.
Color-blind tier icons and optional text labels (“Rare”).
Vendor price formula tied to tier + budget so mistakes are costly but recoverable.
Monte Carlo sim export: affix distribution histograms per ilvl band.
Unique effect design review: not strict BiS for all specs.
Set threshold bonuses: 2-piece must stand alone.
Localization pass on affix display names with stat numbers always visible.

Key takeaways

Tier tells players how many knobs rolled; ilvl tells them how strong the knobs can be.
Affix budget math keeps god rolls rare without hiding variance in grey icons.
Color, beams, and compare UI are part of the loot system — not polish you ship later.
Uniques enable builds; sets reward collection — neither should homogenize every loadout.
Server-side rolls and logged instances are non-negotiable for any tradable gear.