Jump to content

Botspawn throwing timer errors, then refusing to spawn.

Pending 2.2.2

Hi, I am trying to run BotSpawn, but upon loading the plugin, I get

"Failed to run a 0.50 timer in 'BotSpawn v2.2.2' (ArgumentException: The Object you want to instantiate is null.)" printed in console, followed by "

at UnityEngine.Object.Instantiate (UnityEngine.Object original, UnityEngine.Vector3 position, UnityEngine.Quaternion rotation) [0x00049] in <c8dc2b468d1841099baa4dd8a110cc44>:0

at UnityEngine.Object.Instantiate[T] (T original, UnityEngine.Vector3 position, UnityEngine.Quaternion rotation) [0x00001] in <c8dc2b468d1841099baa4dd8a110cc44>:0

at Facepunch.Instantiate.GameObject (UnityEngine.GameObject go, UnityEngine.Vector3 pos, UnityEngine.Quaternion rot) [0x00007] in <1a813de50fac44e5b0be384ca2521394>:0

at Oxide.Plugins.BotSpawn.InstantiateSci (UnityEngine.Vector3 position, UnityEngine.Quaternion rotation, System.Boolean murd) [0x0002e] in <b6d2348e10d2481c882a414806c99cf3>:0

at Oxide.Plugins.BotSpawn.SpawnBots (System.String name, Oxide.Plugins.BotSpawn+DataProfile zone, System.String type, System.String group, UnityEngine.Vector3 location, System.Int32 spawnNum, System.Boolean initial) [0x003db] in <b6d2348e10d2481c882a414806c99cf3>:0

at Oxide.Plugins.BotSpawn+<SetupProfiles>c__AnonStorey16.<>m__0 () [0x00087] in <b6d2348e10d2481c882a414806c99cf3>:0

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

Then all bots refuse to spawn. Any help would be greatly appreciated.

  • Like 1

Share this comment


Link to comment
2 hours ago, Taracmeden said:

Hello, I am getting this error too. I am not on staging myself

Did you have that issue with oxide where your server would throw apex exceptions then not start? And can you spawn murderers in console?

Share this comment


Link to comment
On 11/22/2021 at 1:06 AM, ChogChey said:

Did you have that issue with oxide where your server would throw apex exceptions then not start? And can you spawn murderers in console?

I did! I fixed it by spinning up a server on my own pc, then transferring the files in the RustDedicated_Data/Managed folder over to my main server's folder
That did not fix this issue though

Share this comment


Link to comment
On 11/21/2021 at 7:51 PM, Taracmeden said:

Hello, I am getting this error too. I am not on staging myself

We had that issue, but managed to fix it by deleting all files and starting over again. I'm hoping the next oxide version will be less glitchy, and will be more compatible with plugins. Lol.

  • Like 1

Share this comment


Link to comment
1 hour ago, ChogChey said:

We had that issue, but managed to fix it by deleting all files and starting over again. I'm hoping the next oxide version will be less glitchy, and will be more compatible with plugins. Lol.

Did you delete all the botspawn files or all the files?

Share this comment


Link to comment
2 hours ago, Taracmeden said:

Did you delete all the botspawn files or all the files?

I wasn't able to get BotSpawn working, that's just what I did to fix it. I deleted all files in the server, and started fresh.

Share this comment


Link to comment
347.9k

Downloads

Total number of downloads.

1.8k

Customers

Total customers served.

23.7k

Files Sold

Total number of files sold.

369k

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.