BotSpawn

Moved

Total Downloads: 11,681 - First Release: Jul 31, 2017 - Last Update: Jul 27, 2018

5/5, 81 likes
  1. The biome spawns work, but not the monuments I've tested so far. But it's not really a big deal as you can make customs spawns, the locations are static anyway.
     
  2. How to cancel Outpost, I did not set up where to refresh.
     
  3. Just put false for autospawn and you wont get any there, I dont as it is impossible to have bots there and survive their attack, if
    you kill the bots the outpost kills you.
     
  4. @Steenamaroo I'm using custom bots, getting flooded with the error posted below. Know anything about it?
    I lightly investigated however I don't know much about the Rust AI Components.
    FP last commit was also "Added some extra safety checks around NPC sensor loading.", so maybe its an issue from their end?


    Code:
    NullReferenceException: Object reference not set to an instance of an object
      at NPCPlayerApex.OnAiQuestion (NPCPlayerApex source, Rust.Ai.AiQuestion_ShareEnemyTarget question) [0x000a7] in <25ffce0737144c53a960ec645231697e>:0
      at Scientist.AskQuestion (Rust.Ai.AiQuestion_ShareEnemyTarget question, System.Collections.Generic.List`1[Rust.Ai.AiAnswer_ShareEnemyTarget]& answers) [0x0002c] in <25ffce0737144c53a960ec645231697e>:0
      at Rust.Ai.SharePlayerTargetComm.Execute (Rust.Ai.PlayerTargetContext c) [0x00018] in <25ffce0737144c53a960ec645231697e>:0
      at Apex.AI.ActionBase`1[TContext].Apex.AI.IAction.Execute (Apex.AI.IAIContext context) [0x00001] in <7bc5c1faa2af4095bd4b5e00ae6066c5>:0
      at Apex.AI.CompositeAction.Execute (Apex.AI.IAIContext context) [0x0001e] in <7bc5c1faa2af4095bd4b5e00ae6066c5>:0
      at Apex.AI.Components.UtilityAIClient.Execute () [0x00071] in <7bc5c1faa2af4095bd4b5e00ae6066c5>:0
      at NPCPlayerApex.TickSensorySystem () [0x000be] in <25ffce0737144c53a960ec645231697e>:0
      at NPCPlayerApex.Apex.LoadBalancing.ILoadBalanced.ExecuteUpdate (System.Single deltaTime, System.Single nextInterval) [0x00038] in <25ffce0737144c53a960ec645231697e>:0
      at Apex.LoadBalancing.LoadBalancedQueue.Update () [0x000ab] in <bb0a7f1370d1429d8f5843f17f216f71>:0
      at Apex.LoadBalancing.LoadBalancerComponent.Update () [0x00006] in <bb0a7f1370d1429d8f5843f17f216f71>:0 
     
  5. +1 :) when i unload BotSpawn plugin no errors in console ;)
     
  6. Everything working fine except now peacekeeper is completely the other way, they wont attack at all

    EDIT: this is for murderer AI
     
    Last edited by a moderator: Aug 3, 2018
  7. Now AI is unable to attack the player close to the range
    [DOUBLEPOST=1533290873][/DOUBLEPOST]Only waving weapons in front of the players
     
  8. after 8/2 update found that when people were attacking the bots.. this would happen.. and it wouldn't stop spamming unless i reloaded the plugin. i unloaded the plugin for now because the server would go from 1000fps down to 90fps. because of these errors. @Steenamaroo
    upload_2018-8-3_22-49-28.png
     
  9. I've seen this error, and similar errors, coming in from other people who aren't using BotSpawn, but are using other plugins which spawn NPCPlayers.
    Haven't had time to look into it yet, but I will. :)
     
  10. i am using ServerRewards but NPC is turned off completely in the cfg. so to answer your question no i am not.. only using botspawn. @Steenamaroo
     
  11. What I'm saying is that other people are getting this error from other NPC spawning plugins,
    so it's not BotSpawn exclusive.

    Still keen to know what it is, all the same. ;)
     
  12. i understand what you are saying. @Steenamaroo but i am letting you know that the only 2 plugins i have that deal with any type of NPC is yours and ServerRewards and as far as i know i have NPC set to FALSE and disabled in ServerReward and when i typed o.reload BotSpawn the error stopped and then i typed o.unload BotSpawn and i havent seen the error since then. all other plugins i am using are working just fine.
     
  13. Not ignoring the others. We'll see if we can get this main issue out of the way,
    then make sure targeting/peacekeeper etc are doing what they should.
    [DOUBLEPOST=1533303040][/DOUBLEPOST]Fairly sure ServerRewards uses HumanNPCCore and not the Rust AI, just fyi.
     
  14. i have no clue since i have it disabled.
     
  15. I can confirm I got the same errors when installing a fresh copy of the most up to date BotSpawn. It only happens though when I actually start enabling murderers. I have some more testing to do today to see if other plugins are contributing like HumanNPC and ServerRewards as we run both on top of BotSpawn but only get said error when BotSpawn is loaded and tries to spawn hostile NPC's. I have a bunch of testing to do with broken or bugged stuff today, so I will test a bit more as soon as I am able :D
     
  16. As before, I believe you'll see this error with any plugin which spawns NPCPlayer types.

    That includes, but is not limited to BotSpawn,
    and does not include HumanNPC + ServerRewards.
     
  17. Im not getting those errors... *knocks on wood.. Ill do more investigation on targeting etc. none of mine are peacekeepers however.
     
  18. all of mine are in peacekeeper
     
  19. Targeting hook fun again, it seems...
    Not even going to tag wulf + ruin his day. :p
     
  20. I use my own custom bot spawner and i have the same errors. Tried disabling the spawner and spawn murderers/scientists through console and it produces the same error.