Problem by using Items with 1.10
blablubbabcDEV opened this issue ยท 4 comments
Migrated from: https://dev.bukkit.org/projects/shopkeepers/issues/431
Originally posted by Telbaru (Jul 25, 2016):
I use this config: http://pastebin.com/jBXJn7bpPermissions are OP so there should not be a problem.I Use the Item what i used in the config: a Paper with the exact name and lore. This is the Item what i used since 3 month without problems. I set a chest and klick right on the chest with the paper in the hand and then on the ground where the villager should stand and right after the klick on the chest it comes the permissions problem. Since the 1.10.2 there is the permission problem so i edited the config for the new versions but the problem is the same.
I think this problem is only by items with names and lore. Normal items like the Paper wihtout name and lore operates right.
Originally commented by blablubbabc (Jul 25, 2016):
I just tried it with your exact given config, and shop creation works fine for me with your custom paper item. So it has to be something else which is preventing the shop creation for you.
Could you please verify that the 'no permission' message your get is the one from shopkeepers and not from some other plugin. For that, compare it to the message in the config. Though I am not sure if another plugin would even be able to prevent the shop creation by preventing the interaction there..
And you can temporarily turn on debug mode and see if that prints something useful to the console.
And of course, make sure that your are not in creative mode.
If nothing helps, try it on a fresh local server with no other plugins running and verify for yourself that it works. And then try to track down the plugin which could be causing this.
Originally commented by Telbaru (Jul 26, 2016):
okay i tested it with a clean server and found an other plugin that blocked the permissions. So i have to talk with the autor. Thanks for testing and sry that i failed :/
Originally commented by blablubbabc (Jul 26, 2016):
[at]Telbaru:
Would you mind sharing which other plugin was causing this? In case somebody else runs into this issue.