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

×
I'm playing the Linux package here.
The razors don't do anything to the reapers, they just go through. :/

This is what should happen:
https://www.youtube.com/watch?v=gEg_aA72Jcc

What can I do?
Attachments:
Post edited August 11, 2014 by Klumpen0815
No posts in this topic were marked as the solution yet. If you can help, add your reply
I think the best thing you can do is to write the developers and report that bug. They will probably create a patch to solve the problem.
It's technically still beatable, it's just difficult and more a test of timing and reflex than of puzzle-solving if you don't eliminate the reapers. One trick to getting past reapers is to use the rat as a meat shield. He can absorb one incoming fireball, which gives you a little bit more time to get out of the way.

Hope the devs patch this for you, and good luck if you want to try winning the hard way!
avatar
Klumpen0815: I'm playing the Linux package here.
The razors don't do anything to the reapers, they just go through. :/

This is what should happen:
https://www.youtube.com/watch?v=gEg_aA72Jcc

What can I do?
This bug happened for me too on the Mac version. In my case, I found that if I re-tried the level often enough then sometimes the sawblades would function properly (most of the time they wouldn't).
Post edited August 12, 2014 by 01kipper
I got a response from MagicalTimeBean:

Hi there!

Thanks for alerting me to this bug--it's something that was actually fixed in the most recent version, but apparently GOG doesn't have that yet... I will follow up with them to make sure they have the latest version.

A quick fix for this is to restart the room. What is happening is the invisible damage zones linked to the saws can get squished and destroyed by the moving blocks, just like the reapers. Then it's just the graphic that remains.

Ian
Hopefully we'll get the current version soon.
Today Escape Goat was marked as "updated" on GoG, but the Linux files are still the same (game version 1.0.6).
Was it a mistake? Will the current version reach GoG? Will I be able to complete the game someday?

PS: Where can I find the savestate in the game folder?
Post edited August 20, 2014 by Klumpen0815
avatar
Klumpen0815: Was it a mistake? Will the current version reach GoG? Will I be able to complete the game someday?
Site bug.
Yeah, I have the same bug. As the developer stated exiting and entering the room helped me finally get past the room. I seem to have this bug an a couple of others with the game. Such as my controller being detected as an Xbox controller and messing up my settings, and a weird HDMI glitch that caused me to lose my display during a game session.
avatar
Klumpen0815: Today Escape Goat was marked as "updated" on GoG, but the Linux files are still the same (game version 1.0.6).
Was it a mistake? Will the current version reach GoG? Will I be able to complete the game someday?

PS: Where can I find the savestate in the game folder?
This bug is still present in version 1.0.7.
The Mac version is still 1.0.6, and the bug is still present.
Years later, the issue is still present in the Linux version.
avatar
popperik: Years later, the issue is still present in the Linux version.
Me too.

I figured out a workaround based on the comment from the developers upthread: if you try to only move the blocks when the sawblades are far away from them, the "damage zone" object should get through unscathed. I just managed to beat the level that way.

Would be nice to have a proper fix though :-/
avatar
popperik: Years later, the issue is still present in the Linux version.
avatar
tpgreyknight: Me too.

I figured out a workaround based on the comment from the developers upthread: if you try to only move the blocks when the sawblades are far away from them, the "damage zone" object should get through unscathed. I just managed to beat the level that way.

Would be nice to have a proper fix though :-/
Restarting the level worked for me. Not by dying or by pressing the shortcut key, only when I restarted from the menu. -.-"
avatar
popperik: Restarting the level worked for me. Not by dying or by pressing the shortcut key, only when I restarted from the menu. -.-"
Ah, I was just hammering R to restart, maybe that's why it didn't help me!
wasted so much time on this only to find out this is (still) a bug on os x.