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

When using the //paste or //stack command, the redstone is inserted incorrectly. #2516

Open
5 tasks done
Xakerors opened this issue Apr 23, 2024 · 3 comments
Open
5 tasks done
Labels
status:accepted Will be fixed / added to WorldEdit, eventually type:bug Incorrect behavior, not working as intended

Comments

@Xakerors
Copy link

WorldEdit Version

7.3.0

Platform Version

Fabric 0.15.10

Confirmations

  • I am using the most recent Minecraft release.
  • I am using a version of WorldEdit 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

Structures with the addition of redstone components are not fully inserted when trying to copy and paste them, or stack
2024-04-24_00 44 01
2024-04-24_00 44 47
2024-04-24_00 44 56
2024-04-24_00 45 18
them.

Expected Behavior

I expected that the structure would be fully installed with the preservation of redstone.

Reproduction Steps

  1. I select an area (two points)
  2. I choose the direction in order to execute the command "//stack"
  3. I'm writing "//stack"
  4. All the blocks were installed as needed, except for redstone.

Anything Else?

I want to say a very important point. If the selection area is affected only by the redstone and nothing superfluous, then it is inserted normally.
2024-04-24_00 58 27
2024-04-24_00 58 44
2024-04-24_00 58 48

@Xakerors Xakerors added status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended labels Apr 23, 2024
@octylFractal
Copy link
Member

Something changed in how redstone is updated, and we need to add an additional hook to prevent block breaking during it. We may shift how block placement is done entirely to avoid surprises like this, which would take longer.

@octylFractal octylFractal added status:accepted Will be fixed / added to WorldEdit, eventually and removed status:pending Pending acceptance or closure. labels Apr 24, 2024
@octylFractal
Copy link
Member

For others finding this issue, this does affect all platforms, as we use the same code to place on all of them.

@octylFractal octylFractal pinned this issue May 14, 2024
@zombachu
Copy link

zombachu commented May 19, 2024

Btw for those looking for a workaround, 7.2 doesn't have this problem if you're able to use it (tested on Paper 1.20.4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:accepted Will be fixed / added to WorldEdit, eventually type:bug Incorrect behavior, not working as intended
Projects
None yet
Development

No branches or pull requests

3 participants