Guide
Game item durability and repair systems explained
Harbor Outpost shipped with indestructible iron swords. Players crafted once, never returned to the forge, and vendor buy prices collapsed because surplus gear flooded every stall. The refactor added per-instance durability on weapons and armor, wear-on-hit for melee and wear-on-block for shields, a repair bench that consumed scrap metal, and a broken state that blocked equip until restored. Session length rose 18% and scrap became the economy’s top sink — not because players enjoyed watching bars drain, but because wear created a reason to revisit hubs, talk to vendors, and plan loadouts before long expeditions.
Durability is a counter on item instances that decreases with use, absorbing hits, or environmental exposure until the item breaks or loses effectiveness. Repair restores that counter through stations, consumable kits, currency, or NPC services. Together they regulate item lifespan, tie combat to economy sinks, and give meaning to crafting beyond the first craft. This guide covers wear triggers and curves, break thresholds, repair pipelines, UI patterns, multiplayer authority, the Harbor Outpost refactor, a technique decision table, pitfalls, and a production checklist.
Why durability exists: sinks, tension, and return trips
Without wear, the best item a player ever crafts stays best forever. That flatters early crafters but starves mid-game loops: vendors sell nothing, gathering feels pointless, and raid drops compete with gear players already own. Durability introduces recurring cost — materials, currency, or time spent at a bench — that pulls value out of circulation and rewards preparation.
Design goals durability commonly serves:
- Economy sink — scrap, repair kits, and vendor fees remove currency and mats from the world.
- Expedition pacing — “Can my kit survive this dungeon?” adds stakes before a long run.
- Item tier differentiation — higher tiers last longer or repair cheaper, making upgrades feel tangible.
- Soft inventory rotation — backup weapons matter when the primary breaks mid-fight.
The failure mode is punitive friction: invisible wear, sudden zero-durability deletes, or repair costs that exceed replacement. Players should always see wear coming and have at least two recovery paths (bench, kit, vendor, or salvage-and-recraft).
Wear triggers: on-use, on-hit, on-block and environmental
Pick one primary trigger per item category and document it in data so designers do not stack hidden multipliers:
| Trigger | Typical items | Feel |
|---|---|---|
| Wear-on-use | Pickaxes, fishing rods, harvesting tools | Predictable; one point per successful action |
| Wear-on-hit (dealt) | Swords, bows, guns | Scales with combat intensity; tune per swing or per shot |
| Wear-on-hit (received) | Armor, shields | Tanks feel maintenance cost; pairs with block systems |
| Wear-on-block | Shields, parry tools | Rewards defensive play without punishing every chip |
| Environmental | Climbing gear, diving suits | Time-based drain while in hazard zones |
Wear curves map actions to durability loss. Linear (1 point per hit) is easy to reason about. Percentage-of-max (lose 0.5% per hit) keeps high-tier items feeling premium. Flat plus random jitter (−2 ± 1) adds texture but complicates player mental models — use sparingly.
Cap wear per frame in multiplayer: a lag spike that replays twelve hits should not apply twelve times if your netcode already consolidated damage. Server authority should increment durability once per validated combat event.
Break states: soft degrade vs hard break
When durability reaches zero, choose a break policy and stick to it:
- Soft degrade — item stays equipped but stats drop (50% damage, no set bonuses). Player can finish the fight but feels urgency. Common in MMOs.
- Hard break — item unequips or becomes unusable until repaired. Strong in survival sandboxes where backup gear matters.
- Destroy on break — instance deleted; player keeps salvage mats. High stakes; pair with clear UI warnings above 10% durability.
Store current_durability and max_durability on the item
instance, not the static definition. Max can rise with upgrades or quality tiers
from
crafting.
Optional broken flag prevents edge cases where 0-dur items still
contribute stats after a failed repair rollback.
Link break states to equipment validation: equipping a broken item should fail with a reason, not silently strip stats.
Repair pipelines: stations, kits, vendors and salvage
Repair is a transaction like crafting or vendor purchase. Define a repair recipe schema:
- Input — damaged instance ID, optional materials (scrap metal × 3), optional currency (50 gold).
- Output — same instance with
current_durability = max_durabilityor partial restore (+25%). - Gate — requires repair bench, NPC blacksmith, or consumable repair kit in bag.
- Authority — server validates ownership, material stock, and item not in trade lock.
Common repair modes:
- Full restore at bench — cheapest per point when at hub; unavailable in combat zones.
- Field repair kit — restores 30–50%; consumed on use; premium sink for expeditions.
- Vendor instant repair — gold sink with convenience tax; good for players who skip crafting.
- Salvage and recraft — below 5% durability, offer dismantle for 60% mats instead of expensive full repair.
Partial repair matters for long sessions: restoring to 80% at lower mat cost feels fairer than binary full-or-nothing pricing. Show cost before confirm; never deduct mats on a failed validation.
UI patterns: bars, color bands and pre-expedition warnings
Durability UI should answer three questions at a glance: how much is left, when will it break, and what does repair cost?
- Slot bar — thin durability strip under item icon in equipment and bag; green > 50%, yellow 20–50%, red < 20%.
- Tooltip breakdown — “Iron Sword: 34/120 (28%). Repair: 2 scrap.”
- Expedition summary — before zone entry, flag any equipped item under 25%; one-click “repair all at bench” if in safe hub.
- Combat feedback — subtle chip sound or icon flash on break threshold cross; avoid modal interrupts mid-boss.
Accessibility: do not rely on color alone; add icons or text labels for low durability. Controller focus should reach repair actions without mouse-hover tooltips.
Multiplayer authority and duplication safety
Durability changes must ride the same authoritative path as damage and loot grants. Client may predict bar animation; server commits the integer. Race conditions to guard:
- Repair and equip in the same frame — serialize on item instance lock.
- Trade window open while durability hits zero — block trade of broken items or auto-cancel with message.
- Duplicate repair requests from double-tap — idempotent repair token per operation.
- Logout with pending wear — flush durability delta in combat log before save.
Log every repair transaction (player ID, instance ID, mats consumed, before/after values) for economy audits and duped-item investigations.
Harbor Outpost gear loop refactor
Pre-refactor pain points from economy telemetry and playtests:
- Iron sword craft rate 4.2× higher than intended sink rate; vendor sell tab unused.
- Expedition abandonment spiked when players ran out of gathering tools mid-route with no warning.
- Backup weapon slots empty in 71% of loadouts because gear never degraded.
Changes shipped:
- Weapons: −1 durability per confirmed hit; armor: −1 per 10 damage taken (floored).
- Soft break at 0% (50% stats); hard unequip only if player ignores repair through two hub returns.
- Repair bench recipe: scrap proportional to missing durability points.
- Field kits sold at Outpost vendor (tied to reputation discount).
- Expedition gate warns if any equipped item < 30% before leaving safe zone.
Post-patch: vendor scrap purchases up 3.1×, median session return-to-hub interval fell from 47 to 31 minutes (healthier pacing), and backup weapon equip rate rose to 44%. Player sentiment improved when repair costs stayed below 40% of recraft cost — a tuning rule the team now encodes in data validation.
Technique decision table
| Approach | Best when | Avoid when |
|---|---|---|
| No durability | Roguelikes with short runs, narrative adventures | Persistent MMOs needing mat sinks |
| Tools only (gathering wear) | Survival crafters, light combat focus | Combat-heavy looter RPGs |
| Full gear wear + repair | MMOs, survival sandboxes, expedition loops | Casual mobile sessions under 5 minutes |
| Repair kits only (no benches) | Action games with field maintenance fantasy | Games with strong hub crafting identity |
| Destroy on break + salvage | Hardcore survival, high-stakes PvE | Competitive PvP with gear unlock grind |
| PvP-only durability | Separating casual PvE from ranked wear tax | Unified economies without split rules clarity |
Common pitfalls
- Surprise zero — item breaks mid-swing with no sub-20% warning; players rage-quit.
- Repair costs more than recraft — undermines the system; cap repair at 40–60% of craft cost unless destroy-on-break.
- Client-authoritative wear — exploiters freeze durability; server must own deltas.
- Stacked wear multipliers — on-hit plus on-use plus environmental on the same sword; designers lose tuning control.
- Broken items in loot tables — drops at 0% durability feel like insult loot.
- Ignoring loadout presets — apply preset with broken primary and no fallback plan; validate or warn.
- PvP durability without repair access — ranked players priced out; offer cheap arena bench or normalize to full before match.
- No sink for repair mats — scrap hoarding reinflates the economy you tried to fix.
Production checklist
- Store durability on item instances; max scales with tier or upgrades.
- Document one primary wear trigger per item category in data schema.
- Server-authoritative wear on validated combat and use events.
- Define soft vs hard break policy; block equip of hard-broken items.
- Repair as atomic transaction with material and currency validation.
- Show durability bars, color bands, and repair cost in tooltips.
- Expedition warning when any equipped item below threshold.
- Cap repair price relative to recraft; offer salvage under threshold.
- Log repair transactions for economy audits.
- Playtest full expedition loop: craft, wear, repair, vendor, recraft.
Key takeaways
- Durability creates recurring economy sinks and gives players a reason to return to hubs, vendors, and crafting benches.
- Pick clear wear triggers per item type; server authority prevents dupes and frozen-bar exploits.
- Soft degrade feels fairer than surprise deletes; always warn before hard break or destruction.
- Repair must cost less than recraft for the same power, or players bypass your loop entirely.
- Harbor Outpost tied scrap demand to proportional repair and expedition warnings, balancing pacing without punitive friction.
Related reading
- Game equipment and loadout systems explained — slot validation when items break or degrade
- Game crafting systems explained — recipes, mats, and recraft as repair alternative
- Game shop and vendor systems explained — selling repair kits and convenience repairs
- Game inventory systems explained — instance storage and transactional item grants