Mechanics are the pages most likely to go stale.
Stealing, defense, guild scoring and event systems change between updates. Every entry here carries the date it was last confirmed.
FIELD
NOTES
Why mechanics pages are dated so aggressively
A shop price is stable for weeks; a mechanic can change in a single patch. Stealing windows, protection behaviour and guild scoring rules have all been rewritten between updates, and advice copied from an older video then reads as a bug rather than as outdated information. Each entry therefore states the version or date it was confirmed against, and treats anything older as history.
The second discipline is scope. A community report describes one server at one moment; it is not a global rule. Entries separate what the game documents, what several independent players observed, and what a single report claimed, because a player planning a night cycle needs to know how much weight a statement carries.
Read a mechanics entry as a decision checklist rather than as lore. Confirm the rule is still live, identify what you would lose if it is, and only then spend gear or time on it. The guides translate each mechanic into that checklist; this section keeps the underlying statement and its date so the translation can be audited later.
Category counts are literal
Only pages present in this repository are counted. Missing entries remain visible as coverage gaps.
Stealing guide
Continue with the task-specific tool or guide.
Updates
Continue with the task-specific tool or guide.