-
Notifications
You must be signed in to change notification settings - Fork 12
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
Players can obtain barrier blocks through the claiming interface #154
Comments
I can confirm, that this problem is a general one! |
This is fixed in the imminent v2 release but seeing as this is a critical issue I don't mind patching it quickly |
Do note that disabling automatic closing of the claim menu when leaving does not make people attempting the glitch stuck because you can still exit by clicking an empty hotbar slot |
Also seems Paper-specific as Spigot does not physically have |
Here's the dev build (from this branch), won't be able to test myself for at least a few hours. |
Works! Can't interact with an item frame anymore, when in editing mode - nice! |
Will 1.21.4 also work? Can't upgrade yet, since Paper is currently not fully released for 1.21.4. |
I don't see why not, since XClaim doesn't use any bleeding API or server internals. It broke for ~1.20 due to using server internals via ParticleLib, but ParticleLib is now completely removed from the plugin. It's fetched automatically for older servers. That being said, you never really know until you try. The most likely issue is maybe Adventure sneaking out of date, which should be helped by Dependabot and completely obsoleted soon-ish. |
😐 The scope of exceptions to the interaction system never ceases to amaze me. Feel free to create another issue. |
This issue had already been addressed in #59 but it seems that it isn't patched, at least not in the latest versions:
The glitch hasn't changed:
8mb.video-Koz-HMFF8rPM.mp4
As a temporary fix, you can put this command in repeating command blocks (tested on 1.21.3):
8mb.video-M5V-6NA6vRvb.mp4
The text was updated successfully, but these errors were encountered: