Skip to content

fix: owners could not build if #public had a non-build trust allowed#472

Open
ItsMacs wants to merge 1 commit intoWiIIiam278:masterfrom
ItsMacs:master
Open

fix: owners could not build if #public had a non-build trust allowed#472
ItsMacs wants to merge 1 commit intoWiIIiam278:masterfrom
ItsMacs:master

Conversation

@ItsMacs
Copy link

@ItsMacs ItsMacs commented Nov 28, 2025

For some reason, owners weren't allowed to place vanilla blocks on top of Nexo blocks (at this point I'm drawn to think it's on top of all block entities, as Nexo blocks are noteblocks) if #public had a non-build trust assigned.

Repeating the owner check fixes this, as the workaround on our server was to set the owner also as co-owner.
It isn't the cleanest fix, but it's a workaround until the reason is figured out.

@WiIIiam278
Copy link
Owner

WiIIiam278 commented Nov 28, 2025

Hey, thanks for your interest in contributing.
I'm a bit confused though. What even is a 'Nexo block'? Some kind of Lucky Block plugin? Can you reproduce this behaviour without the plugin? If you're attempting to block third party plugin actions, a hook for that plugin may be needed within the plugin itself that handles the huskclaims API. It sounds like maybe this plugin has listeners at conflicting priority orders?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants