Jump to content

Stacksize - Editor probaly crashed

Closed 1.0.20

Kaho

Hey King,

changed the Global Stacksize bback to 1 as i dont want to Stack Weapons
Now i started Changing every Categorie to 3 expect Guns

Noticed that Medics are missing and saw a "button" next to "Guns" on the right side.
But its cuttet.

As soon as i pushed the Cutted button i get this error in Console:

 

Failed to call hook 'CMD_cmd' on plugin 'Loottable v1.0.18' (KeyNotFoundException: The given key was not present in the dictionary.)
  at System.Collections.Generic.Dictionary`2[TKey,TValue].get_Item (TKey key) [0x0001e] in <fb001e01371b4adca20013e0ac763896>:0 
  at Oxide.Plugins.Loottable.CreateStacksizeUI (BasePlayer player) [0x00859] in <8fac58e6a57b4f38897c358a38016821>:0 
  at Oxide.Plugins.Loottable.CMD_cmd (Oxide.Core.Libraries.Covalence.IPlayer player, System.String command, System.String[] args_0) [0x00522] in <8fac58e6a57b4f38897c358a38016821>:0 
  at Oxide.Plugins.Loottable.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x024ce] in <8fac58e6a57b4f38897c358a38016821>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <09575a60985045248bcb43b20faeeb99>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <bae5f1223fce49c493b01571c99dce02>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <bae5f1223fce49c493b01571c99dce02>:0 


Also i get the Message "If you can read this, the editor probaly crashed :(. Try Closing and opening it again"

But nothing Works... unloaded / reloaded... nothing.

Any Tips?

Link to comment
1.2m

Downloads

Total number of downloads.

6.1k

Customers

Total customers served.

90.3k

Files Sold

Total number of files sold.

1.8m

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.