Failed to run a 0.10 timer in 'Backpacks v3.3.0' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.Backpacks.TryMigrateData (System.String fileName) [0x0001f] in <5f149cd53afa4f478f370cdc6df048c6>:0
at Oxide.Plugins.Backpacks+Backpack.Get (System.UInt64 id) [0x0005e] in <5f149cd53afa4f478f370cdc6df048c6>:0
at Oxide.Plugins.Backpacks+<OpenBackpackConsoleCommand>c__AnonStorey4.<>m__0 () [0x00000] in <5f149cd53afa4f478f370cdc6df048c6>:0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <ec05e0208c9149bba43236ca58fea105>:0NullReferenceException at TryMigrateDataFixed
You mentioned in discord that this showed up after restarting the server after a crash. It also looks like this happens when a player is opening their backpack. One guess is that the player's backpack data file was being saved when the crash occurred which corrupted the file. If any specific players are reporting that their backpacks won't open, then you could look at the files in the
oxide/data/Backpacks directory for those players' steam ids to see if those files can be opened. You may be able to recover some of the data from the file, but it's likely that they will simply needs to be deleted and the player(s) will have to start over with a new empty backpack. Okay thank you i will ask my players and open a Support Ticket at my Forum! Thanks!
Backpacks v3.5.0 included some fixes to prevent NullReferenceException errors in the case of data corruption, one of which was in the TryMigrateData method, so marking this as Fixed. Please open a new thread if the error returns.
Locked automatically