Nullreferanceexeption

After about 2 - 4 hours of the server running i get a spammed error nullreferenceexeption, according to the server log its due to playercorpse.boyancysleep. I have done days of testing and narrowed it down to the water patrol mod. Ive have tried re-installing and wiping the old config file completely. This is for the latest version. Ive have rolled back to version 1.06 to eliminate the issue. Is there a fix planned for this?

On 10/7/2024 at 2:58 PM, Negligent Ranger said:

After about 2 - 4 hours of the server running i get a spammed error nullreferenceexeption, according to the server log its due to playercorpse.boyancysleep. I have done days of testing and narrowed it down to the water patrol mod. Ive have tried re-installing and wiping the old config file completely. This is for the latest version. Ive have rolled back to version 1.06 to eliminate the issue. Is there a fix planned for this?

Can you share the full error?

What version of NpcSpawn do you have?

My NPC Spawn version is 2.7.8

NullReferenceException: Object reference not set to an instance of an object
  at PlayerCorpse.BuoyancySleep (System.Boolean inWater) [0x00008] in <3aec307eee464538bf0b5313d5ab1ad7>:0 
  at Buoyancy.Sleep () [0x0001a] in <3aec307eee464538bf0b5313d5ab1ad7>:0 
  at InvokeHandlerBase`1[T].DoTick () [0x00138] in <97363e0bbe864c65a9819cff9eddaf42>:0 
  at InvokeHandlerBase`1[T].LateUpdate () [0x0000c] in <97363e0bbe864c65a9819cff9eddaf42>:0 

This is a single instance of the error from the server log, I was able to recreate the error on Water Patrol version 1.0.6 by simply unloading the mod without restarting the server, after water patrol NPCs had spawned. In water patrol version 1.0.8 this error occurs without any assistance. I believe its has to do with a water patrol NPC despawning. 

It may be possible that after the 1.0.8 update the plugin now conflicts with a different plugin that wasn't an issue before. Other NPC plugins that

I am using are many of KpucTaJI's events, like satdish, harbor, junkyard, ect. As well as Raidable Bases and BotRespawn. Im going to try running a test server tonight with some of those plugins disabled with the 1.0.8 water patrol. Are there any other logs i could be looking at? Thank you for the reply

1 hour ago, Negligent Ranger said:

It may be possible that after the 1.0.8 update the plugin now conflicts with a different plugin that wasn't an issue before. Other NPC plugins that

I am using are many of KpucTaJI's events, like satdish, harbor, junkyard, ect. As well as Raidable Bases and BotRespawn. Im going to try running a test server tonight with some of those plugins disabled with the 1.0.8 water patrol. Are there any other logs i could be looking at? Thank you for the reply

Check also your server convars, I wonder if you have a setting or as you said another plugin that was not an issue before.

Anything you can do such as you were already doing as pinpointing the time and any clues around that time or soon before it to lead to what is causing it.

Good news, I believe this issue is caused by a conflict with BotRespawn. Without that plugin installed I could not get the error to occur. More specifically the conflict maybe with BotRespawn and NPC Spawn and not water patrol itself. In addition to that discovery, Im not sure if it was the oxide update to 2.0.6307, but Ive been running a server now for 6 hours with Botrespawn and water patrol 1.0.8 with out any errors. My oxide version earlier this week was 2.0.6305. So either the issue resolved itself or there is a small compatibility issue and I've just been lucky. If the error returns or persists I may consider switching over to the Better NPC mod instead of botrespawn. However for now the problem is resolved. On a side note I really love KpucTaJI plugins and have never had any issues getting them to work. Thank you for the assistance.  We can mark this support ticket resolved/closed. Thank you. 

So the potential conflict only happened on an older oxide version? That could make a lot of sense.

Thank you for the feedback and for letting me know! If anything else comes up don't hesitate to reach out.