WorldEdit Version

7.3.6+6892-3d660b8

WorldGuard Version

7.0.11+068ad68

Platform Version

I've tested on spigot and paper multiple 1.21.1 versions

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

When you you shoot a bow in an area you aren't allowed to build (or hurt entities) in, it says "You can't hit that here". I've attached a video

Expected Behavior

It shouldn't say this

Reproduction Steps

1. fire a bow
2. Watch the message

Optional WorldGuard-Report

No response

Anything Else?

No response

can't repro. please provide a proper minimal reproducible example and steps if you think this is a WG issue.

I am running no plugins now (only WorldEdit and WorldGuard). I simply made a region and didn't add any flags to it. Left it as a default region.

I had my alt try to shoot a bow and it says "Hey! Sorry, but you can't hit that here"

This server is running Paper version 1.21.1-77-master@4ff58c4 (2024-09-12T18:05:09Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version

Worldguard ver: 7.0.11+068ad68

As this is a paper build with normal WG build and NO other plugins, I am unsure how it's not replicating for you @wizjany

Here is my full startup log

https://paste.md-5.net/uwowapezix.md

The issue is that WG doesn't even listen to uh... bow firing? projectile movement?

The message implies that the arrow is actually hitting something (entitydamage i guess?). Perhaps try turning on the event logger and provide the output of that so I can see what event and what target is triggering it.

I will be able to do that as soon as I am back home :)

For further info, the message is sent directly as the arrow is fired and not when it lands. So it implies that the player itself is the entity trigger it. But we will see with the debug later

Ok so the issue is specifically the flame enchantment on the bow ... setting the arrow on fire. However, this doesn't appear to be changed behavior in WG. Has this only started happening recently?

This has only happened since I updated to 1.21 from 1.20.4. I am using WG 7.0.9+5934e49 and WE 7.3.3+6788-6359df8 on my 1.20.4 servers and no issue there. So somewhere between those 2 vers is where the issue was created

Aite @wizjany here ya go:

[16:05:29 INFO]: [WorldGuard] USE BOW [CraftPlayer{name=princess_lyds}] @world : PlayerInteractEvent
[16:05:30 INFO]: [WorldGuard] DAMAGE ARROW [CraftPlayer{name=princess_lyds}] @374,67,107 : EntityCombustByEntityEvent [DENY]

yea, the behavior of the flame enchant must have changed either on mojang's or spigot's end.
not sure if that's a bug or intentional, guess we will have to workaround it as usual.

Awesome thanks! Glad we got to the bottom of it