Rust's November 2026 update is unusually relevant to dedicated server operators. Beyond new weapons and gameplay changes, Facepunch describes a broad optimization effort spanning CPU, memory and networking. The update is already live, not a staging-only preview.
This guide separates what Facepunch measured from what a server owner can reasonably expect, and identifies the most important checks for community and modded servers.
Rust's November 5 update is live, with meaningful networking improvements and a major progression redesign.
Facepunch released Printed and Polished on November 5, 2026. Its published staging measurements include up to 25% less network traffic in a 500-player test and a substantial reduction in building-privilege lookup time. The patch also changes how workbench technology trees consume blueprints. Server owners should update, check mod compatibility, and measure real post-update network and CPU behavior rather than assuming the advertised benchmarks apply to every server.
Rust PC dedicated servers and modded communitiesRelease status: live November 5, 2026
Facepunch published Printed and Polished on November 5, 2026 as its monthly Rust update. The studio describes it as one of its largest optimization-focused releases. It includes a blueprint progression overhaul, new Uzi 9mm, gamepad support, and numerous performance improvements.
The official performance figures are explicitly based on staging data. They are useful indicators, not guarantees that any particular hosted server will see identical results.
What the networking improvements actually mean
Facepunch reports up to 25% less network traffic on a 500-player server in its staging measurements. This is an example at a particular scale, not a universal 25% bandwidth reduction or a promise of higher player capacity.
Operators should compare outbound and inbound network usage under similar concurrent player loads, with the same map and plugins, before and after the update. Peak usage, connection quality, and entity-heavy locations matter more than a single idle bandwidth reading.
Building privilege lookups received a major optimization
Facepunch replaced repeated physics queries for building privilege with a grid-based lookup. In its cited large-base case, the check fell from 5.7 milliseconds to under 0.02 milliseconds on both server and client. That is a per-operation benchmark, not a claim that whole-server tick time improved by the same percentage.
This could be particularly relevant around large compounds and dense building activity. If your community previously saw lag while placing blocks or moving around massive bases, capture before-and-after server metrics and check for improvements.
Be careful interpreting the RAM and FPS numbers
The developer's headline performance summary also cites roughly 1.6 GB less total memory use, a roughly 10% higher median player framerate, and garbage collection occurring about half as often in staging tests.
Much of the accompanying detail concerns client rendering, asset loading, audio, and animation. These figures should not be advertised as a guaranteed 1.6 GB reduction in dedicated-server RAM requirements or a 10% increase in server tick rate. Profile the Rust server process separately from the game client.
Blueprint progression changed: review custom server rules
Workbenches no longer require blueprint fragments to craft, and scrap is no longer spent on technology trees. Facepunch now uses three blueprint tiers: fragments, pages, and books. Research tables still allow researching items with scrap.
Server owners running custom progression, loot-table, shop, or economy plugins should check whether their plugins reference old blueprint costs or workbench behavior. Test changes in a staging environment and review the plugin author's release notes before changing live configurations.
Dedicated server checklist after the update
Before restarting, save and back up your world and plugin configuration. Follow your host's established update procedure and allow the official server build to install. After launch, inspect startup logs, verify players can connect, and confirm that your modding framework and key plugins are compatible.
Test building privilege around dense bases, blueprint unlocks, research and workbench interactions, and any custom loot or progression systems. Compare network throughput and server processing under representative player load. If a plugin breaks, preserve logs and report the precise versions to its maintainer rather than deleting your world.
Facepunch's patch does not establish a new universal minimum RAM figure, guaranteed slot increase, or automatic requirement to wipe a community's persistent data. Keep wipe decisions separate from the update itself.
A couple more questions
Is the November 2026 Rust update live?
Yes. Facepunch published Printed and Polished on November 5, 2026. The performance numbers cited in its post are staging-test measurements.
Will my Rust server use 25% less bandwidth?
Not necessarily. Facepunch reports up to 25% less network traffic in a 500-player staging test. Your results depend on player count, world activity, and server configuration.
Does the update mean Rust servers need 1.6 GB less RAM?
No universal dedicated-server RAM reduction has been established. The published memory improvement should not be directly converted into a new hosting minimum.
Should I wipe my Rust server for this update?
Follow your community's established wipe policy and any official update requirements. The performance figures alone do not justify wiping player data.
Sources & useful links
The technical details behind this guide, if you want to dig further.
Keep reading
Ready to start your Rust journey?
Put what you learned into action with a server built for your next adventure.
View Rust plans