uMod - NullReferenceException at HackableLockedCrate.DisableRB - Rust

Posted 7 years ago

Last updated 6 years ago

I've had no issues till todays update and now this is constantly displayed

ReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object
at HackableLockedCrate.DisableRB () [0x00009] in <6497642b7b9f41fb91a4208bcdeb8c16>:0
at HackableLockedCrate.LandCheck () [0x00051] in <6497642b7b9f41fb91a4208bcdeb8c16>:0 Map] 161fps 60gc 4m1s
at InvokeHandler.DoTick () [0x000d6] in <f007cbba545d45a5a71a5c94084d7ba0>:0 2kb/s in, 20kb/s out
at InvokeHandler.LateUpdate () [0x0000c] in <f007cbba545d45a5a71a5c94084d7ba0>:0

Fired up a fresh install on my diedicated box (vanilla) no issues, installed oxide and boom

same error again (no plugins)

any ideas?

Posted 7 years ago

Last updated 6 years ago

#2

I think facepunch messed up something with hackable crate.

Posted 7 years ago

Last updated 6 years ago

#3

I just had this same error after I installed the oxide update releesed 15hrs ago (v2.0.4178). I just reverted back to the one released earlier this week (v2.0.4174) and the error has gone now try that

Posted 7 years ago

Last updated 6 years ago

#4

In response to Wxll ():
I just had this same error after I installed the oxide update releesed 15hrs ago (v2.0.4178). I just...

When you install older version of OxideMod - u basically downgrade game files, so it won't be always possible to connect to your server if rust received a protocol change

Posted 7 years ago

Last updated 6 years ago

#5

That is not an error from Oxide. The only change in our update was patching for the new Rust version and changes. Installing an old Oxide build downgrades your Rust version, hence the difference.

Posted 7 years ago

Last updated 6 years ago

#6

Finally had a few hours with no errors and now it's flooding with error messages again.

I appreciate the reply wulf but how can a fresh install with oxide yeil same error and no error with vanilla.

Posted 7 years ago

Last updated 6 years ago

#7

In response to browney ():
Finally had a few hours with no errors and now it's flooding with error messages again.

<...

That would imply that your Rust install was not fully updated then as "vanilla". There are literally no changes from Oxide, only Rust in the last update. The area in the error is also only from Rust, we do not touch that area.

Posted 7 years ago

Last updated 6 years ago

#8

Went back to a previous version of oxide for now.

Posted 7 years ago

Last updated 6 years ago

#9

Got kicked when trying to open Locked crate on oil rig. Got also error in console

Setting parent to entity that hasn't spawned yet! (net is null)
NullReferenceException: Object reference not set to an instance of an object

Build Date: 03/16/2019 22:29:43

Unity Version: 2018.3.3f1

Changeset: 33211

Branch: release

Oxide.Rust Version: 2.0.4178

Posted 7 years ago

Last updated 6 years ago

#10

Game Server Flood Console

(Filename: <6497642b7b9f41fb91a4208bcdeb8c16> Line: 0)

NullReferenceException: Object reference not set to an instance of an object
at HackableLockedCrate.DisableRB () [0x00009] in <6497642b7b9f41fb91a4208bcdeb8c16>:0
at HackableLockedCrate.LandCheck () [0x00051] in <6497642b7b9f41fb91a4208bcdeb8c16>:0
at InvokeHandler.DoTick () [0x000d6] in <b3d95774e91f4d8480e73eb7576da5f4>:0
at InvokeHandler.LateUpdate () [0x0000c] in <b3d95774e91f4d8480e73eb7576da5f4>:0

Help me the solution of this error who understands.

Merged post

Game Server Hosting Linux for details...

Posted 7 years ago

Last updated 6 years ago

#11

FWIW, I am seeing the same errors spamming my logs on a new server all day every day. This is on a privately built VM, so not tied to a gameserver host per se. It is however, also on Linux.

Merged post

I just ran a validate (using LGSM) and there were some updates. Then I updated Oxide (reinstall) to be sure. Will let you know.

Posted 7 years ago

Last updated 6 years ago

#12

how did it go?

Posted 7 years ago

Last updated 6 years ago

#13

So far clean. It's not particularly busy yet but usually would have errored by now.

Locked automatically

6 years ago

NullReferenceException at HackableLockedCrate.DisableRBNot An Issue