Hoppers stop working if you replace hoppers using //stack
Mario-Radinovic opened this issue ยท 2 comments
WorldEdit Version
7.2.6-beta-02
Platform Version
Fabric 0.11.6
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
If I had hoppers placed and then replace those with new hoppers using //stack command, hopper will just not work (not transfer items) anymore.
Locking/unlocking it doesn't help. As soon as I manually remove stuck hopper and place it again by hand it starts working again.
Bug doesn't happen if I stack same hoppers replacing any other block that is not hopper.
Expected Behavior
Hopper should keep transfering items after being replaced with new hopper using //stack command
Reproduction Steps
- place a chest, hopper sucking items from a chest, and another chest taking items from hopper above
- Select placed chests and hopper
- use //stack forward twice (or place a hopper on the position where new hopper would get pasted by //stack command)
- Put items in newly pasted chest and check the hopper
Anything Else?
I have tested it with both //perf neighbors off and on, same thing happens
Doing it while there are items in top chest doesn't change the result
Have you tried not using an outdated beta? 7.2.6 has been released for a bit.
