Rust Optional Client & Server Update
November 19: Mounted Projectile Fixes, Storage Adaptors & A Unity Upgrade
Facepunch released an optional client and server update for Rust on November 19, 2026. It is not a forced wipe and it does not change the game's content, but it does fix a set of combat and building bugs, cleans up the combat log, and moves the client to a newer Unity version.
Optional updates are easy to skip. This one is worth applying anyway, because the projectile fixes affect mounted combat and the Unity upgrade can affect mods and performance. Here is the full list.
🔧 What Changed
- Fixed invalid projectiles while on horseback and other mountables. Shots that should not have been possible are gone.
- Fixed invalid projectiles when shooting players mounted to boogie boards and innertubes.
- Fixed a rare issue causing building blocks to not render.
- Fixed an issue with catapult launched players.
- Fixed storage adaptors sometimes saying "requires power to sort" when already powered.
- Fixed various errors.
- Combat log now uses weapon short names.
- Upgraded to Unity 6000.3.28f1.
🎯 Why These Fixes Matter
Mounted combat has been a recurring source of odd shots in Rust. Arrows and bullets fired from horseback, boogie boards and innertubes could register in ways that felt unfair on the receiving end, and those cases are now blocked. The catapult fix is in the same family: players launched by a catapult should no longer produce broken projectile or movement states.
The storage adaptor fix is smaller but more visible in daily base life. If you have ever seen an adaptor claim it needs power while sitting next to a powered connection, that message should now be accurate.
The combat log change is the one that matters for server tooling. Using weapon short names makes logs easier to parse for Discord relays, stat trackers and admin plugins that read combat logs - but it can also break a parser that expected full weapon names, so check your integrations after updating.
🧩 The Unity Upgrade
The client has moved to Unity 6000.3.28f1. Facepunch ships engine upgrades fairly often, and they usually arrive with a handful of follow-up fixes in the next optional update. For server owners the practical advice is simple: update both the client and the server, then give your plugins a test on a staging copy before rolling out to the live server - especially if you run Oxide, uMod or Carbon plugins that touch UI, rendering or input.
🖥️ What This Means For Your Server
- It is optional, so plan it. No forced wipe is attached to this update. You can update on your normal maintenance window instead of an emergency restart.
- Update the server and the client together. A mismatched optional build will block players from joining, so tell your community when you plan to switch.
- Test plugins after the Unity change. Engine upgrades are the most common cause of plugin breakage. Load your plugin stack on a staging server first, then update live.
- Check combat log integrations. If your Discord relay or stats plugin parses weapon names, verify it still reads the short names correctly.
- Watch mounted combat reports. The projectile fixes are the kind of change players notice immediately in PvP. Expect fewer "that shot should not have hit" complaints, and fewer false reports to review.
If you want a Rust server that can absorb optional updates without downtime drama, our Rust hosting plans are ready to deploy - with the plugin stack and performance headroom this game asks for.
Conclusion
The November 19 optional update fixes mounted and catapult projectile issues, a rare building block rendering bug, storage adaptors falsely reporting they need power, and assorted errors, changes the combat log to weapon short names, and upgrades the client to Unity 6000.3.28f1. It is optional, it is not a wipe, and it is still worth applying on your next maintenance window.