This repository was archived by the owner on Sep 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Block updates dont seem to register. #12
Comments
Issue #11: |
I have also found that if you spam the command that pastes or sets blocks, it will sometimes actually stay there and work. |
So that can be a temporary workaround. Just an unreliable one though. |
Muqsit
added a commit
that referenced
this issue
Apr 29, 2019
This seems to be fixed in the above commit. Currently, it hasn't been merged to the master branch but you can test it. Here's a |
@Muqsit Error: Not Found |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using //set 0 or //set the update is registered visually, but when you place a block (in the case of using //set 0) the blocks (that you just removed) reappear on each side of the block that you just placed. And when filling an area, breaking a block will cause the blocks around it to disappear. Attempting to place a block to fill the area that just disappeared causes the block you placed to not place at all and the blocks around that area that you tried to place it in to disappear too.
The text was updated successfully, but these errors were encountered: