Steenamaroo

Yes, you can go to the desired location and use the /botspawn add <profilename> chat command to add a new profile. If you then set Parent_Monument for that new profile, in the customprofiles data file, to the name of a default profile "Launch Site 0", for example, and reload BotSpawn, that new custom profile will automatically relocate after map changes, so that the profile always appears in the correct place relative to the specified monument. The Parent_Monument name must be exactly as it appears in the defaultprofiles json. The same is true if you choose to use custom spawn points with your new custum profile(s), but Parent_Monument must be set, and the plugin reloaded, before adding custom spawn points. "also, does the plugin affect how turrets interact with animals?" No, I don't believe so.

I'll take a look at that. Thank you.

Then I guess they're just too far from navmesh? It should warn you if that is the case, when adding custom spawn points. "No navmesh was found at this location. Consider removing this point or using Stationary : true."

"Any chance you have UseCustomSpawns true and some spawn points that are in the air or underground or something?" Rule that out first. Personally I'd just use custom spawn points for the lighthouses and harbors. If you already are then do /botspawn edit "ProfileName" to see where the current spawn points are. As far as I know any respawn/timer/population control issues are resolved in V2.1.6 but I don't think there was ever any issue regarding finding spawn points.

Hi, Are you both coming from a few versions ago? V2.1.1 or something? There's a note in the main description explaining, but the way custom spawn points are stored has recently changed, in order to facilitate auto-migrating them if Parent_Monument is in use. That means people can use custom spawn points + Parent_Monument and only ever have to set up their spawns once, but it does mean that existing custom spawn points would need to be re-done now.

Hi, Yes, once you've set up some profile they will automatically spawn thereafter, as long as they're enabled. Yes, that's normal - The UI has to constantly reload to be up to date so you may see the occasional flicker or whatever.

Thanks man! Same to yourself. No, there's nothing different about, or specific to, any single profile. Any chance you have UseCustomSpawns true and some spawn points that are in the air or underground or something? With radius as high as 200 it should definitely be finding something, somewhere, unless that's the case ^.

Hi, I don't know about the DeathNotes end but BotSpawn assign a random name to each npc it spawns, unless you manually specify names. If you were to give your profiles manual names like BotNames: ["Airfield Guard"], for example, that would cut down the numbers a lot. Check BotSpawn overview for proper formatting, as this field accepts lists of names.

Hi, Can you ensure you're on the most up to date public version, please? That's V2.1.5.

Ah, yeah. Don't remove MigrationData. I think the title of it literally says "DoNotEdit", no? Setting Parent_Monument to "" should have no adverse effects, though, other than existing custom spawn points being automatically removed.

You definitely updated the BotSpawn.cs file? I've updated public now so you may as well get it from there, but I did find an instant-respawn issue with default profiles, and fixed/tested it.

ugh, really? Ok, I'll have a look this evening. I made some changes to how custom spawn points are handled and it's had a few knock-on effects. Thanks for letting me know. Depending on the terrain around the lighthouse it may be very difficult to get random spawn points. In some cases custom spawn points may be necessary but they auto-migrate at wipe now (if you set Parent_Monument correctly before adding points) so at least it only needs done once.

Should be all good now @MastrJedii

Waiting for feedback on something else before releasing a public update (...again<sign>). Here's the respawn fix until then, for anyone who wants. BotSpawn.cs

@Sasquire- I'm not finding this one. Do you know the steps to reproduce it? Thanks.

On it. Thank you!

Hi, Thanks for the info. No, Parent_Monument isn't (shouldn't be...) required - This is a bug that I'll fix. Got a few small things to fix so I'll most likely update some time today.

Nice. Thank you.

All good now? @MON@H

Fixedamaroo.

Ok, thanks. I'll take a look. I may have updates pending - If so there'll be a new version released later today. Thanks for the info.

I asked people to test this for me and report back - from what I gather the issue is fixed in V2.1.2. Did you update to V2.12, set Parent_Monument for some profile, then `/botspawn move <profilename>` to where it's meant to be, and then see a failure to relocate after a wipe? If so, please share your custom + default data profile files and I'll take a look.