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

Bug: Grolden Chambers: A block stops being recognised as block #22

Open
wisprabbit opened this issue Feb 8, 2022 · 0 comments
Open

Comments

@wisprabbit
Copy link

wisprabbit commented Feb 8, 2022

Reported by Muftwin. In Muftwin's playthrough of Grolden Chambers, an A block became inactive, and was treated as a step rather than a pushable block.

Muftwin's video: https://streamable.com/457u13

Unfortunately, it's not known how to reproduce this, and Muftwin doesn't know what they did to cause this to happen.

Muftwin later discovered another method of creating what they call "ghost blocks", which is recorded in detail with reproducible steps in issue #25. In light of this later bug, Muftwin suggests:

"the groldy is primed to push the block as long as you are still in line on the next turn, but you broke the block. now the groldy is pushing nothing, so when the next block falls into place its a ghost because... ehh.
considering that i end up on the block when i do the bug i must be climbing and therefore its the same bug? the differences are interesting, but the essence is the same you end up pushing a block that isn't there."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant