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

Regions in the end or nether are not protected from exploding beds #1675

Open
stonar96 opened this issue Nov 29, 2020 · 3 comments
Open

Regions in the end or nether are not protected from exploding beds #1675

stonar96 opened this issue Nov 29, 2020 · 3 comments
Labels
status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended

Comments

@stonar96
Copy link
Contributor

stonar96 commented Nov 29, 2020

Versions

WorldEdit version: 7.2.0

WorldGuard version: 7.0.4

Platform version: git-Paper-298 (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)

Describe the bug

Regions in the end or nether are not protected from exploding beds, even though the player who tried to sleep in the bed cannot build in the region (is not a member of the region).

To Reproduce

  1. Go to the end or nether
  2. Create a region.
  3. Make sure you cannot build in the created region.
  4. Place a bed next to the created region.
  5. Try to sleep in the placed bed.
  6. The region is not protected from the explosion.

Expected behavior

The region to be protected from the explosion as it is for TNT, saplings, pistons, ... Either the bed or the player (who tried to sleep in the bed) shouldn't be treaded as member of the created region in this case, if they aren't.

Screenshots

I think the issue is described well enough.

Additional context

I know there is a flag for those explosions, namely other-explosion. However, I don't want to disable other-explosions entirely inside the created region. Also there are flags for TNT and pistons for example and regions are nevertheless protected from them if they are no members.

@stonar96 stonar96 added status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended labels Nov 29, 2020
@Joo200
Copy link
Collaborator

Joo200 commented Nov 29, 2020

grafik
Works fine for me.

Pls join the discord for more help and provide your region setup

@stonar96
Copy link
Contributor Author

stonar96 commented Nov 29, 2020

Just to clarify:
@Joo200 didn't reproduce the issue as described above. The bed has to be placed outside of the created region, where the player can sleep.

The behavior was discussed on Discord to be intended. The explosion is associated to the bed location, just the other-explosion flag defaults to true since it isn't meant to be associated. (See difference between protection related flags and mobs, fire and explosions related flags.)

@wizjany
Copy link
Collaborator

wizjany commented Nov 29, 2020

just to be clear, the behavior is working as expected - I'm not sure if it's working as intended. I think it might be worth investing if (and if so, why) respawn anchors have the same (or different) behavior when in the overworld (possibly due to the explode events?) and think about how to properly classify bed explosions (preferably without breaking current setups which rely on the other-explosion flag to prevent bed explosions).

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

3 participants