Backpack plugin not working after installing plugin entity ownerSolved

We've removed entity owner plugin. Still not working. We've reinstalled backpack plugin and still not working. Rebooted server, still not working. Any advice ? Error below.

Failed to run a 0.10 timer in 'Backpacks v3.4.0' (NullReferenceException: Object reference not set to an instance of an object)   at Oxide.Plugins.Backpacks+Backpack.Get (System.UInt64 id) [0x0001d] in :0
at Oxide.Plugins.Backpacks+cAnonStorey4.<>m0 () [0x00000] in :0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in :0
Failed to run a 0.10 timer in 'Backpacks v3.4.0' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.Backpacks+Backpack.Get (System.UInt64 id) [0x0001d] in :0
at Oxide.Plugins.Backpacks+cAnonStorey4.<>m0 () [0x00000] in :0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in :0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) Failed to run a 0.10 timer in 'Backpacks v3.4.0' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.Backpacks+Backpack.Get (System.UInt64 id) [0x0001d] in

I have currently the same issues even in our test rig without any other plugin installed its the /backpackgui thats causing it as i see each time we click on the icon we recieve that error typing /backpack it works fine 

...............

Sorry to hear you folks are having issues. I'm not yet sure what could be causing this since errors cannot include line numbers unfortunately, and the method that seems to be having the error (Backpacks.Get()) doesn't appear to be able to throw a NullReferenceException under normal circumstances. That method also hasn't changed since 2 versions ago, so it's unclear why this error would suddenly start happening. I haven't been able to reproduce this but will attempt it after work with the info provided. One trend so far based on the above comments is that it happens with the backpack.open console command (or GUI button which runs that command). Any more info you can provide to reproduce the issue is appreciated.

Ts3hosting

...............

Not sure what this means. Could you elaborate? Are you also experiencing this issue? The above message is not helpful in debugging this issue whatsoever.

Heartlesswolve

I have currently the same issues even in our test rig without any other plugin installed its the /backpackgui thats causing it as i see each time we click on the icon we recieve that error typing /backpack it works fine 

That's interesting. Running the /backpackgui command should actually remove the gui button so you shouldn't be able to click it anymore after running that command. Did you mean that this happens after you have run that command a second time to re-enable the gui button, or is there possibly a bug where the gui button isn't removed?

Also, when reinstalling the plugin for testing purposes, please perform a full reset, by deleting the Data/Backpacks.json file and Data/Backpacks/ directory. If the plugin works after that, then it indicates something may have been wrong with the data files.

Thank you WhiteThunder. We are going to try the following "when reinstalling the plugin for testing purposes, please perform a full reset, by deleting the Data/Backpacks.json file and Data/Backpacks/ directory. If the plugin works after that, then it indicates something may have been wrong with the data files."

Will revert with any further findings or erros that appear.

I'm unable to reproduce any issue like this. I'm also not sure if this has anything to do with the Entity Owner plugin. I installed that and it didn't seem to cause any problems.

Both of you, feel free to PM me your discord tags so I can work with you more directly when I have time, since that may result in a faster resolution. Also, if you could try previous versions of the plugin to see if those work, that may be helpful for determining the root cause.

@Heartlesswolve can you paste the error you were seeing? You said it's the same as the one from the original poster, but I just want to see it for myself to make sure since these sorts of errors can look similar. The part about your case that I'm struggling to understand is why would it work for the chat command but not for the console command... A corrupt data file wouldn't explain that.

KuNVivBRyCQVkjZ.jpg WhiteThunder

Sorry to hear you folks are having issues. I'm not yet sure what could be causing this since errors cannot include line numbers unfortunately, and the method that seems to be having the error (Backpacks.Get()) doesn't appear to be able to throw a NullReferenceException under normal circumstances. That method also hasn't changed since 2 versions ago, so it's unclear why this error would suddenly start happening. I haven't been able to reproduce this but will attempt it after work with the info provided. One trend so far based on the above comments is that it happens with the backpack.open console command (or GUI button which runs that command). Any more info you can provide to reproduce the issue is appreciated.

Not sure what this means. Could you elaborate? Are you also experiencing this issue? The above message is not helpful in debugging this issue whatsoever.

That's interesting. Running the /backpackgui command should actually remove the gui button so you shouldn't be able to click it anymore after running that command. Did you mean that this happens after you have run that command a second time to re-enable the gui button, or is there possibly a bug where the gui button isn't removed?

Also, when reinstalling the plugin for testing purposes, please perform a full reset, by deleting the Data/Backpacks.json file and Data/Backpacks/ directory. If the plugin works after that, then it indicates something may have been wrong with the data files.

I still use the original "B" key to open the backpack and either tab/esc key to close it, i also have the backpack gui which i can use (slower) by pressing chat key and pressing "button" on the screen and pressing it again or tab/esc to close it, i am not getting any errors in console. so it might be something else in the config (a pure guess)
I have tried the /backpack in chat (much slower) and it opens the backpack and again no errors in console.
as it is a very basic config it would be hard to make a mistake with it

{
  "Drop on Death (true/false)": true,
  "Erase on Death (true/false)": false,
  "Use Blacklist (true/false)": false,
  "Clear Backpacks on Map-Wipe (true/false)": false,
  "Only Save Backpacks on Server-Save (true/false)": false,
  "Blacklisted Items (Item Shortnames)": [],
  "GUI Button": {
    "Image": "https://i.imgur.com/I2xhUzB.jpg?1",
    "Background color (RGBA format)": "0.3 0.3 0.3 0.8",
    "GUI Button Position": {
      "Anchors Min": "0.4 0.0",
      "Anchors Max": "0.4 0.0",
      "Offsets Min": "-245 18",
      "Offsets Max": "-205 78"
    }
  },
  "Backpack Size (1-7 Rows)": 7
}

it happends when users click on the backpackgui not the command itself we had an entire players got kicked and we recieved an error 
Under here you see the exact error when users click on the backpack icon

Failed to run a 0.10 timer in 'Backpacks v3.4.0' (AssertionException: Assertion failure. Value was False
Expected: True
Calling GiveUID - but already has a uid!)
  at UnityEngine.Assertions.Assert.Fail (System.String message, System.String userMessage) [0x00043] in <745c4d442eef4e08b35b5975d62d89d1>:0
at UnityEngine.Assertions.Assert.IsTrue (System.Boolean condition, System.String message) [0x0000f] in <745c4d442eef4e08b35b5975d62d89d1>:0
at ItemContainer.GiveUID () [0x00000] in <45235a51f18248a7ba30d3fad238508d>:0
at Oxide.Plugins.Backpacks+Backpack.Initialize () [0x0007b] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Plugins.Backpacks+Backpack.Open (BasePlayer looter) [0x00032] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Plugins.Backpacks+cAnonStorey4.<>m0 () [0x00010] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in :0
Heartlesswolve

it happends when users click on the backpackgui not the command itself we had an entire players got kicked and we recieved an error 
Under here you see the exact error when users click on the backpack icon

Failed to run a 0.10 timer in 'Backpacks v3.4.0' (AssertionException: Assertion failure. Value was False
Expected: True
Calling GiveUID - but already has a uid!)
  at UnityEngine.Assertions.Assert.Fail (System.String message, System.String userMessage) [0x00043] in <745c4d442eef4e08b35b5975d62d89d1>:0
at UnityEngine.Assertions.Assert.IsTrue (System.Boolean condition, System.String message) [0x0000f] in <745c4d442eef4e08b35b5975d62d89d1>:0
at ItemContainer.GiveUID () [0x00000] in <45235a51f18248a7ba30d3fad238508d>:0
at Oxide.Plugins.Backpacks+Backpack.Initialize () [0x0007b] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Plugins.Backpacks+Backpack.Open (BasePlayer looter) [0x00032] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Plugins.Backpacks+cAnonStorey4.<>m0 () [0x00010] in <9798bf7055004031aef80a45dfdcbd80>:0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in :0
That's actually a completely different error. They both start with Failed to run a 0.10 timer because all the backpack opening code runs on a delay, but you can clearly see the exception message is different.

I've seen that error reported when using a plugin that allows arbitrary items to be placed inside items, such as the plugin Box Mover. I am planning a fix for that case in the next update or two. My guess is that it's only particular backpacks that cannot be opened because they contain one of those special items. Also, are you sure the chat command worked when the console command didn't? That just doesn't seem possible since they run the same code. I'm guessing it was that one player whose backpack was broken tried to use the console command (or button), and one player whose backpack was not broken tried to use the chat command.

Since this is a different error, please open a new thread instead of replying here. Thank you.

Several improvements were made in Backpacks v3.5.0 to prevent NullReferenceException errors. Please update, and open a new thread if you experience any more errors.

Locked automatically