BotSpawn

Thanks so much, works great! Sorry for non-botspawn chat here Steamamaroo lol

 

Oops : wrong place

 

Steenamaroo updated BotSpawn with a new update entry:

1.7.2

[DOUBLEPOST=1530889808][/DOUBLEPOST]@FireBurst
Their displayName most likely is, or contains, their userID, so you could compare to get what you want.

 

Exactly. I was just too lazy and in a hurry that I just replaced it with what I wanted it to show lol.

 

Peacekeeper seems broken for scientist, attacking regardless but not all at once.
Murderer roaming seems broken
Previous version to the one from 30 mins ago Murderers were running up at you but not attacking when no weapon is out, not attacking when a weapon is out. Now they're all just standing still.

Reverting to 1.6.9 for now

 

Could scientists have been going in and out of agro range?
I too noticed zombies are not as aggressive as they use to be.
My Zombies are chasing Scientists forever, because they seem to be having a hard time running and swinging their machetes

 

Peacekeeper still broken for scientists on 1.6.9

Murderers have returned to normal behaviour on 1.6.9

 

All I changed 40 minutes ago was a null check around something that only happens when a bot dies.
There was no change to behaviour or targeting or anything like that.

There is something different in 1.6.9 I can look at, but I'll need to check it properly.
[DOUBLEPOST=1530893228][/DOUBLEPOST]Ugh...
I'm still on oxide 3987, but everything is working perfectly for me at first glance.
Murderers attack aggressively, peacekeeper+vanish are honoured..No obvious issue.

Will update soon.

 

Cool, they seem to have stopped spazzing now on the older version, unfortunately got a problem with Warehouse and Radtown spawning on both config and custom profiles. Will wait for a new version though before worrying about it

 

Error while compiling: BotSpawn.cs(1797,29): error CS1061: Type `NPCPlayerApex' does not contain a definition for `utilityAiComponent' and no extension method `utilityAiComponent' of type `NPCPlayerApex' could be found. Are you missing an assembly reference?

 

Rust+oxide version?

 

Protocol: 2099.165.1

Build Date: 07/05/2018 15:14:12

Unity Version: 2018.1.4f1

Changeset: 27596

Branch: main

Oxide.Rust Version: 2.0.3993

 

I don't get it.
Running the same version, compiling fine. Modified the .cs at all?

If not, I guess reinstall oxide?

 

haven't changed anything also doing it on other mods as well

 

Are you new to BotSpawn? Did it ever compile for you?

utilityAiComponent has been exposed for a good while.

 

getting some odd start up issues, I do run custom bots:

Code:

(07:52:48) | Failed to run a 2.00 timer in 'BotSpawn v1.7.2' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotSpawn.SelectWeapon (NPCPlayerApex npcPlayer) [0x00140] in <c2b930c491194e64aa6487e659da184a>:0
  at Oxide.Plugins.BotSpawn+<sortWeapons>c__AnonStorey3.<>m__0 () [0x00000] in <c2b930c491194e64aa6487e659da184a>:0
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <0f58cfbbba844942876db6036f28ac86>:0
(07:52:48) | Failed to run a 2.00 timer in 'BotSpawn v1.7.2' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotSpawn.SelectWeapon (NPCPlayerApex npcPlayer) [0x00140] in <c2b930c491194e64aa6487e659da184a>:0
  at Oxide.Plugins.BotSpawn+<sortWeapons>c__AnonStorey3.<>m__0 () [0x00000] in <c2b930c491194e64aa6487e659da184a>:0
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <0f58cfbbba844942876db6036f28ac86>:0

Protocol: 2099.165.1
Build Date: 07/05/2018 15:14:12
Unity Version: 2018.1.4f1
Changeset: 27596
Branch: main
Oxide.Rust Version: 2.0.3993

 

PMing.

 

it's always compiled on oxide.reload BotSpawn for me. I'll try reloading oxide again to see fi that helps, but I'm getting this on 4 servers
[DOUBLEPOST=1530922838][/DOUBLEPOST]well apparently oxide was the culprit, just odd it was on 4 servers, thanks for the help

 

No probs. Thanks for coming back to let us know.

 

Had a similar problem , had to update oxide 3 times before it ran ok