|
Oh hell yeah. Subscribed.
|
# ¿ Feb 23, 2017 14:24 |
|
|
# ¿ May 10, 2024 05:22 |
|
Andrew Plotkin did a fantastic writeup of this game that I will link when you are done.
|
# ¿ Feb 24, 2017 07:13 |
|
SelenicMartian posted:Oh, I will turn it down. This time I reduced it by 10-11dB, next time I'll go with 20. It was definitely ok at the autoduck volume, if that helps.
|
# ¿ Feb 24, 2017 16:32 |
|
SelenicMartian posted:So, what next? Now you tell us why you resigned.
|
# ¿ Mar 7, 2017 18:45 |
|
Domus posted:So the game keeps repeating "no man is an island" over and over, just like the key to escape is the key to escape. But we've yet to see either no man or an island. The village is specifically not on an island, at least in the show. So what does it mean? Keep going long enough in one direction and you'll escape? It appears to be on an island in at least one episode, if I remember correctly.
|
# ¿ Mar 16, 2017 23:11 |
|
Looking at this, keeping security at 100% means no fights. If there's a fight there's a (security)% chance it'll be stopped. Keeping water or food at 100% means no riots. There's a (security/10)% chance of a riot starting IF a random number is higher than either the water or food values, and a (security/10)% chance of security stopping the riot. Those two and terrorism are the only things that can increase deaths, but: no deaths means no water lines are ever blown up. gschmidl fucked around with this message at 08:57 on Apr 9, 2017 |
# ¿ Apr 9, 2017 08:54 |
|
Jabor posted:This seems entirely plausible, in previous plays as things were being decreased it would stop every 10 for an event message. The trick is that it's not just to survive ten events, we have to survive at least ten events and then trigger the end-of-game. I think you can just quit it at that point.
|
# ¿ Apr 9, 2017 08:58 |
|
ManxomeBromide posted:Given what "should" be happening there, I think it might be scanning the keyboard. This might be as simple as picking 9 off the menu. As further evidence of this, 185 is 57 (the ASCII code for '9') + 128 (maybe the top bit = key pressed? It's looping waiting for the value to be at least 128 there for a bit...) According to Apple II docs, PEEK(-16384) gives you the ASCII value of the pressed key + 128, so 9 should indeed do it.
|
# ¿ Apr 9, 2017 09:11 |
|
|
# ¿ May 10, 2024 05:22 |
|
Congratulations, Six. Here's Andrew Plotkin's summary I mentioned I would be posting.
|
# ¿ Apr 23, 2017 17:28 |