Open eriktorbjorn opened 4 years ago
I managed to set up the scenario I described. I added a debug "SCORE" command so that I could see exactly how much I had recorded:
>SCORE
2051 - 11 (min 10)
2061 - 21 (min 20)
2071 - 15 (min 40)
2081 - 15 (min 14)
When I showed the buffer to Perelman, the reaction was:
Perelman looks up. "PRISM, several of my colleagues and I have finished viewing
the recordings that you made, and everyone there was incredibly disturbed by
them, especially the scenes from 2081. However, there was general agreement that
you didn't show us quite enough from 2071. We'd like to see a progression; the
sentiment was that without the missing link, it's difficult to tell if the
simulations are really valid. Maybe you could collect some more data, make some
more recordings, and then report back to us. Well, I've got to run, but I'll
talk to you later." He leaves the room.
Since I had less than half the needed recordings from 2071, he should have said that I didn't show them "anywhere near enough from 2071", but he instead said I didn't show them "quite enough from 2071" since 15 is more than half of the needed 2081 recordings.
The PARTIAL
routine checks the recording times in the order 2081, 2071, 2061, 2051. Maybe this particular case is the only one that can trigger the bug because 2081 is the only year that requires less recordings than the previous year? If so, it may be enough to reorder the tests to 2071, 2061, 2081, 2051.
But it's such a minor detail, and there's almost no way you'd ever trigger it without cheating...
The
PARTIAL
routine is used when Perelman has looked at your recordings if you've recorded enough from three of the simulations, but not enough from the fourth one. SeeI-RECORDINGS-VIEWED
:Maybe I'm missing something obvious here, but since you only give a recording score to it (e.g.
2051-SCORE
) it can only guess which year you actually meant.The mininum score you need to reach are:
So it seems like it would be possible to come up with a scenario where you've for instance recorded enough from 2051, 2061 and 2081, and your score for 2071 is exactly the same as one of the other three. Then it might think you've reach the halfway mark for 2071 even though it's actually the halfway mark for a different year.
But since the worst that could happen (as far as I can tell) is that the game doesn't make the right decision on whether to print "quite enough" or "anywhere near enough", I don't think it's worth worrying about.