Jump to a section
01
Confirm the original announcement before publishing a change
A change is confirmed only when an original Roblox or AA/DW Discord announcement can be linked; community summaries are historical leads, not primary proof.
If a search result claims a 2026 update, new map, new Perk, or balance adjustment without that original link, keep it out of the confirmed timeline.
02
Build an evidence-first timeline
For each verified entry, record the announcement date, version or event name, the change as announced, whether it is still active, and the direct original source. Separate the announcement date from the date a community page was edited.
| Field | Meaning |
|---|---|
| Announced | Date on the original post |
| Change | What the original post actually states |
| Status | Current, ended, reverted, or unknown |
| Proof | Direct Roblox or AA/DW Discord announcement |
03
Label community event records as history
The Wiki records Cultist Takeover as a historical event released on 2025-02-11. That page is useful for understanding the event and locating search terms, but its community classification means it cannot by itself prove a current event or a new update.
- Preserve past-event dates
- Mark ended content clearly
- Re-check the official experience and announcements before saying an event is live
SOURCE DESK
Sources and verification
Authority labels matter. Community references are useful for discovery, while current game text and original announcements remain the final check.
Official announcement channel; link the original post when confirming an update or balance change.
OfficialDecaying Winter on RobloxOfficial game page and experience entry point.
CommunityCultist Takeover WikiCommunity record of the historical Cultist Takeover event; not primary update proof.