{"action":"created","issue":{"url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/663","repository_url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention","labels_url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/663/labels{/name}","comments_url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/663/comments","events_url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/663/events","html_url":"https://github.com/MinecraftPortCentral/GriefPrevention/issues/663","id":326687092,"number":663,"title":"/at and /ct now giving players block-break access (plus piston bug)","user":{"login":"Corcustos","id":15864775,"avatar_url":"https://avatars3.githubusercontent.com/u/15864775?v=4","gravatar_id":"","url":"https://api.github.com/users/Corcustos","html_url":"https://github.com/Corcustos","followers_url":"https://api.github.com/users/Corcustos/followers","following_url":"https://api.github.com/users/Corcustos/following{/other_user}","gists_url":"https://api.github.com/users/Corcustos/gists{/gist_id}","starred_url":"https://api.github.com/users/Corcustos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Corcustos/subscriptions","organizations_url":"https://api.github.com/users/Corcustos/orgs","repos_url":"https://api.github.com/users/Corcustos/repos","events_url":"https://api.github.com/users/Corcustos/events{/privacy}","received_events_url":"https://api.github.com/users/Corcustos/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-05-25T23:15:30Z","updated_at":"2018-05-26T02:43:07Z","closed_at":"2018-05-26T00:14:28Z","author_association":"NONE","body":"As the title says, if I do ./ct or ./at in any claims to allow users to use pixelmon PCs, doors, etc, it allows them to block-break, but they still cannot block-place. The claimflag for block-break is false, and I even set an override for admin claims to no avail. There's not really much other information to give. I do ./at all OR /ct all, and they can break blocks now. Remove it, and they cannot. This isn't so much of an issue for admin claims because all I need enabled is interact-block-secondary, but this also happens in user claims.\r\n\r\nNote: Turns out the interact-block-primary flag specifically allows people to break blocks. It did not in 578. interact-block-secondary doesn't allow people to place blocks though, so I'm really confused.\r\n\r\nI am using the following versions:\r\nGP 4.3.0.587\r\nSF 3105 - Forge 2655\r\nLP 4.2.13\r\n\r\nNobody has the \"griefprevention.*\", or \"*\" commands. Additionally, when I first upgraded GP from 578, this issue did not occur. It was only after a restart that this started happening.\r\n\r\nGPDebug: https://griefprevention.github.io/debug/?ELxduy1ICn\r\nNot sure if this helps, but I had a user break blocks with ./at and ./ct on. Their user is Syco_KN. I also broke some blocks as well.\r\n[latest.log](https://github.com/MinecraftPortCentral/GriefPrevention/files/2041065/latest.log)\r\n[fml-junk-earlystartup.log](https://github.com/MinecraftPortCentral/GriefPrevention/files/2041066/fml-junk-earlystartup.log)\r\n\r\n(I can't upload a debug.log because it's too large for both here and gist)\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/comments/392230149","html_url":"https://github.com/MinecraftPortCentral/GriefPrevention/issues/663#issuecomment-392230149","issue_url":"https://api.github.com/repos/MinecraftPortCentral/GriefPrevention/issues/663","id":392230149,"user":{"login":"bloodmc","id":2998171,"avatar_url":"https://avatars2.githubusercontent.com/u/2998171?v=4","gravatar_id":"","url":"https://api.github.com/users/bloodmc","html_url":"https://github.com/bloodmc","followers_url":"https://api.github.com/users/bloodmc/followers","following_url":"https://api.github.com/users/bloodmc/following{/other_user}","gists_url":"https://api.github.com/users/bloodmc/gists{/gist_id}","starred_url":"https://api.github.com/users/bloodmc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bloodmc/subscriptions","organizations_url":"https://api.github.com/users/bloodmc/orgs","repos_url":"https://api.github.com/users/bloodmc/repos","events_url":"https://api.github.com/users/bloodmc/events{/privacy}","received_events_url":"https://api.github.com/users/bloodmc/received_events","type":"User","site_admin":false},"created_at":"2018-05-26T02:43:07Z","updated_at":"2018-05-26T02:43:07Z","author_association":"CONTRIBUTOR","body":"Your sponge log is filled with errors from the plugin de.randombyte.commandutils. Remove that plugin and try again. If it still does not work then you need to do what I asked and reproduce on a clean server as there is clearly something on your end breaking it. GPDebug reports false so the issue is not on my end."}}
{"actor":{"display_login":"bloodmc"}}