Skip to content
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

Confuse handling of lectern #1950

Open
6 tasks done
RedstoneFuture opened this issue Sep 10, 2022 · 2 comments
Open
6 tasks done

Confuse handling of lectern #1950

RedstoneFuture opened this issue Sep 10, 2022 · 2 comments
Labels
status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended

Comments

@RedstoneFuture
Copy link

WorldEdit Version

7.2.12

WorldGuard Version

7.0.8-beta-01

Platform Version

git-Paper-141 (MC: 1.19.2)

Confirmations

  • I am using the most recent Minecraft release.
  • I am using a version of WorldEdit compatible with my Minecraft version.
  • I am using a version of WorldGuard compatible with my Minecraft version.
  • I am using the latest or recommended version of my platform software.
  • I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
  • I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

If a player want to take a book from a lectern, the region need the activated "interact" flag (to open the GUI) and the "chest-access" flag to take the book.

But if the player wants to put the book back on the lectern, he must have building rights. This makes no sense compared to a normal inventory block.

Expected Behavior

With activated "interact" flag, the player has access to put the book back to the lectern too. He does not need build-permission for the region.

Reproduction Steps

  1. Region with a region-owner, "interact = true", "chest-access = true"
  2. Testplayer take a book
  3. Testplayer can't put the book back

Optional WorldGuard-Report

No response

Anything Else?

Now, the general question: was it planned this way and can it be changed?

@RedstoneFuture RedstoneFuture added status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended labels Sep 10, 2022
@wizjany
Copy link
Collaborator

wizjany commented Sep 10, 2022

due to bukkit event handling. dunno if i really want to deal with a workaround (or if it's really possible)

@RedstoneFuture
Copy link
Author

due to bukkit event handling. dunno if i really want to deal with a workaround (or if it's really possible)

Okay. Are there regular workarounds in WorldGuard due to event handling or rather rare?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended
Projects
None yet
Development

No branches or pull requests

2 participants