It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi,

I've noticed a few general bugs in this version (Windows) but in particular, a blocker on level 8-4 which means it can't be completed.

Specifically, the first time you use the wooden block with gel to open a ? door, you have access to a new teleport which takes you to a new room with a gel'd block too. Except the ? door there remains closed even though the block is in the right place.

Other smaller bugs are glitches which occur when undoing (notoriously hard to code for correctly :)) but you can usually get past those after a few further undos and minor redo.

Hoping to an updated version soon.

Thanks,

Peter
Running into the same problem here. At first I thought it was just another bug caused by the Rewind feature, but the bug occurs even if I don't use Rewind at all during the level. I'm attaching a screenshot to illustrate the problem.
Attachments:
Same problem here. Glad someone else has tested it without using the rewind feature - for some reason throwing blocks into the goo people is buggy for me, and the blocks doesn't always pick up the goo on the side.
Same problem great game so far but i cant complete it until this is fixed. Even looked up on youtube and I'm doing everything right it just wont open.
avatar
Synt_x: Hi,

I've noticed a few general bugs in this version (Windows) but in particular, a blocker on level 8-4 which means it can't be completed.

[...]
I've noticed a couple of glitches, too, but since I haven't gotten to level 8-4 yet, I haven't encountered that myself. Have you emailed gog support about that bug? Or better yet send email to the original developer. They must have provided the binaries to gog and they are the ones who are ultimately responsible for fixing this anyway.

Since there are videos on youtube which clearly show a completable level 8-4 it may be a version issue.

Thank you :)
Fabian
avatar
Synt_x: Hi,

I've noticed a few general bugs in this version (Windows) but in particular, a blocker on level 8-4 which means it can't be completed.

[...]
avatar
fabian.troester: I've noticed a couple of glitches, too, but since I haven't gotten to level 8-4 yet, I haven't encountered that myself. Have you emailed gog support about that bug? Or better yet send email to the original developer. They must have provided the binaries to gog and they are the ones who are ultimately responsible for fixing this anyway.

Since there are videos on youtube which clearly show a completable level 8-4 it may be a version issue.

Thank you :)
Fabian
We've emailed the developer about this issue along with the screenshot in this thread so we hope to hear something soon :)
Confirmed on Mac as well (1.0.0) :
- "disappearing blocks" when rewind is used
- 8-4 "?" wooden block ignored
Same issue here too!
avatar
fabian.troester: I've noticed a couple of glitches, too, but since I haven't gotten to level 8-4 yet, I haven't encountered that myself. Have you emailed gog support about that bug? Or better yet send email to the original developer. They must have provided the binaries to gog and they are the ones who are ultimately responsible for fixing this anyway.

Since there are videos on youtube which clearly show a completable level 8-4 it may be a version issue.

Thank you :)
Fabian
avatar
JudasIscariot: We've emailed the developer about this issue along with the screenshot in this thread so we hope to hear something soon :)
Any news? Otherwise please reimburse the price and I'll purchase once fixed. At the moment it's broken and I don't collect/buy/accept broken games
avatar
Synt_x: ...
Add me to the list, Synt.

I've battered my way to 8-4 as well, and that door won't open for me, either. Like others here, I've watched a video to confirm that my game isn't behaving as expected.
Same here.
Having the same problem
Same problem here.

Linux version.
Looks like this is fixed as of 2.1.0!
avatar
Moozh: Looks like this is fixed as of 2.1.0!
Yup, was fixed in the first update since the error-report.