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

Doesn't remember block metadata while editing. #2632

Open
5 tasks done
Zosya1226 opened this issue Sep 24, 2024 · 3 comments
Open
5 tasks done

Doesn't remember block metadata while editing. #2632

Zosya1226 opened this issue Sep 24, 2024 · 3 comments
Labels
status:pending Pending acceptance or closure. status:stale Issue was not confirmed by maintainers type:bug Incorrect behavior, not working as intended

Comments

@Zosya1226
Copy link

WorldEdit Version

7.3.6

Platform Version

paper 1.21.1-52

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

2024-09-24_07 48 13

I don't know how to avoid this block destruction when i //move //cut + paste //copy + paste
Sometime cross type of redstone becomes a dot.

Expected Behavior

All of redstone components are moving with blocks exactly as it copied or moved from "home" position. I use 7.2.9 WE on my 1.17.1 bukkit server, no common issues.

Reproduction Steps

  1. //copy + paste
  2. //cut + paste
  3. //move
    any plot of redstone

Anything Else?

No response

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

This is almost certainly #2516

Copy link

This issue has been automatically marked as stale because it has not been fully confirmed. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added status:stale Issue was not confirmed by maintainers labels Oct 24, 2024
@EngineHub EngineHub deleted a comment from github-actions bot Oct 24, 2024
@EngineHub EngineHub deleted a comment from github-actions bot Oct 24, 2024
@github-actions github-actions bot removed the status:stale Issue was not confirmed by maintainers label Oct 24, 2024
Copy link

This issue has been automatically marked as stale because it has not been fully confirmed. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the status:stale Issue was not confirmed by maintainers label Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:pending Pending acceptance or closure. status:stale Issue was not confirmed by maintainers type:bug Incorrect behavior, not working as intended
Projects
None yet
Development

No branches or pull requests

2 participants