Oxide.Rust 2.0.7676 Released for Rust Server Hosts
Oxide.Rust 2.0.7676 brings hook adjustments and permission fixes for every modded Rust server following the 2633.288.1 client update.
OxideMod has published release 2.0.7676 of Oxide.Rust, providing compatibility with the September 3rd Rust update (2633.288.1). The build introduces new plugin hooks, modifies existing cooking hooks, and corrects permission verification logic across community instances.
Anyone operating a modded Rust server requires this framework update to keep plugins functioning cleanly against the latest protocol. If you run a custom community node, you can also register it on our Add Your Server page or track broader updates on the JoinGG blog.
Hook Additions and Deprecations
According to the Oxide.Rust project repository, the release adjusts how developers monitor container cooking and world interaction:
- The hook
OnComposterUpdateis now deprecated in favour ofOnOvenCook. - A new hook,
OnPlayerDigComplete, has been introduced forBaseDiggableEntity. - New power grid hooks,
OnPowergridStageChange(d), have been implemented.
Plugin developers targeting composters will need to transition logic over to OnOvenCook in future revisions to avoid unhandled deprecation notices or broken event flows.
Internal Bug Fixes and Method Refactoring
The 2.0.7676 build also delivers core bug fixes and cleanup across administrative routines:
- A defect affecting the permission check when issuing user grant commands has been resolved.
- The
DropItemroutine was refactored and fixed to execute through native game methods directly.
These modifications ensure administrative command permissions behave properly during console delegation and resolve internal inconsistencies when items drop into the game world.
Requirements for a Modded Rust Server
Server administrators updating to the 2633.288.1 protocol must apply Oxide.Rust 2.0.7676 to maintain mod compatibility. While the source notes do not specify explicit manual configuration adjustments, server owners running mods that track fertilizer production or item generation should audit their plugins for OnComposterUpdate usage. Standard update procedures apply: shut down the host instance, patch the core server files, apply the latest Oxide binaries, and restart.
What Players Will Notice
Players joining an updated host will not observe radical gameplay overhauls directly from Oxide itself. However, fixes to the DropItem method prevent potential item-handling glitches, and administrative permission systems will function correctly if an owner manages permissions in-game.
JoinGG is a live directory of community game servers — current status, players online right now, and a copyable address for every listing.
Common questions
- What happens if plugins continue using the deprecated OnComposterUpdate hook?
- Plugins that continue relying on OnComposterUpdate risk generating unhandled deprecation notices or encountering broken event flows. Developers must update their plugins to use OnOvenCook instead to prevent these issues.
- What is the correct procedure for applying the Oxide.Rust 2.0.7676 update to a host?
- Applying the update requires administrators to shut down the host instance, patch the core server files, apply the latest Oxide binaries, and restart the server. No explicit manual configuration adjustments are specified.
- Will players experience direct gameplay changes after a server installs Oxide.Rust 2.0.7676?
- Players will not see radical gameplay overhauls directly from the Oxide framework. They will primarily benefit from internal fixes that prevent item-handling glitches when items drop and ensure administrative permissions function properly.
- Tags
- rust
- Share
Published · 2 min read
