Game equipment and loadout systems explained

Equipment vs inventory vs loadout

These three layers are often conflated. Separating them keeps code and UX sane:

Equipping moves an item reference from bag to slot (or swaps with whatever was there). Unequipping returns it to inventory if capacity allows. A loadout apply operation batch-equips many slots atomically — either all valid swaps succeed or none do, so players never end up half-equipped after a failed preset apply.

Slot taxonomy and restriction rules

Slots define where items can live and what categories fit. Common patterns:

• Weapon slots — primary, secondary, sidearm; two-hand weapons may occupy both hand slots.
• Armor slots — head, chest, legs, feet, gloves; sometimes shoulders and belt as separate slots.
• Accessory slots — rings (2), amulet, trinket; often the highest stat-density slot for build-defining effects.
• Mod / gem sockets — nested slots on parent items; applying a mod mutates the parent instance, not a top-level equipment row.
• Quick-bar slots — consumables and gadgets mapped to face buttons; technically equipment for combat purposes.

Restrictions gate what can equip where:

• Item type tags — slot=chest, weapon_class=rifle.
• Level and stat requirements — “Requires 40 Strength”; check against base + equipped stats or base only (design choice; document it).
• Class / faction locks — paladin-only shields; reputation-gated gear.
• Unique-equipped flags — only one copy of a legendary across all slots (common in MMOs).
• Set membership — two-piece bonus only fires when enough set items are equipped simultaneously.

Validate restrictions server-side in multiplayer. Client-side equip previews are fine; authoritative state must reject illegal combinations before stats propagate to combat.

Stat aggregation pipeline

When equipment changes, every system that reads player power needs a single recalculate pass. A typical pipeline:

1. Base stats from character level and skill tree allocations.
2. Flat bonuses from each equipped item (“+42 Attack”).
3. Percent modifiers applied in a defined order (additive within tier, then multiplicative — publish the order in a design doc).
4. Set bonuses when equipped count crosses thresholds (2/4/6 piece).
5. Buffs and debuffs from status effects (temporary; may or may not persist through loadout swap).
6. Derived stats — crit chance, move speed, cooldown reduction computed from final primary stats.

Cache the aggregated result and invalidate on equip, unequip, level-up, or buff expiry. Emit one stats_changed event so UI, AI threat scaling, and matchmaking all update once. Avoid letting individual items poke global stats directly — that leads to double-counting when swapping two rings in one frame.

Show players a diff preview before they confirm equip: green/red deltas on DPS, armor, and key secondary stats. Hide raw formula internals; surface the outcomes players actually care about.

UI patterns: paper doll, list, and hybrid

How players see and manipulate equipment shapes session pacing:

• Paper doll — character silhouette with clickable slot regions. Strong visual feedback; pairs well with 3D inspect and transmog. Harder on mobile (small touch targets).
• Slot list — vertical rows (“Head: Iron Helm”). Dense, accessible, fast to scan. Less emotional attachment to the character.
• Comparison pane — hovered bag item vs currently equipped side by side. Essential for looters; without it players alt-tab to wikis.
• Loadout tabs — horizontal preset strip; one tap to apply. Cap presets at 3–10; more creates decision paralysis.

Harbor Chronicles moved from list-only to hybrid: paper doll for flavor, list for precision edits, comparison pane on every bag hover. Controller focus order follows slot list top-to-bottom so navigation never jumps randomly across the doll.

Loadout presets and quick-swap

A preset stores slot ID → item instance ID mappings plus optional metadata (name, icon tint, linked skill build ID). Core operations:

• Save current — snapshot equipped state; warn if any slot is empty or contains a borrowed trial item.
• Apply preset — for each slot, unequip current and equip preset item if still in inventory; skip missing items with a clear toast (“Fire Staff not found — 7/9 slots applied”).
• Duplicate preset — fork for experimentation.
• Context presets — auto-suggest “PvE” when entering a dungeon zone (optional; never force without consent).

Quick-swap in combat is a design choice. ARPGs often allow instant swap out of combat only; hero shooters allow mid-match weapon swap on a cooldown. Document the rule and enforce it in the equip API, not scattered in UI buttons.

Link presets to crafting benches: “Save as loadout” after a gear craft session reduces re-entry friction for min-maxers.

Visual attachment and transmog

Equipment systems split stats from appearance when transmog is supported. The equip layer holds instance IDs for stat-bearing items; a parallel visual_override map per slot points at cosmetic mesh IDs. On equip change, the character rig swaps attachables at named bones (hand_r, spine_02, head).

Pipeline checklist: LOD meshes match across variants, sheath/unsheath animations exist for each weapon class, clipping tests run on the tallest and shortest body types. A chest piece that floats on wide shoulders breaks immersion faster than a -2% stat error.

Harbor Chronicles raid refactor

Before refactor, equipment lived inside the general inventory UI with no presets. Pain points from playtest telemetry:

• Average 11.8 minutes from raid lobby open to first pull (target: 5).
• 34% of players entered raids with wrong-resistance gear because swap friction discouraged prep.
• Support tickets for “lost gear” were mostly failed partial swaps leaving items in limbo between bag and slot.

Changes shipped:

1. Five named loadout presets with atomic apply and missing-item reporting.
2. Stat diff preview on every equip and preset hover.
3. Resistance tags surfaced on slot list rows (fire, ice, void) for raid-specific prep.
4. Transactional equip API — swap is all-or-nothing per operation.
5. Hub NPC “Armory” as dedicated equipment screen (inventory still handles mats and quest items).

Post-patch: lobby-to-pull median fell to 3.9 minutes; wrong-resistance entries dropped to 9%. Build diversity index (unique loadout hashes per raid) rose 22% because experimenting carried lower social cost.

Technique decision table

Common pitfalls

• Partial equip on preset apply — player thinks they are fire-resistant but chest slot failed silently. Always report skipped slots.
• Stat order ambiguity — two designers add “+10% damage” modifiers that stack multiplicatively by accident. Document and unit-test aggregation.
• Equip during combat when disallowed — exploit swap-for-stats mid-boss. Enforce in server API.
• Duplicate unique items — equip same legendary in two slots via race condition. Lock instance ID across slots.
• No comparison UI — players externalize decisions to wikis and leave your game.
• Paper doll without list fallback — controller and mobile users cannot hit slots reliably.
• Loadout bloat — unlimited presets become hoarding; cap and charge gold sink for extra tabs if needed.
• Visual-only items granting stats — transmog mesh accidentally carries stat component. Separate data paths.

Production checklist

• Define slot enum, item tag schema, and restriction validation in one module.
• Implement transactional equip/unequip with server authority in multiplayer.
• Publish stat aggregation order; add tests for flat, percent, and set bonuses.
• Build comparison pane with DPS/defense/resistance deltas before ship.
• Ship at least three loadout preset slots; test apply with missing items.
• Wire stats_changed event to UI, combat, and AI scaling once.
• Validate visual attach on min/max body types and all weapon classes.
• Separate transmog visual IDs from stat-bearing instance IDs.
• Log preset apply success rate and lobby-to-activity time in analytics.
• Playtest full gear swap on gamepad without mouse; fix focus order.

Key takeaways

• Inventory owns items; equipment owns worn slots; loadouts are named snapshots for fast apply.
• Stat aggregation must be centralized, ordered, and invalidated once per change — never per-item ad hoc patches.
• Comparison UI and preset quick-swap reduce friction more than marginal stat tweaks.
• Atomic equip operations prevent limbo items and partial-loadout confusion.
• Harbor Chronicles cut raid prep time by ~67% with five presets, resistance tags, and a dedicated armory screen.

Related reading

• Game inventory systems explained — bags, stacking, and server-authoritative grants
• Game loot tables and weighted random explained — where equipment items enter the economy
• Game crafting systems explained — forging gear that feeds loadout presets
• Game character customization explained — appearance layers alongside stat equipment