"SetDestination" can only be called on an active agent
Just updated and now getting an error. "SetDestination" can only be called on an active agent that has been placed on a NavMesh. ???? Any thoughts??
 
 
 
It just keeps repeating over and over

Just fly out, shoot the damn scientist in the picture above and don't worry about it. 
anyone seen this getting spammed?


"SetDestination" can only be called on an active agent that has been placed on a NavMesh.

It probaly nothing to do with oxide.

Thank you very much.
so Im getting this spammed in my RCON but I havent changed anything in months.
Ive checked oxide logs and theres no issues there...

This is all it says in my server logs as well:

"SetDestination" can only be called on an active agent that has been placed on a NavMesh.
(Filename: Line: 197)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)

Any Ideas of whats causing this? Or where else I should be looking for logs?

Merged post

also going out there to kill 1 damn scientist every Xmin is unreasonable... any other way to fix this?

"SetDestination" can only be called on an active agent that has been placed on a NavMesh.

Is this something related to your mod? Fresh wipe on my server and this is showing up. 
Getting moderated like a champ, there? :P

idk. Hands up if you're having this issue and not using BotSpawn... ?
Hey, I don't mind my post being moved and whatnot if there's a solution in the thread. When I get home I'll check it out. Thank you! 
In response to ():
Getting moderated like a champ, there? :P

idk. Hands up if you're having this issue and n...
There is no bot spawn on the server  thats having issues... I am however using zombie hordes from CC but Ive been using that addon for months with no issues.  then all of a sudden wall of text based errors XD
Seems more likely to be coming from newly introduced AI on new monuments (oilrig?) but it's good to get confirmation.
Thank you. ^^.
In response to Philoludos ():
Hey, I don't mind my post being moved and whatnot if there's a solution in the thread. When I get ho...
I didn't move it. I got notified that there was a new thread under BotSpawn support but the link redirected to this, so I assume someone did.
I was getting that error at least twice a minute. Can confirm, killing that specific scientist resolved the problem. 
Can anyone confirm if this is a Umod issue or a Facepunch issue?
This is not related to Oxide itself, would either be a plugin or Rust.