Guide

Game encumbrance and weight systems explained

Harbor Siege's Bastion of Ash update added a co-op supply route: players hauled ore from a mine to the fortress forge while waves attacked the caravan. Analytics showed 38% of runs abandoned mid-route — not because combat was too hard, but because a single ore stack weighed 40 units against a 50-unit carry cap. Players could not pick up healing kits after the first haul, slowed to a crawl at 90% capacity, and quit rather than make a second trip. The encumbrance model treated weight like a spreadsheet column instead of a pacing tool.

Encumbrance is any rule that limits how much a character can carry and optionally punishes excess load with slower movement, higher stamina drain, blocked actions, or disabled fast travel. It sits between your inventory data layer and the moment-to-moment feel of looting, crafting, and traversal. This guide covers encumbrance taxonomy, penalty curves, integration with pickup pipelines and stamina, the Harbor Siege refactor, a technique decision table vs slot-only caps, pitfalls, and a production checklist.

Encumbrance taxonomy

Teams mix these patterns; knowing which you ship prevents accidental double punishment.

Model	What is limited	Typical feel
Slot-only	Fixed bag cells (grid or list slots)	Diablo-style tetris; no movement penalty
Hard weight cap	Sum of item weights cannot exceed max	Skyrim, many survival RPGs; pickup blocked at cap
Soft weight tiers	Penalties ramp between thresholds (light / burdened / overburdened)	Fallout, ESO; still playable but costly
Category quotas	Separate limits per type (ammo, materials, quest items)	Destiny resource caps; reduces one-category hoarding
Volume / bulk	Large items consume multiple slots or cubic units	Resident Evil attache case; spatial puzzle
Virtual / account stash	Weightless bank; only active loadout encumbered	MMO bank tabs; separates hoarding from combat load

Weight and slots are not mutually exclusive. A common RPG pattern: slots gate unique gear while weight gates stackable materials — but both must read clearly in UI or players blame the wrong system when pickup fails.

What weight should affect

Movement and animation

The classic encumbrance penalty slows walk and sprint speed, disables dodge rolls, or plays a heavy-footstep animation set. Apply penalties as a multiplier on base move speed, not a flat subtraction, so buffs and debuffs stack predictably. Cap the slowest speed (e.g. never below 40% of base) unless you intentionally want an overburdened crawl for comedy or hardcore modes.

Stamina and action economy

Burdened characters can pay extra stamina per sprint tick, jump, or dodge. This punishes combat while looted without making traversal unbearable in safe hubs. Link weight tier to regen rate: overburdened players recover stamina 30–50% slower so kiting remains possible but risky.

Pickup and interaction gates

Decide per item class: block pickup entirely, allow pickup but auto-drop lowest-value stack, or permit temporary overcap with immediate penalty. Your pickup pipeline should return a structured reason (“over weight by 12”) so UI and audio feedback match the failure mode.

Fast travel, mounts, and vehicles

Many RPGs disable fast travel while overburdened to force a dump at a stash. Mounts and pack animals can add a secondary weight pool that does not slow the rider — a progression unlock that turns encumbrance from friction into build choice.

Designing penalty curves

Let r = currentWeight / maxWeight (load ratio). Three sane curves:

Step tiers — no penalty below 0.75; −15% speed from 0.75–1.0; block sprint above 1.0. Easy to communicate in UI.
Linear ramp — speed multiplier = 1 - 0.4 * max(0, r - 0.5). Smooth but harder to explain without a meter.
Exponential cliff — gentle until r > 0.9, then harsh. Discourages “one more ore” without early annoyance.

Playtest with realistic hauls, not empty bags. A curve that feels fine during tutorial combat breaks when a boss drops four rare pieces and pushes r from 0.6 to 1.1 in one frame. Consider a 3-second grace window after pickup before penalties apply so animation and UI can catch up.

Item weight assignment

Weight values are a design lever, not physics simulation:

Quest and key items — weight 0 or a dedicated quest pouch that ignores caps. Blocking story progress because a key weighs 5 units is never worth it.
Currency and tokens — weightless; track in account wallet.
Stackables — weight per unit × stack count; round per-unit values to integers players can mental-math.
Equipment — often zero while equipped (worn weight) and nonzero in bag; document the rule so loadout swaps do not surprise players.
Materials vs gear — ore and lumber should be heavy; magic rings light. Tuning here shapes how often players return to town.

Export a spreadsheet: item id, weight, stack max, category, soulbound flag. Balance passes sort by weight-per-gold or weight-per-power to catch outliers.

UI and player communication

Encumbrance fails when players discover penalties accidentally:

Always-visible meter — numeric 47 / 80 plus a color band (green / yellow / red). Icon-only bars confuse.
Preview on hover — loot tooltip shows “+12 weight (would burden you)” before pickup.
Tier labels — “Light,” “Burdened,” “Overburdened” with consistent copy in HUD, settings, and tutorial.
Sort and dump tools — “Send materials to stash,” sort by weight descending, quick-drop junk filter. Friction without tools reads as bad UX.
Audio cue on tier change — subtle clink when crossing into burdened; distinct only for overburdened.

Multiplayer and authority

Server must own weight totals. Clients predict pickup for responsiveness but roll back if the grant would exceed cap. In co-op, personal encumbrance is per-player; shared crate weight is a separate pool with its own max so one hoarder cannot slow the whole squad. Replicate only the tier enum and totals, not per-item weight recalculation every frame.

When one player revives another, decide whether downed loot drops reduce victim weight automatically or require manual strip — ties into downed state design.

Harbor Siege supply-run refactor

Pre-refactor: single 50-unit cap, linear speed penalty from 70% load, ore at 40 units per stack, healing kits at 8. One ore stack plus starter gear left 2 units free — not enough for kits after the first pickup. Abandon rate on the supply route: 38%.

The refactor:

Split pools — combat loadout (slots + 30-unit combat weight) separate from mission cargo (60-unit caravan pool that does not affect dodge or sprint).
Step tiers on combat pool only — cargo weight never slows movement; failing the caravan cap blocks only additional ore, not consumables.
Ore stack size — reduced to 20 units with higher stack count so players make multiple lighter trips or invest in pack-mule upgrade.
Pickup preview — world ore shows projected caravan fill bar before interact.
Stash at mine entrance — one-click deposit overflow without full menu navigation.

Post-refactor: supply-route completion rate rose from 62% to 89% over two weeks. Average trips per successful run went from 1.4 (many failed) to 2.1 (intentional pacing). Combat kit usage normalized because healing items always fit the combat pool.

Technique decision table

Approach	Best when	Risk
Slot-only (no weight)	Action RPGs, looter shooters, fast pacing	Grid frustration; less “realism” for survival fans
Hard weight cap	Survival, extraction, sim RPGs	Hard stops mid-combat feel awful without stash nearby
Soft tiers + hard block	Open-world RPGs, co-op haul missions	Needs clear UI; double-stacking with slot limits confuses
Weightless account stash	MMOs, live-service collection games	Reduces tension unless active loadout still matters
No encumbrance	Arena shooters, narrative adventures	Loot volume can trivialize resource scarcity goals

Common pitfalls

One heavy quest item blocks the whole loop. Exempt keys or use quest pouches.
Penalties stack with other slows. Encumbrance + mud + debuff can freeze movement; multiply with a floor.
Pickup fails silently. Always surface weight, slots, and category in the denial message.
Equipped gear double-counts. Document worn vs carried weight rules.
No dump path mid-mission. If you punish carry, provide stash, send-to-bank, or destroy-junk flow.
Co-op shared blame. One player's hoard should not slow allies unless design explicitly calls for shared caravan weight.
Patching weights without migration. Changing ore from 40 to 20 leaves existing stacks over cap; clamp or split on login.

Production checklist

Encumbrance model chosen and documented (slots, weight, tiers, pools).
Item weight table reviewed; quest/currency items exempt.
Penalty curve playtested at 0.5, 0.85, 1.0, and 1.15 load ratio.
HUD meter with numeric fraction and tier label.
Loot tooltip previews weight impact before pickup.
Pickup pipeline returns structured failure reasons to UI.
Stash, mount, or caravan extension progression defined.
Fast-travel and dodge rules per tier documented.
Server-authoritative weight validation on all grants.
Co-op personal vs shared weight pools specified.
Sort-by-weight and quick-deposit tools in inventory UI.
Balance pass: weight-per-minute on core farming routes.
Migration plan for live weight retunes.

Key takeaways

Encumbrance is a pacing tool, not a realism checkbox.
Separate combat load from mission cargo when co-op hauling matters.
Soft tiers teach; hard blocks need stash or dump paths nearby.
UI preview prevents “why can't I pick this up?” rage quits.
Server owns totals; clients predict with rollback.