Rust January Wipe: A Quiet Reset Before the Naval Storm
The January 1 force wipe kept things light, clearing out holiday content and laying groundwork behind the scenes for February's Naval Update while giving the whole playerbase a clean start to 2026.
Headline feature
Landing on New Year's Day itself, the January wipe was never going to be a huge content drop, and Facepunch treated it that way. This was a full blueprint wipe like the months before it, so everyone started the new year from scratch, rock and torch in hand, with no research carried over from December. The patch itself was deliberately restrained. Rather than shipping new weapons or monuments, the team used the update to clean house and prepare the ground for the much bigger Naval Update due February 5.
What actually changed
The Christmas event was switched off, with holiday items, decorations, and the seasonal NPCs that came with it disabled until next winter. Beyond that, the patch was mostly made up of quality of life tweaks, bug fixes, and performance optimizations rather than any single headline system. Facepunch also used the update as a moment to look back at 2025 and preview what the year ahead had in store, giving players a rough sense of the roadmap without locking in specifics.
Underneath the surface, a chunk of this patch was infrastructure work described as naval prep, meaning code changes that would not be visible to players immediately but were laying the foundation for the boats, deep sea content, and ocean rework planned for February. It is the kind of update that reads thin in patch notes but matters a lot for what comes next.
What this means for the wipe
If you were hoping for a splashy January, this was not that wipe. Servers reset clean on schedule, holiday clutter got cleared out, and the meta stayed largely where November and December left it. The real headline event of early 2026 was always going to be February's Naval Update, and January functioned as the calm, structural lead in to it.