Sasquire

Yes, much better

Steen, I think that was exactly it. I had it set as Running_Speed_Boost. Not sure why it kept it at 5 for the default but not the custom, but I guess that doesn't matter now Appreciate that you spotted that!

By config, I mean the custom profile file. I've double checked and you're correct about the default profiles. They accept Running_Speed_Boost as 5. But the custom profiles do not. If you put 5 in there, it'll change to 10 on bot reload.

We have it already set to 5, but when the configs are uploaded, BotReSpawn auto sets it to 10. We can't do lower than 10.

Thanks for the recent update. This has indeed corrected the auto migration location as well as the formatting. However, another problem has presented itself as they're (custom profiles) still spawning centre map. From what I can tell, this is due to the offset in migrationdata. So if you add a parent_monument and let the migrationdata populate itself, while it gets the ParentMonument details correct, it auto adds an offset that sends all of the bots to the centre of the map. No idea why. I believe the offset should be just x 0, y 0, z 0 which would get all the bots working fine. But if I have three custom profiles linking to launch as an example, it will offset them all exactly the same, and all will spawn centre map. Profiles added via the UI appear to add (offset) correctly. EDIT: I've have a distant memory that the old BotSpawn may have had this problem as well. I got around it by making a script that downloaded the custom profiles (after migration was auto filled), zeroing the offsets and reuploading.

You've been very regular with the updates, so I'm happy to wait for the next one

Yeah, it was doing it fine in BotSpawn, but since the move to BotReSpawn, it's no longer auto populating migration data. If we create a manual profile for the custom json with... { "Profiles": { "low_super2_pistol.nailgun": { "type": 1, "Spawn": { "AutoSpawn": true, "Radius": 90, "BotNames": [ "[YT11] Name" ], "BotNamePrefix": "", "Keep_Default_Loadout": false, "Kit": [ "low_monument_pistol.nailgun_1" ], "Day_Time_Spawn_Amount": 3, "Night_Time_Spawn_Amount": 2, "Announce_Spawn": false, "Announcement_Text": "", "BotHealth": 83, "Stationary": false, "UseCustomSpawns": false, "ChangeCustomSpawnOnDeath": false }, "Behaviour": { "Roam_Range": 40, "Aggro_Range": 40, "DeAggro_Range": 60, "Peace_Keeper": false, "Bot_Accuracy_Percent": 24, "Bot_Damage_Percent": 46, "Running_Speed_Boost": 0, "AlwaysUseLights": false }, "Death": { "Spawn_Hackable_Death_Crate_Percent": 0, "Death_Crate_CustomLoot_Profile": "", "Death_Crate_LockDuration": 600, "Corpse_Duration": 4, "Weapon_Drop_Percent": 100, "Min_Weapon_Drop_Condition_Percent": 0, "Max_Weapon_Drop_Condition_Percent": 100, "Wipe_Belt_Percent": 0, "Wipe_Clothing_Percent": 0, "Allow_Rust_Loot_Percent": 0, "Respawn_Timer": 10 }, "Other": { "Chute": false, "Suicide_Timer": 10, "Die_Instantly_From_Headshot": false, "Instant_Death_From_Headshot_Allowed_Weapons": [], "Parent_Monument": "Abandoned Supermarket 2", "Disable_Radio": true } } }, "MigrationDataDoNotEdit": { } } and upload that json file, restart the bot, the migration data remains empty and the bot will spawn centre map. Another oddity which is definitely related to this issue, is that the file isn't auto-formatted. eg when you used to load the bot using a json file our script created (or one manually typed our even), it would get formatted correctly when the mod loads. So if it's not tabulatted/spaced correctly like above, your mod with clean that up. That no longer happens (though the bot still spawns. However, once we add a custom profile via the UI, the migration data for all them are filled, and then the file is correctly formatted as well. Hope this makes sense. (Not that I care about it's formatting, but I feel the issue is related.)

Appreciated

We use a separate program to create custom profiles which gets uploaded over ftp daily. They're simply set to parent monuments. However, when the bot plugin loads, the migrationdata remains empty and the bots (those listed under customProfiles) all spawn in the centre of the map. If I use the UI and add a new profile, all the migrationdata gets auto filled for every profile, and then the custom profiles work perfectly thereafter. Is it possible to auto fill the correct migrationdata on bot load (or restart)? Or have the option to do so? Appreciated.

Think I've figured it out. If you removed the ParentMonument record so it just equals "" and then remove it's MigrationData, you'll get this error. So again, my fault. I'm using my own program to create the configs daily, and slipped up in situations where on a new map, certain monuments no longer appear. And it was was trying to add the old monuments but as they no longer exist, was leaving their parentmonument and migrationdata empty. And then BAM, that error appears. You should have a noedit not or something for the migration data *holds head in shame*

Found the issue for me (putting it here in case others get the same fault). I had added some new profiles which didn't have the necessary 'parent_monument'. Without this, I got the above error. So this was completely my fault. In all fairness, my custom profile config is over a 1MB in size at times (and my kits config is over 56MB) so I'm really stressing these mods to the limit Appreciate your work Steenamroo.

I'm getting a similar error with 2.1.4 Failed to run a 1.00 timer in 'BotSpawn v2.1.4' (KeyNotFoundException: The given key was not present in the dictionary.) at System.Collections.Generic.Dictionary`2[TKey,TValue].get_Item (TKey key) [0x0001e] in <eae584ce26bc40229c1b1aa476bfa589>:0 at Oxide.Plugins.BotSpawn.AddProfile (System.String name, Oxide.Plugins.BotSpawn+ConfigProfile monument, UnityEngine.Vector3 pos) [0x001a7] in <e4ff697bef80413dbe12b7a661ab50d5>:0 at Oxide.Plugins.BotSpawn.CheckMonuments (System.Boolean add) [0x0017b] in <e4ff697bef80413dbe12b7a661ab50d5>:0 at Oxide.Plugins.BotSpawn.SetupProfiles () [0x00000] in <e4ff697bef80413dbe12b7a661ab50d5>:0 at Oxide.Plugins.BotSpawn.<OnServerInitialized>m__0 () [0x001be] in <e4ff697bef80413dbe12b7a661ab50d5>:0 at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <c2afd8354b8b4f3ca451cf5a1aa111c3>:0