Skip to content

at y=0, //paste & //stack do not place redstone components #2840

Closed as not planned

Description

@atw1020

WorldEdit Version

7.3.16

Platform Version

Fabric 0.17.2

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

Likely a duplicate of #2516, but I have found some additional oddities that others have not noted that could help fix the issue, and I don't have permission to comment on the original post

  1. The issue seems to only occur at height y=0
  2. The number of blocks has some impact, where the issue is more likely for larger numbers of blocks. However, I've seen the issue reproduced when stacking as few as six blocks 2 times (see replication steps)
  3. Horizontal co-ordinates also have some effect on whether the issue shows up. In particular, I've observed that at the co-ordinates 254, 0, -86, but not across the chunk border at 257, 0, -86
  4. The direction you stack the components matters. Not sure what the particular pattern is, but at co-ordinates 0, 0, 0 the issue shows up when stacking north, but not south.
  5. The issue seems only to show up if redstone comparitors make up a certain percentage of the blocks being replaced, something between ⅛ and 1/6

Expected Behavior

//paste & //stack places redstone components the same regardless of co-ordinates

Reproduction Steps

  1. Create a test stucture containing redstone dust, a repeater and a comparitor at 0, 0, 0 facing west
Image
  1. Select the structure using WE, turn north and execute the command "//stack 2"
Image
  1. Observe incorrect behavior
Image

Anything Else?

Other workarounds are mentioned in #2516, but another solution is to ensure that all redstone builds are constructed well above y=0. I've checked all other heights from -62 up to 320 and y=0 is the only height this occurs at.

Activity

  1. atw1020 commented on Oct 11, 2025

    @atw1020
    Author

    Tried using the recommended workaround //reorder multi and even //reorder none, and things got worse. I have issues stacking at any y-level, not just y=0, with these settings. I suggest that anyone else trying to work around this bug leave their settings on //reorder fast. The setup at 0, 0, 0 described above also does not work with these settings, and I started having issues with even simpler stacking commands.

    Here are the steps to reproduce additional bugs that show up with //reorder none and //reorder multi:

    1. Create a test structure at the coordinates specified in the screenshot (two blocks at (33, -38, 17) and (33, -40, 18), with redstone dust on top of each)
    Image
    1. Switch reorder settings to "none" or "multi" (interestingly, this works for fast settings)
    Image
    1. Select the structure using WE and stack 3 times up
    Image
    1. Observe incorrect behavior
    Image
  2. me4502 commented on Oct 12, 2025

    @me4502
    Member

    It's worth noting that as you're on Fabric, if you have Carpet installed (or a handful of other mods) it completely overrides our ability to prevent blocks from breaking. WorldEdit needs to be able to prevent block updates, but those other mods take complete control over the process so that only their systems are allowed to control whether they occur or not

  3. atw1020 commented on Oct 12, 2025

    @atw1020
    Author

    I have no other mods installed

    Image
  4. github-actions commented on Nov 12, 2025

    @github-actions

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:pendingAwaiting triage.status:staleIssue was not triagedtype:bugIncorrect behavior, not working as intended

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions