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

Wind Burst enchant not sending users back into the air #2147

Closed
6 tasks done
baailey opened this issue Sep 20, 2024 · 6 comments
Closed
6 tasks done

Wind Burst enchant not sending users back into the air #2147

baailey opened this issue Sep 20, 2024 · 6 comments
Labels
status:invalid This does not describe a request or bug with WorldGuard type:bug Incorrect behavior, not working as intended

Comments

@baailey
Copy link

baailey commented Sep 20, 2024

WorldEdit Version

7.3.7-SNAPSHOT+6926-485bb41

WorldGuard Version

7.0.13-SNAPSHOP+2301-d9716a5

Platform Version

Paper 1.21.1-85-master

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 drop down onto an entity and hit them with a Mace that has the Wind Burst enchant, it is not sending the user back into the air as it should.

Expected Behavior

For the player to be sent into the air upon hitting an entity.

Reproduction Steps

  1. Give yourself a Mace
  2. Enchant it with the Wind Burst enchant
  3. Fall from a height above the entity and hit them while you are in mid-air

Optional WorldGuard-Report

No response

Anything Else?

No response

@baailey baailey added status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended labels Sep 20, 2024
@wizjany wizjany added status:invalid This does not describe a request or bug with WorldGuard and removed status:pending Pending acceptance or closure. labels Sep 20, 2024
@wizjany
Copy link
Collaborator

wizjany commented Sep 20, 2024

the server doesn't even send an event for this so i'm unsure how WG could even be causing issues here. not sure if you think this is related to a region setup (your steps don't mention regions at all) or what, but it's working perfectly fine.

@wizjany wizjany closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2024
@baailey
Copy link
Author

baailey commented Sep 20, 2024

this was tested with only worldedit and worldguard in a global region with no flags. on a paper server with no plugins it works as intended, but after adding worldedit and worldguard it does not. unsure what other info I can provide for you here.

@baailey
Copy link
Author

baailey commented Sep 20, 2024

here is a 20 second clip showcasing all the necessary information, as well as an example of the enchant not functioning as intended. please let me know if there is anything else I can provide https://youtu.be/vB2YKx7iNl0

@wizjany
Copy link
Collaborator

wizjany commented Sep 20, 2024

javaw_GvkEcj6axQ.mp4

idea64_LkkrwQ2W9P

@baailey
Copy link
Author

baailey commented Sep 20, 2024

it is caused by block-other-explosions being set to true. i guess the question is, would this be classed as working as intended or would you consider it a bug

@wizjany
Copy link
Collaborator

wizjany commented Sep 20, 2024

if it's a bug it's certainly not a worldguard one. if the server is telling us there's a block explosion (and a sourceless one at that) and you tell WG to prevent them, then it's doing its job.

@EngineHub EngineHub locked as resolved and limited conversation to collaborators Sep 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:invalid This does not describe a request or bug with WorldGuard type:bug Incorrect behavior, not working as intended
Projects
None yet
Development

No branches or pull requests

2 participants