Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The "bell is heard 3 times" is telling. We did all 3 steps and only heard a bell at the end of the last step, at which point the eye started rotating in the skull but did not pop out.
I suspect the problem is that the clues are unclear what is "inside the loop" and what is "outside the loop" of what you repeat for each of the numbers and it presents evidence to the player that they were doing it right when they're not. The eye rotated after entering all 3 sets of 3 numbers, each set with a different valve position, and finally using the button at the end. Perhaps the button is intended to be done after each set of 3 numbers before moving the valve again for the next set, and the real bug is we only did step 1 and thought we had done all 3, because the game let us "succeed" at it even when we did it wrong. If it was expecting exactly 1 valve position, 3 numbers, then a button press to do step 1 then it was letting us do a lot more valve positions and numbers and still work for step 1 anyway. What we did was valve position , number, number, number, valve 2 position, number, number, number, valve 3 position, number, number, number, then Button at the end because we thought that's how you do the whole thing, It probably shouldn't let that succeed at finishing step 1 because that sends the signal to the players, "what you did was right because it did something" when it wasn't. If it expects 3 numbers then the button for step 1, and it doesn't fail when you do all 9 numbers before the button, then that doesn't tell the player "that was wrong". Instead it tells the player "you did the whole combination where apparently the end result is that the eye moves for some reason..." It would actually have been better if it had *failed* to get to the end of step 1 with what we did (too many valve positions and too many numbers for step 1).
Until looking at the walkthrough, we didn't realize that "get the eye to rotate in the socket" wasn't the expected end result of all 3 steps. And the walkthrough didn't say that "get the eye to rotate" is just step 1, thus it looked like a bug "we did all 3 steps and the walkthrough says the eye should pop out after all three steps, yet when we did all 3 steps the eye rotated instead of popping out" is what it looked like. The idea that what we had done was end up triggering only step 1 even though we did it wrong was not clear.
It looks like what the code is doing is that once the one valve position and 3 piston numbers are entered for step 1, it ignores any subsequent changes done to the valve and piston between then and the button press. Thus a player who is thinking incorrectly that "I need to do all the valve positions and piston numbers before pressing the button the first time" gets a fake confirmation "that was right" by seeing the skull eye start moving. It wasn't right, but the game makes it look like it was right because it made the skull do something.
Ironically, it would actually be better if the puzzle was LESS forgiving - making those extra valve and piston movements cause a fail of step 1 would have communicated, No, that's not right", rather than what it does now, which is give out a false positive that tricks the player into thinking they've succeeded at all 3 steps so they stop.
We had a hard time making it work when we used mouse-drag to turn the valve wheel.
But when we used mouse-click to move the valve wheel 90 degrees per click, then it worked.
I think the "spin 360 to reset" only worked when done by clicking 4 times, instead of by actually spinning with a mouse drag.
recieved received
dissapearance disappearance
posession possession
premisis premises