Jump to content

Profile (Re)spawning as Scientists instead of as Configured

No Response 1.0.3
Solarix

By Solarix,

  • Report this file
    • Solarix

    Some monuments in the default profile are experiencing scientists spawning where they should be spawning as Zombies, usually mixed.  Seeing these errors in console, could also be related to the day/night cycle issue... 

    Failed to run a 0.20 timer in 'BotReSpawn v1.0.3' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotReSpawn+CustomGroup+<PostSpawnProcess>c__AnonStorey0.<>m__0 () [0x0011c] in <8af9b651957840ee900a97b3dc81d4d4>:0 
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <9882f28dc2204b4dba514a9ad18f5042>:0 
Failed to run a 0.20 timer in 'BotReSpawn v1.0.3' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotReSpawn+CustomGroup+<PostSpawnProcess>c__AnonStorey0.<>m__0 () [0x0011c] in <8af9b651957840ee900a97b3dc81d4d4>:0 
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <9882f28dc2204b4dba514a9ad18f5042>:0 
Failed to run a 0.20 timer in 'BotReSpawn v1.0.3' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotReSpawn+CustomGroup+<PostSpawnProcess>c__AnonStorey0.<>m__0 () [0x0011c] in <8af9b651957840ee900a97b3dc81d4d4>:0 
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <9882f28dc2204b4dba514a9ad18f5042>:0 
Failed to run a 0.20 timer in 'BotReSpawn v1.0.3' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BotReSpawn+CustomGroup+<PostSpawnProcess>c__AnonStorey0.<>m__0 () [0x0011c] in <8af9b651957840ee900a97b3dc81d4d4>:0 
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <9882f28dc2204b4dba514a9ad18f5042>:0 
ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

     

    Share this comment

    Link to comment
    Robert A Puccini

    Similar issue here. Was this resolved or is there a fix? I have scientist spawning with my "Zombie" profile. Scientist also don't seem to despawn so I have areas that are super congested. Scientist also murking anyone who gets into line of sight.

     

    Calling 'Unload' on 'BotReSpawn v1.0.3' took 1096ms

    Unloaded plugin BotReSpawn v1.0.3 by Steenamaroo

    Loaded plugin BotReSpawn v1.0.3 by Steenamaroo

    NullReferenceException: Object reference not set to an instance of an object

    at Oxide.Plugins.BotReSpawn.SelectWeapon (HumanNPC npc) [0x000e2] in :0

    at Oxide.Plugins.BotReSpawn+BotData.SelectWeapon () [0x00000] in :0

     

    (Filename: Line: 0)

    NullReferenceException: Object reference not set to an instance of an object

    at Oxide.Plugins.BotReSpawn.SelectWeapon (HumanNPC npc) [0x000e2] in :0

    at Oxide.Plugins.BotReSpawn+BotData.SelectWeapon () [0x00000] in :0

     

    (Filename: Line: 0)

    NullReferenceException: Object reference not set to an instance of an object

    at Oxide.Plugins.BotReSpawn.SelectWeapon (HumanNPC npc) [0x000e2] in :0

    at Oxide.Plugins.BotReSpawn+BotData.SelectWeapon () [0x00000] in :0

    Edited by Robert A Puccini
    • Like 1

    Share this comment

    Link to comment
    Steenamaroo

    Hi,

    To the best of my knowledge all of these issues are resolved now. The current public version is V1.0.5 - You should grab that.

    If you saw an error relating to Unload() method, it's possible you may have some npcs on your map which BotSpawn failed to destroy.

    It was a pretty rare issue but I did get reports from one or two people about it.


    Those npcs would be 'rogue' - No longer subject to BotReSpawn control so it's possible you'd continue to see errors or issues relating to those npcs while they are still alive, even after updating the plugin.
    Once they're all dead, or after your next scheduled server restart, all should be fine.

    Sorry for any inconvenience with this.

    • Like 1

    Share this comment

    Link to comment
    1.1m

    Downloads

    Total number of downloads.

    5.6k

    Customers

    Total customers served.

    80.7k

    Files Sold

    Total number of files sold.

    1.6m

    Payments Processed

    Total payments processed.

    Customers

    Providers

    Resources

    About Us

    Codefling is the largest marketplace to buy and sell plugins, maps, tools, and more! Our modern platform makes it easy to find exciting new content while providing a feature-rich environment for creators to monetize their work!

    ×
    ×
    • 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.