Decaying Winter items

Supply logic

Classify an item by the decision it changes.

A useful item report tells the squad what decision becomes possible. Medical and infection-management records answer health-related needs but should not be collapsed into one vague category. Rations and drinks answer another part of sustain. Deployables change the safe-zone plan. Crafting resources and salvages support a blueprint chain. Utility records can change movement or preparation, yet their exact use must come from a current source.

During scavenging, report the family before the detailed name when time is limited. “Deployable defense returning,” “infection-management supply,” or “crafting resource for the blueprint plan” lets the team assign ownership and storage. The exact record can be checked when it affects placement, timing, or compatibility.

This classification also prevents waste. Two players can return with useful items that solve the same problem while another critical category remains empty. A shared supply board, even if it exists only as spoken handoffs, makes those gaps visible.

Observed supply surface

Browse named records with their source boundary attached.

The observed route inventory includes named rations, drinks, medical and infection-management indexes, deployables, utility equipment, loot containers, and crafting resources. The table groups those labels only where the wording supports a family clue. It does not fill in effects, quantities, rarity, or locations from memory.

A named record becomes a complete item entry after verifying its current function, use timing, acquisition context, stack or charge behavior when relevant, interactions, and update date. Until that review exists, the safe value of the row is discoverability: the player can find the right source instead of relying on an unsupported summary.

Safe-zone handoff

Assign supplies before the wave.

Distribution should follow role and timing. A supply that must be used under pressure belongs with an Agent who can reach the expected situation. A deployable needs an agreed location and trigger. A crafting resource needs to reach the player or station responsible for the blueprint plan. A ration or medical record should not disappear into private inventory if the squad is relying on it as a shared reserve.

Use a short handoff: item family, owner, intended moment, and fallback. This makes tradeoffs visible when the team cannot support every plan. It also reduces duplicate use, because everyone knows whether a resource is committed or protected.

• Name the supply family and intended user.
• State whether it is immediate-use, reserve, deployable, or crafting material.
• Tie deployables to a position and a trigger before pressure arrives.
• Recheck named mechanics on the dedicated current source.

Feedback loop

Let missing supplies shape the next search.

After defense, update the next scavenging plan from what the squad actually lacked. If ammunition constrained ranged users, the weapons route owns the equipment decision while this route records the supply gap. If sustain failed, separate general healing, infection management, rations, and drinks instead of asking for “more items.” If a deployable arrived too late, the problem may be return timing rather than item choice.

This feedback loop keeps the database connected to the walkthrough. Items are not collectibles in the archive; they are recovered resources inside a cycle of search, return, distribution, defense, and evacuation. A detailed item page should explain exactly where its verified effect changes that cycle.