EngineHub / EngineHub/WorldGuard

The `pvp` flag doesn't protect against crystal PvP

Open
#2,233 0 comments 0 reactions 0 assignees View on GitHub
status:pending type:bug
Dominant language
Java
Stars
938
Forks
671
PR merge metrics
No merged PRs in 30d

Description

### WorldEdit Version

Bukkit-Official(7.3.16+cbf4bd5)

### WorldGuard Version

Bukkit-Official (7.0.14+2339-43997ec)

### Platform Version

Paper 1.21.8 Build #60

### Confirmations

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

### Bug Description

The title says it all pretty much - in a region where the `pvp` flag is set to `deny`, players can kill each other by blowing up end crystals. Although, weirdly, if you set up a plugin that listens for `DisallowedPVPEvent`, you'll notice that the event does actually get called, but players still receive damage from the explosion.

### Expected Behavior

Players who are not the player who blows up the end crystal should not take damage from the explosion.

### Reproduction Steps

1. Create a region
2. Set the `passthrough` flag to `allow` in the region to allow building
3. Set the `pvp` flag to `deny` in the region
4. Have two players stand next to an end crystal, all within the region
5. Have one of the players blow up the end crystal
6. Observe as the player who did not blow up the end crystal takes damage
### Optional WorldGuard-Report

_No response_

### Anything Else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.