1. Community
  2. Game Support
  3. Rust
NullReferenceException at OnAiQuestionNot An Issue
Posted 7 years ago
Last updated 6 years ago
#1
I posted something related to (NullReferenceException: Object reference not set to an instance of an object) spam some weeks ago, I found the problem causing it, this plugin does it, I got a lot of NullReferenceException messages and I unloaded the plugin, after that, messages stopped. Is there a way to fix this?


screenshot-699.png

Kind regards,
Adriok
Posted 7 years ago
Last updated 6 years ago
#2
You'd need to check your output_log.txt (or where -logfile is set) for the full error, as just showing the generic first line doesn't help.
Posted 7 years ago
Last updated 6 years ago
#3
In response to Wulf ():
You'd need to check your output_log.txt (or where -logfile is set) for the full error, as just showi... 
NullReferenceException: Object reference not set to an instance of an object
  at NPCPlayerApex.OnAiQuestion (NPCPlayerApex source, Rust.Ai.AiQuestion_ShareEnemyTarget question) [0x000a7] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Scientist.AskQuestion (Rust.Ai.AiQuestion_ShareEnemyTarget question, System.Collections.Generic.List`1[Rust.Ai.AiAnswer_ShareEnemyTarget]& answers) [0x0002c] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Rust.Ai.SharePlayerTargetComm.Execute (Rust.Ai.PlayerTargetContext c) [0x00018] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Apex.AI.ActionBase`1[TContext].Apex.AI.IAction.Execute (Apex.AI.IAIContext context) [0x00000] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at Apex.AI.CompositeAction.Execute (Apex.AI.IAIContext context) [0x0001c] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at Apex.AI.Components.UtilityAIClient.Execute () [0x00055] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at NPCPlayerApex.TickSensorySystem () [0x000c7] in <86c59486ea244afa9d93057edfd6428c>:0 
  at NPCPlayerApex.Apex.LoadBalancing.ILoadBalanced.ExecuteUpdate (System.Single deltaTime, System.Single nextInterval) [0x00038] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Apex.LoadBalancing.LoadBalancedQueue.Update () [0x00095] in <787a2dc0b1ce4c1cbf241b55159b5f2a>:0 
  at Apex.LoadBalancing.LoadBalancerComponent.Update () [0x00004] in <787a2dc0b1ce4c1cbf241b55159b5f2a>:0
Posted 7 years ago
Last updated 6 years ago
#4
I had the same, in the log file wulf suggested checking out, I could see the problem was while loading the config. I deleted my config for deathnotes, ran "oxide.reload DeathNotes" at server console and all was good. 
Posted 7 years ago
Last updated 6 years ago
#5

I'm getting this error long time ago but it's becoming annoying, what could cause this error?

NullReferenceException: Object reference not set to an instance of an object
  at NPCPlayerApex.OnAiQuestion (NPCPlayerApex source, Rust.Ai.AiQuestion_ShareEnemyTarget question) [0x000a7] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Scientist.AskQuestion (Rust.Ai.AiQuestion_ShareEnemyTarget question, System.Collections.Generic.List`1[Rust.Ai.AiAnswer_ShareEnemyTarget]& answers) [0x0002c] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Rust.Ai.SharePlayerTargetComm.Execute (Rust.Ai.PlayerTargetContext c) [0x00018] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Apex.AI.ActionBase`1[TContext].Apex.AI.IAction.Execute (Apex.AI.IAIContext context) [0x00000] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at Apex.AI.CompositeAction.Execute (Apex.AI.IAIContext context) [0x0001c] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at Apex.AI.Components.UtilityAIClient.Execute () [0x00055] in <f099585cca9b44ec90de92bcaa4581a5>:0 
  at NPCPlayerApex.TickSensorySystem () [0x000c7] in <86c59486ea244afa9d93057edfd6428c>:0 
  at NPCPlayerApex.Apex.LoadBalancing.ILoadBalanced.ExecuteUpdate (System.Single deltaTime, System.Single nextInterval) [0x00038] in <86c59486ea244afa9d93057edfd6428c>:0 
  at Apex.LoadBalancing.LoadBalancedQueue.Update () [0x00095] in <787a2dc0b1ce4c1cbf241b55159b5f2a>:0 
  at Apex.LoadBalancing.LoadBalancerComponent.Update () [0x00004] in <787a2dc0b1ce4c1cbf241b55159b5f2a>:0



Kind regards,
Adriok

Posted 7 years ago
Last updated 6 years ago
#6
I had the same issue, with same callstack.
Locked automatically