EngineHub / EngineHub/WorldGuard

Tnt approval/denial based off location of clicked block not location of block placed

Open
#1,859 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

7.2.9-SNAPSHOT

### WorldGuard Version

7.0.7-SNAPSHOT

### Platform Version

git-Paper-70

### 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

```
System information
Java 17
Minecraft 1.18.1
Paper 70 for 1.18.1
WorldEdit 7.2.9-SNAPSHOT
WorldGuard 7.0.7-SNAPSHOT
```

It appears this is exclusive to tnt placement.
Placing tnt off a block in a region you don't have permission to will deny you even though you don't lack permission where the tnt would have been placed. I made a video with a short demonstration [here](https://www.youtube.com/watch?v=05VSrPBxUwo).

### Expected Behavior

Determining what regions are applicable when placing tnt should be based off where the tnt is placed not what block is clicked when placing it. Just like any other block.

### Reproduction Steps

1. Create region
2. Revoke your permissions from that region
3. Outside the region, place a tnt off a block that is the edge of that region

### 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.