-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interact allowed in an Authority but cannot interact #29
Comments
This is really weird! If you exclude a player from this authority only, are they still unable to interact? This might imply that a different authority is taking priority |
Excluding someone does allow interaction. But I also only have 1 authority set up. |
I hopped back on and re-did pretty much everything. Interacting as a whole works now but crafting and specifically some profession blocks don't work. I recorded a small video so you can see what's going on. |
Apologies for the delay! I've looked into this issue and identified where it's coming from. Will be looking into the best way to resolve this, hopefully soon! 🙂 For now, a workaround is to set |
No worries! Thanks for the reply no matter how delayed it is. :) If you need any assistance testing stuff I'd be more than happy to help as well. |
Has this bug ever been looked further into? I'm still having this issue as I have an authority that overrides a "deny" flag for interact. I can't just set it to pass as that's not enough. |
I experienced the same bug during setup today. Setting (I don't know whether it was a combination of these that fixed it or not, I know having all of them on allow but having interact on pass did not work. This was on 1.21.1 Fabric using version 0.3.9+1.21.1) |
Installed Leukocyte version 0.3.3+1.18 to our All of Fabric 5 server. Set an authority to protect a spawn area but allowed the rule for interact so that people could open doors, use waystones, etc. No one other than OP's can actually interact with items though. Screenshot provided of our rule set up
.
The text was updated successfully, but these errors were encountered: