Hello! Since the last update I am seeing how several players constantly receive server kicks. I have informed Alistair and he told me that this problem is caused by oxide and not by the game itself.

I know that other modified servers also experience the same problem.

(09:46:21) | infoplayer. disconnecting: NullReferenceException: Object reference not set to an instance of an object. MapView.SetupMarkers () (at <00000000000000000000000000000000>:0) MapView.MarkersDirty () (at <00000000000000000000000000000000>:0) MapInterface.ForceOpen (System.Boolean open) (at <00000000000000000000000000000000>:0) MapInterface.SetOpen (System.Boolean open) (at <00000000000000000000000000000000>:0) BasePlayer.ClientInput (InputState state) (at <00000000000000000000000000000000>:0) BasePlayer.ClientUpdateLocalPlayer () (at <00000000000000000000000000000000>:0) BasePlayer.ClientCycle (System.Single deltaTime) (at <00000000000000000000000000000000>:0) Client.Update () (at <00000000000000000000000000000000>:0)

On my server people get playerflood packet tick disconnects, yet I do not see any errors in the console.

Oxide has not been updated for today's Rust update yet, so if you updated prematurely, that is most likely why. This error isn't realted to Oxide specifically, more so mixed Rust versions being installed on top of each other.

Hi Wulf! This error has been occurring since yesterday's update Thursday. Today Rust was updated and the problem was not solved. Alistar told me that this error comes from oxidemod, but I would not know if oxidemod as such or a mod, since it does not refer to any mod.

ninco90

Hi Wulf! This error has been occurring since yesterday's update Thursday. Today Rust was updated and the problem was not solved. Alistar told me that this error comes from oxidemod, but I would not know if oxidemod as such or a mod, since it does not refer to any mod.

There isn't anything that we touch related to that above error, so I don't really see how it could be.

"Corrected hook index for OnTeamUpdated hook." I think this error that I mentioned in the post should now be fixed with the latest update of oxide!

I have this happening a lot, multiple players effected even after todays update. I'd definitely say this is an issue, I can't seem to figure out what plugin is causing it though.