BotSpawn

Moved

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

5/5, 81 likes
  1. Same here
     
  2. Do any of you guys manually move custom locations, each time the map seed changes, in order to keep them near a certain monument?

    If so, and you want to test a completely automated version, fire me a PM.
    It might already be public by Thursday but if not it'd be great to have a few people to test it.
     
  3. No I just leave them in default locations and use the roaming range. The fix you released stopped the numbers scrolling up the screen.
     
  4. Nothing to worry about its the percentage of what is being loaded/installed , Sometimes get it on different plugins or when loading some files,
    Its like when you are updating Steam through your server page, you will see percentage being loaded.
     
  5. "Suicide_Timer": 60, not working - i have respawn timer on 10
     
  6. These options are alternatives to each-other.

    Only non-respawning bots will suicide. Airdrop bots, bots called 'toplayer' and bots deployed as a one-off via external hooks.
    The reason is that without a suicide option there's no certainty that they'll be killed and then, over time, you could end up with hundreds of them.
    [DOUBLEPOST=1528061463][/DOUBLEPOST]
    Yeah, I had some trouble with aggro and set it aside.
    It's something I want to add back in, though.
    [DOUBLEPOST=1528061500][/DOUBLEPOST]
    <cough> Let's run with that.
    Either way it's not some random debug code that I left in 'cos I was really tired. ;)
     
  7. I use 1.6.1 fine, if but if I update to 1.6.5 the bots (tested with murderers only so far) start acting really weird, rocking back and forth. Downgrading back to 1.6.1 and everything is fine again.
    Do I need to delete some config/data file for new one to be generated or something? If you want, I can upload a video.

    Code:
    {
      "Options": {
        "NoBotsVBots": false,
        "Ignore_Animals": false,
        "APC_Safe": false,
        "Turret_Safe": false,
        "Animal_Safe": false,
        "Supply_Enabled": false,
        "Remove_BackPacks": true,
        "Ignore_HumanNPC": false,
        "Pve_Safe": false,
        "Corpse_Duration": 60
      },

    Code:
        "Trainyard": {
          "Activate": true,
          "Murderer": true,
          "Bots": 10,
          "BotHealth": 100,
          "Radius": 100,
          "Kit": [],
          "BotName": "randomname",
          "Bot_Accuracy": 4,
          "Bot_Damage": 2.0,
          "Respawn_Timer": 60,
          "Disable_Radio": true,
          "Roam_Range": 40,
          "Peace_Keeper": false,
          "Weapon_Drop": false,
          "Keep_Default_Loadout": false,
          "Wipe_Belt": true,
          "Wipe_Clothing": true,
          "Allow_Rust_Loot": false,
          "Suicide_Timer": 300
        },
     
  8. Rocking back and forth? That's a new one on me.
    I was working at this auto-relocation stuff last night and had to spawn murd+sci over and over without issue.

    Config/Data should automatically update between the versions you mentioned but maybe try plain config/data just to rule some things out?

    In short, I don't know what's changed to cause that but obviously something has.
     
  9. Yeah, rocking back and forth for me too. Back to 158 again xD or was I on 162 last..
     
  10. Are either of you getting any relevant console messages when they spawn?
     


  11. config if someone want to reproduce

    No console message on spawn
     

    Attached Files:

  12. I'm not seeing it. Is it isolated to that zone/area?
    It could be that they can't find a path to navigate to you.
     
  13. All I can find from "botspawn" that seems relevant is these:
    13:17 [Warning] Calling 'OnNpcPlayerTarget' on 'BotSpawn v1.6.5' took 142ms [GARBAGE COLLECT]
    17:18 [Warning] Calling 'OnEntitySpawned' on 'BotSpawn v1.6.5' took 195ms [GARBAGE COLLECT]

    Man, if you could somehow have it work exactly like 1.5.8 did that would be great. I'm scared cus my server is pretty much based on your plugin now, and it's fine , but I feel like sooner or later the rust devs will break my beloved 1.5.8 xD

    Could be path issue, but when it happen to me and my friend ,the bots were just next to us in a field. I think there was a thin tree, but that's it, shouldn't be stopping them
     
  14. The reason I ask is that mine are acting just fine, but if I fly into the air a few meters they will just run back and forth a few meters in front of me.
    That's pretty much definitely a pathfinding thing; It doesn't know how to get to me.
    Not sure if you're seeing the same thing, though. Doesn't sound like it if it happened in a field?! :(
    [DOUBLEPOST=1528066220][/DOUBLEPOST]
    If that config is from version 1.6.5 then something is wrong - It's out of date.

    It should have auto-updated, which I'm going to check now, although still; I don't see how/why it would cause this problem.
    Update: I just went from a clean 1.5.6 to 1.6.5 and the config updated perfectly.
    Not sure why yours is outdated!?
     
    Last edited by a moderator: Jun 3, 2018
  15. Not likely to be path issue, did the exact same test twice on both version in addition to other areas.
    Did some more tests just now in other monuments, same thing.

    no issues at all with 1.6.1
     
  16. Ok. I just tested at the exact location shown in your vid without issues.

    Can you try with the most up to date version, and make sure that your profiles (config+data) have
    BotNames [], (<-- list, like kits)
    Peace_Keeper_Cool_Down
    Chute
    Long_Attack_Distance

    If those are missing it's not up to date.
    Not sure why that would happen but, if that's the case, please back up your files, delete them from server, then reload the plugin.
     
  17. Sorry my bad, I was pasting pre-update config. It does update automatically.

    Just deleted config and let the plugin generate new default config. Still behave strange. For example, they stop following you after a certain distance and start the good old rockin' back and forth while 1.6.1 follows you forever (which I do enjoy).
     
  18. Ok, thanks for the info. I'll look into it some more.

    Would you mind attaching config from 1.6.5, where the issue occurs?
     
  19. There you go
     

    Attached Files: