Decaying Winter weapons

Decision first

Choose a resource plan before a weapon name.

A weapon choice changes more than damage output. A ranged plan consumes ammunition and competes with other ranged users. A melee plan changes exposure, positioning, and the importance of a fallback when pressure becomes difficult to control. A crafted plan adds a blueprint and resource dependency. The squad should identify those obligations before treating a named weapon as an automatic upgrade.

During scavenging, report a weapon by category and requirement first. “Ranged, needs ammunition” or “crafting route, needs blueprint resources” gives teammates information they can act on even when nobody remembers the current statistics. The named record can be checked after the group knows whether the plan fits its inventory and role coverage.

This method also reduces stale advice. Exact weapon numbers, tier labels, and blueprint locations are vulnerable to updates. Category, ammunition dependency, and the found-or-crafted distinction are the stable facts supported by the research package.

Coverage index

Browse the observed equipment route surface.

The route inventory contains broad category pages, combat guides, crafting routes, and named records. The table preserves that structure. It does not merge “Guns” with “Ranged Combat,” or “Crafting” with “Workbench,” because separate pages can answer different questions even when they belong to the same decision chain.

A row marked as a named record is a lookup lead only. The route title proves that the community surface contains a page with that label; it does not prove current damage, rarity, recipe, spawn location, or availability. Those fields should be populated only after a dedicated source review with a captured date where volatility matters.

Ranged logistics

Make ammunition visible to the whole squad.

Ranged weapons consume ammunition, so the loadout creates a shared logistics problem. Before more than one Agent commits to ranged combat, identify whether the team can support both plans and who will communicate changes in supply. A powerful weapon without a supported ammunition plan can become dead weight during a later defense.

Do not solve the problem by hoarding every ranged resource without context. The squad needs a handoff: who is using the ammunition, what role that player covers, and what fallback remains when supply drops. The perks and traits pages help explain the role; the items page helps separate ammunition-related planning from medical, ration, infection-management, and deployable needs.

• State the ranged user and the role the weapon supports.
• Track shared ammunition pressure instead of treating every pickup as private.
• Keep a melee or non-ammunition fallback when the plan depends on continued supply.
• Recheck current weapon and ammunition details on the dedicated source.

Blueprint chain

Connect blueprints to a return decision.

Weapons can be found or crafted from blueprints according to the community weapons index. Crafting therefore affects scavenging priorities: a promising blueprint route has no value if the squad cannot recover the required material in time to build and distribute the result. Report crafting progress as a missing-resource list, not as a vague intention to search longer.

A fallback should exist for both failure modes. If the blueprint or resources do not appear, the Agent still needs a viable weapon category. If the weapon is completed but the squad cannot support its ammunition or positioning demands, another player should not have to redesign the defense during the wave. A short pre-wave equipment check turns crafting from an isolated goal into a team decision.