Hey,

As the title says, I'm unable to auto-spawn bots after setting autospawn=true. I get the following message in my console:

 

Failed to run a 1.00 timer in 'BotSpawn v2.1.1' (NullReferenceException: Object reference not set to an instance of an object)

at Oxide.Plugins.BotSpawn.AddProfile (System.String name, Oxide.Plugins.BotSpawn+ConfigProfile monument, UnityEngine.Vector3 pos) [0x0001a] in <c47c8495443945238d69e53449638a81>:0

at Oxide.Plugins.BotSpawn.CheckMonuments (System.Boolean add) [0x00180] in <c47c8495443945238d69e53449638a81>:0

at Oxide.Plugins.BotSpawn.SetupProfiles () [0x00000] in <c47c8495443945238d69e53449638a81>:0

at Oxide.Plugins.BotSpawn.<OnServerInitialized>m__0 () [0x001be] in <c47c8495443945238d69e53449638a81>:0

at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <ec05e0208c9149bba43236ca58fea105>:0

(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

 

One thing I've been able to do, I can set custom profiles and manually spawn bots. The json file in the data folder is updated; however, when the plugin is reloaded and I try to spawn bots using the same custom profile, it says "There is no profile by that name in default or custom profiles jsons."

Any help is much appreciated, thank you!

Hi,

I think it has to be some kind of mistake in one of the data files that isn't getting caught.
Would you mind attaching the -DefaultProfiles and -CustomProfiles json files for your current prefix?

Thanks.

Yeah no problem. Just using the default prefix, haven't changed too much in the data files though. 

 

Edited January 18 by Tyler MacGregor

Yeah, not sure how it's happened but the contents of 'default-DefaultProfiles.json' is null.

Delete that file and reload BotSpawn and you should get a new file to work with.

I will try that, but I think that file ending up null occured in the download process. I will let you know. Cheers!

 

It worked, thanks so much for the speedy reply. Idk how that file ended up null but I feel a little braindead not seeing that haha glad it's working now. Thank you!

No problem. To be fair BotSpawn should catch that and set it straight...I thought it did, actually, but obviously not.

Next V will.