thx for support i stopped my server and reinstall plugin and now no bug

I'll investigate further and let you know what I find @Crowbar

i back on v2.0.4 and no error

Bastos

thx for support i stopped my server and reinstall plugin and now no bug

Thank you! And big thank you for your time and effort.

im getting it looks like everyone is getting it for the new plugin update

I'm also getting this error as well.

http://imgur.com/gallery/cptgUct

Running into this as well.

Deleted and reinstalled the plugin and let it generate new jsons. 

Noticed something weird.

My stone stacks used to be 5000. Now your json says this...

  "ItemId": -2099697608,
        "Shortname": "stones",
        "HasDurability": false,
        "VanillaStackSize": 5000,
        "CustomStackSize": 5000

That being said, everything is working properly and people aren't having the errors anymore. 

Nope, nevermind. Still broken. 

Share the exception you're all getting. Should show up in the server console. If it says ChestStacks plugin, unload the ChestStacks plugin. Otherwise post the exception, it'll help

Hi please could you assist im am getting the following error

RPC ERROR IN MOVE ITEM 

ssertionException: Assertion failure. Value was False

Expected: True

split_Amount <= 0

i dont have cheststacks installed    

Running into the same problem yet again. I get kicked for RPC Error each time I try to move something in my inventory.

AnExiledGod

Share the exception you're all getting. Should show up in the server console. If it says ChestStacks plugin, unload the ChestStacks plugin. Otherwise post the exception, it'll help

getting the same all my player got kicked for

RPC ERROR IN MOVE ITEM 

Nice

I won't be able to look at it for a few hours. Do the errors stop when the plugin is unloaded? And I need the data file for anyone getting this error so I can check something.I don't touch canmoveitem so I don't see why it'd be happening unless a stack was configured wrong

I deleted the .cs and associated .json files from my server, so I have nothing to give you. But, after moving them out and reloading, everything is vanilla and working fine. 

Everyone should role back to 3.0.0. I'll try to have a fix tonight.