Decaying Winter enemies

Threat vocabulary

Begin with the official threat families.

The official experience description names hostile scavengers, militarized raiders, and seemingly supernatural enemies. Those phrases are broad enough to orient a new player and stable enough to anchor the archive. The current community enemy index uses Scavengers, Raiders, and Reikgons as its main hostile categories, which provides a bridge from official language to the route surface players already search.

The bridge is useful, but it is not a license to merge every record. A named enemy, a boss-wave page, a combat guide, an event route, and a general category page can all require different fields and update dates. The table below preserves the observed label and family clue so a future detailed entry can bind mechanics to the right source.

During play, use the shortest verified term the squad understands. The goal is to direct attention and action, not to recite a taxonomy during a wave. Detailed behavior belongs in preparation or post-run review.

Observed records

Use the observed record table as a lookup map.

The inventory includes category routes, named records, combat guides, boss waves, raids, and updated-title variants. Each row below is therefore a pointer, not a complete profile. The “family” column reflects wording supported by the official or community taxonomy, while the boundary column states what must still be checked.

Duplicate-looking labels are retained when the route surface retains them. “Shadow” and “Shadows ?” might be related, and “Wave Ultima” has an updated-title variant, but deduplication without opening the sources could erase a redirect, historical page, or distinct record. A verified entity page should resolve that relationship explicitly.

Squad communication

Turn a record into a useful callout.

A field callout needs three parts: the threat label, the direction or pressure area, and the requested response. If the name is uncertain, use the broader family rather than guessing. “Raider pressure on the return path” is more useful than confidently naming the wrong record. The enemy index can settle terminology before the next cycle.

The response should describe a team action: regroup, preserve distance, change target priority, protect a resource carrier, or abandon a detour. Exact tactical advice depends on current mechanics and the live situation, so it belongs to a verified record. The stable wiki contribution is a shared vocabulary and a clear route to the evidence.

• Use a broad official or community family when the named record is uncertain.
• Add direction and the action you need from teammates.
• Separate boss-wave, event, and ordinary hostile records during research.
• Recheck current behavior before turning a callout into a permanent rule.

After-action record

Review the first recognition failure.

After a failed defense, identify the earliest threat-information failure. Did the squad use different names for the same family? Did a named record create a positioning change nobody communicated? Did an event or boss-wave page get mistaken for an ordinary encounter? Did the team commit supplies before understanding the pressure? One precise question produces a better update than a broad request for “all enemy stats.”

Open the dedicated record, capture the source date, and add only the fields the squad needs: identity, family, encounter scope, recognition cues supported by the source, and the response that follows from verified mechanics. This approach grows the database through real use while avoiding fabricated portraits or copied stat walls.