Decaying Winter is a wave-based roguelike co-op survival experience set on EDEN-227. This field archive organizes the verified survival loop, player-facing systems, official media, and carefully bounded community reference coverage into routes that answer one task at a time.
Start here
Pick the next useful page.
The core loop
Scavenge, return, defend, repeat.
The official experience description establishes a hostile planet, a lethal daytime storm, hostile scavengers, militarized raiders, supernatural opposition, and an evacuation objective. The useful way to read those facts is as one connected pressure system. A squad leaves safety because the next defense needs resources. It returns because the open window is limited. It defends because progress depends on surviving the next wave rather than winning an isolated encounter far from the group.
That rhythm makes information timing important. A weapon entry matters when it clarifies whether the team is committing to melee or consuming ammunition. An item entry matters when it helps decide what should come back to the safe zone. A perk or trait reference matters when it clarifies a role before the squad disperses. This wiki therefore keeps route titles narrow: the walkthrough explains sequence, while the databases support a choice inside that sequence.
A new player should begin with the walkthrough, then open the weapons, items, perks, traits, or enemies route only when a specific decision appears. Experienced players can reverse that order and use the homepage as a compact index. Both paths lead back to the same verified loop instead of presenting disconnected pages as if they were separate games.
Squad method
Use the five-player limit as a planning tool.
The Roblox experience API reports a maximum server size of five. That number does not prescribe one perfect composition, but it gives the squad a practical ceiling for task ownership. Before leaving the safe zone, decide who is collecting broadly, who is watching the return window, who is preserving supplies, and who is preparing to anchor the defense. Clear ownership reduces duplicate detours and makes missing resources visible before the storm closes the decision window.
Loadout pages are most useful when read as coordination records rather than isolated rankings. The perks index records four role groups in current community data: Basic, Frontline, Backline, and Support. The traits index records a limit of three active traits. Those two facts support a conversation about coverage, but they do not justify a universal tier list. The archive focuses on questions a squad can answer together and leaves volatile effect values to a fresh source check.
- Name one primary task for each Agent before the scavenging window opens.
- Treat ammunition as a shared constraint when more than one player wants a ranged plan.
- Return useful supplies early enough that the defense can place and distribute them.
- Use the enemy index for recognition and terminology, not as a promise of fixed spawns.
Source discipline
Read the evidence boundary before the detail.
This site separates first-party facts from community-index coverage. First-party records confirm the experience name, universe, setting, survival genre, maximum server size, input requirement, broad threat language, evacuation objective, and official media. Community pages expand the browsable surface with perk, trait, weapon, enemy, item, character, mode, event, and ending records. Those indexes are valuable for navigation, yet an observed page title alone does not prove a current statistic or mechanic.
For that reason, database rows on this build emphasize record names, source families, and the exact question a player should verify before acting. The approach is deliberately conservative. It prevents a legacy route, event page, historical status entry, or duplicate title from silently becoming evergreen gameplay advice. It also keeps future updates small: a changed mechanic can be corrected in its dedicated route without rewriting the site’s core description.
4 records
| Record | Evidence boundary | Use in this archive |
|---|---|---|
| Setting, objective, server size, input | Official Roblox records | Safe for stable orientation with a captured date where needed |
| Perk and trait counts | Current community indexes | Coverage summary; recheck before freezing a volatile value |
| Named weapons, items, enemies, characters | Observed community route surface | Lookup leads; detailed claims need a page-level source check |
| Official screenshots and video | Receipt-bound media manifest | Editorial context with recorded publisher and publication URL |
Official field record
Use official media without turning it into invented lore.
The official experience media API supplies the image set used across this archive and lists a YouTube video titled “Decaying Winter - Last Strandeds.” Images are assigned to routes in the media manifest so a combat frame, Agent scene, key art, or experience icon supports the page where it has the clearest editorial role. The same image is not multiplied into fabricated portraits, item cards, map diagrams, or cosmetic variants.
The video facade below loads only a thumbnail at first. The privacy-preserving player is mounted after an explicit click, and the official YouTube watch link remains visible. This keeps the page responsive while preserving the source connection. Mode details stay on the game-modes route because a title in the official gallery is evidence that the media exists, not permission to generalize every mechanic from the video label.
Official experience video ·Open on YouTube
Frequently asked questions
What should a new Decaying Winter player read first?
Start with the walkthrough because it explains how scavenging, the return window, defense, and evacuation fit together. Open the equipment and loadout databases only when the walkthrough raises a concrete choice. This sequence avoids memorizing isolated names before you understand why the squad needs them.
Does this wiki claim every community page is current?
No. Community route names are used to organize coverage and locate subjects that deserve a dedicated source check. Stable claims come from the official Roblox experience records when available. Counts or classifications taken from a community index are labeled by their source boundary and should be rechecked after game changes.