ForgeEssentials

ForgeEssentials

339k Downloads

[1.7.10] permission deny with storage drawers isn't working

X-Coder opened this issue ยท 5 comments

commented

1.7.10, tested with rev. 1330+1341.

I tried to deny access in a zone to a left click on a storage drawer by using /p user ... deny fe.protection.interact.StorageDrawers.fullDrawers4.* but it still gives me the item of the storage drawer when I left click on it. Same with /p group.
Is this a bug? Do you know how I can prevent this?

If I use fe.protection.interact.* it makes no difference. It works fine on other blocks, but not with storage drawers. /protectdebug is printing me the same permission name when I left click on the storage drawer.

/p group ALL zone zonename is listing the permission I set.

This is the sources to storage drawers, if it helps.
In their sources they used a onBlockClicked override.

commented

Use /p debug and see what permissions are being checked when you right click a storage drawer.

commented

On right and left click it prints in red: fe.protection.interact.StorageDrawers.fullDrawers4.1

Which I blocked with using /p user zone deny fe.protection.interact.StorageDrawers.fullDrawers4.1

The main problem is the left click on the storage drawer, but right click behaves strange too some times, it feels like it is adding a item half way when permission is denied.

Storage drawers has a key based auth system called "personal key" built in, when crafted and placed it allows to restrict single drawers only to the owner.
With FE it would allow a much finer group and zone based restriction.

I'm the only one with this problem?

commented

As we moved to 1.12.2, is this still an issue? Closing this issue in 7 days if no response @X-Coder

commented

Thanks for replying and testing on 1.12.2 @X-Coder.
As all focus is now on 1.12.2 I'll close this issue

commented

Thought this project was dead, good to see you are working again on it, because I like it very much.

Just tested it in 1.12.2, no problems so far for in this version. But the reported 1.7.10 is still bugged, but I don't mind if you can't fix it as I currently don't have much time anyway.