Rust Jobs 3 Migration Guide for Modded Servers

Facepunch made UsePlayerUpdateJobs 3 the default in Rust's July 2, 2026 "Common Ground" update. Jobs 2 is deprecated and scheduled for removal in August; after its removal, selecting mode 2 will run mode 3 underneath.

This creates a compatibility deadline for modded servers. Facepunch says it rewrote how server player state is passed around and that server mods will need corresponding code updates.

What changed

Facepunch identifies five principal Jobs 3 improvements:

• UniTask is used to avoid allocations from multithreading code.
• Per-frame player snapshot sending is accelerated through a new fuzzy pool and removal of buffer preallocation.
• Parts of player network subscription updates run in parallel.
• EAC and analytics tasks are scheduled earlier to avoid making the main thread wait for them.
• The remaining server anti-hack logic is parallelized.

The official changelog records the staged rollout. It recognized UsePlayerUpdateJobs level 3 in the April 2, 2026 "Spring Clean" update, citing UniTask and parallelization of anti-hack and network streaming. The June 4, 2026 "Built Different" update removed the level 0 and 1 code paths, and "Common Ground" made level 3 the default.

The changelog also states that skipping NetWrite preallocation can save 0.6 milliseconds on busy frames.

Recommended migration response

Because Facepunch explicitly says the player-state rewrite requires server mods to update, operators should identify affected mods, obtain compatible releases, and test the complete mod stack with Jobs 3 before deployment. Any rollback plan should not depend on Jobs 2 remaining a distinct execution mode.

A focused migration review should confirm that:

• Every installed mod and dependency has a recorded version and update source.
• Maintained Jobs 3-compatible releases have been identified and tested.
• Mods without compatible updates have a replacement or removal plan.
• The final mod combination starts and operates under Jobs 3 without unresolved compatibility errors.
• Server data and configuration are backed up before production deployment.

Continue monitoring official Facepunch notices and follow sourced Rust coverage on TOP OF GAMES for future server-maintenance developments.