BotSpawn

Moved

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

5/5, 81 likes
  1. By wipe config and data, you mean delete both files and then add the customs bots back and make the changes in the config? That is an easy part, I always save my stuff in case I need to do that lol.
     
  2. Yes, that's right.

    Unfortunately when I add new options to the plug they don't get added into your config/data automatically, so a wipe or manual update is required.
    For a big update like this, wipe is easiest.
     
  3. Perfect, I will do it now! If I click on support the developer for your beer money, does that go to you?
     
  4. It does indeed! Thank you. :)

    edit: Your timing is perfect; My beer glass is empty.
     
  5. Thanks @Steenamaroo for all of your hard work on plugins. This is my favorite update yet. Seems to be working really well. Pay no mind to those who have no clue about what you do and how you scramble for us when we report errors. You the man!
     
  6. Thank you all for the support.
    I know I'm learning as I go and make mistakes along the way, but the feedback and support makes it fun and a lot easier!

    Hope you're all enjoying BotSpawn again. :)
     
  7. So I wiped the Oxide Default and Config, and the plugin, downloaded the plugin again and updated the basic (did not do the custom spawn points yet because I wanted to get basic first) and got the following:
    BotSpawn v1.4.3: Failed to load config file (is the config file corrupt?) (Unexpected character encountered while parsing value: T. Path 'Zones.Airfield.Activate', line 35, position 18.)

    Failed to initialize plugin 'BotSpawn v1.4.3' (JsonReaderException: Unexpected character encountered while parsing value: T. Path 'Zones.Airfield.Activate', line 35, position 19.)
    at Newtonsoft.Json.JsonTextReader.ReadAsBoolean () [0x00000] in :0
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonContract contract, Boolean hasConverter) [0x00000] in :0
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00000] in :0

    I noticed the kits do not say default anymore but instead say "Kit": [], Do I need to remove the [] and replace with default or kit name? Also I counted down to line 35 (inside the error) and that brings me to the Airfield "Activate": True, line...the first one I turned on. Any suggestions?
    [DOUBLEPOST=1515212377][/DOUBLEPOST]
    Code:
    New options},
        "Airfield": {
          "Activate": True,
          "Aggression_Range": 40,
          "Bot_Accuracy": 4,
          "Bot_Damage": 0.4,
          "BotHealth": 100,
          "BotName": "BABs Minion",
          "Bots": 30,
          "Disable_Radio": false,
          "Keep_Default_Loadout": false,
          "Kit": [],
          "Murderer": false,
          "Radius": 100,
          "Respawn_Timer": 150,
          "Roam_Range": 100,
          "Weapon_Drop": false
        },Old Option I am trying to enter:
    },
        "Airfield": {
          "Activate": true,
          "Aggression_Range": 20,
          "Bot_Accuracy": 4,
          "Bot_Damage": 0.4,
          "Bot_Firing_Range": 20,
          "BotHealth": 100,
          "BotName": "BABs Minion",
          "Bots": 25,
          "Disable_Radio": false,
          "Kit": "default",
          "Murderer": false,
          "Radius": 100,
          "Respawn_Timer": 150
        },
    
     
  8. "True" needs to be "true"

    Post edited.
     
    Last edited by a moderator: Jan 6, 2018
  9. I wish there was a "I'm a DumbA.."button because I would click it for myself...Yep that stupid T was Capital...Banging head on computer!! I also had to keep "Kit": [], like it was, if I add the word "default" to the middle it causes an error saying there is no default kit.
    Last things then I will hopefully leave you alone! I noticed the Retaliate and timer were missing, will they just auto retaliate without that extra line? And no reset timer, is this no longer neaded since there is now a roam range? (I love that by the way because mine kept wandering WAY away) as for the new, what does the loadout mean? Also, I saw in one of your updates you were going to be changing the bothealth to be a scale vs a number, like instead of a boss guy having 350 health you could set it to be 10 times the normal health, did this get pushed back? I wanted to make sure I wasn't trying to make the NPCs 100 times their normal health this go round :)
    Missing
    "NPC_Retaliate": true,
    "Reset_Timer": 1800,
    New
    "Keep_Default_Loadout": false,
     
  10. It's all good. I'd probably hit that button too. :p

    Yes, the word default is no longer used with kits.
    Formats for none, single, or multi are shown here.
    If you set multiple, one is chosen at random.

    Reset true/false and timer are no longer needed, as you say, because roam range is limited.
    Those only existed because the bots would eventually end up miles way. :(

    Bot health does now work on a multiplier but the maths is behind the scenes.
    From your perspective, just set the number you want the bots health to be. 100 is default.
    Technically their health never exceeds 100 - I just scale the damage by a multiplier, based on the desired health you enter.
    "200 health" actually equals half damage.

    I removed retaliate tonight because it was a disable option (I.E. They retaliated by default) and I noticed that the bots no longer retaliate to friendly fire.
    FP must have changed that recently.
    I'm not sure that anyone would actually want the bots to return to friendly fire but if it's requested I could look into forcing it.

    Keep default load out is sort of complicated.

    Say you give a bot a kit with one weapon, he'll be naked and have a weapon.
    If you set "Keep_Default_Loadout": "true" and give him the same kit, he'll be dressed like a scientist/murderer and will have the associated weapons, but he will also have the weapon you gave him.

    It's basically whether your kit should be added on top of a default bot's gear, or given instead of.

    Hope that answers everything.
     
  11. I saw someone else had this error as well, but nobody really mentioned it again, so I'll try.

    "NullReferenceException: Object reference not set to an instance of an object"

    Im also getting this error:
    SubCategoryIntoContainer: This should never happen!

    Well I guess it's not an error, but a warning or whatever
     
    Last edited by a moderator: Jan 6, 2018
  12. Thanks @srtbull
    Do you know what happened just before this error?

    Edit: That's not coming from BotSpawn, I don't think ^.
     
    Last edited by a moderator: Jan 6, 2018
  13. They both kinda happen at the same time, its when someone shoots a bot. But not every time. Seems random.
    You might kill 5 or 6 then the 7th, this might happen.

    This is how it looks in the console
    [Death Notes] rivka was shot in the Lower Spine by Bull with a Assault Rifle from 14.24m.
    SubCategoryIntoContainer: This should never happen!
    SubCategoryIntoContainer: This should never happen!
    rivka[2670010/76561190007365959] was killed by Bull[2663155/76561198040218052]

    This is how the first error looks:

    [Death Notes] carolee was shot in the Groin by Bull with a Assault Rifle from 19.72m.
    162.157.157.31:63084/76561198040218052/Bull kicked: RPC Error in OnProjectileAttack
    NullReferenceException: Object reference not set to an instance of an object
     
  14. I googled the SubCategory message and got a few results relating to loot containers.
    Are you using a kit and, if so, is the main container packed full?
     
  15. I don't know if it helps but prelaunch I received the same error and I traced it back to scrap, if I added scrap in the kit I would continue to get this error, if I took scrap out it worked like a charm. If scrap is in the kit, then I would remove. Are you using multiple kits? If you are that might be why you are getting the error after a few kills and not every time.
     
  16. Does adding Custom Spawn locations add those locations to the CFG?
     
  17. read the overview :

    Custom location settings are held in/data/BotSpawn.json
     
  18. ah thanks must have missed that
     
  19. (10:01:51) | Air security[687189/76561190002018737] was killed by Explosion
    (10:01:53) | Air security[687176/76561190007374484] was killed by Explosion
    (10:01:57) | Air security[687202/76561190002006090] was killed by Explosion

    after 1 min droped air all bots died from server explosion... why?
     
  20. Any way to let players damage the bots even when server.pve is set to true?