Jump to content

Faled to call hook "DestroyController"

Pending 2.1.8

r0gi
r0gi

Posted

Hi my friend....since last Update:

 Failed to call internal hook 'DestroyController' on plugin 'BetterNpc v2.1.8' [1320420410] (Object reference not set to an instance of an object)
at void Oxide.Plugins.BetterNpc.DestroyController(string name, Vector3 position) in /home/rustserver/serverfiles/carbon/plugins/BetterNpc.cs:line 2836
at object Oxide.Plugins.BetterNpc.InternalCallHook(uint hook, object[] args) in BetterNpc.cs/Internal:line 291

aimacak

Posted

14 hours ago, r0gi said:

Hi my friend....since last Update:

 Failed to call internal hook 'DestroyController' on plugin 'BetterNpc v2.1.8' [1320420410] (Object reference not set to an instance of an object)
at void Oxide.Plugins.BetterNpc.DestroyController(string name, Vector3 position) in /home/rustserver/serverfiles/carbon/plugins/BetterNpc.cs:line 2836
at object Oxide.Plugins.BetterNpc.InternalCallHook(uint hook, object[] args) in BetterNpc.cs/Internal:line 291

Hello, please send the server logs that contain this error.

aimacak

Posted (edited)

@r0gi

Hello again, additional information has appeared. If you have both BetterNpc and GasStationEvent installed (or any other event that has the function of removing BetterNpc on the monument at the start of the event), and this monument is disabled in BetterNpc, this error occurs, just change the parameter in the GasStationEvent (or any other) configuration.

 

 Change this:

"Disable NPCs from the BetterNpc plugin on the monument while the event is on? [true/false]": true,

to this:
 

"Disable NPCs from the BetterNpc plugin on the monument while the event is on? [true/false]": false,

 

Edited by aimacak
2.3m

Downloads

Total number of downloads.

10.7k

Customers

Total customers served.

154.4k

Files Sold

Total number of files sold.

3.3m

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.