Not something I’d replay, but it makes you think.

But yeah, I see why many people would not like the game!

The only enjoyable sequence (for me) was the spaceman clock scenario, but I felt that it missed some opportunities to make the gameplay fun. Obviously I didn’t understand whatever underlying meaning there was (if any), but it would have been more interesting if launching off of the pieces were to push said pieces towards something (like the hole in the center).

Since when did Indy Game devleopers decide that the best way to be “Indy” was to be nearly incomprehensible and incredibly irritating? It reminds me of that period in every cinema student’s life when they film a naked hot chick eating raw meat and it all turns out to be some bizarre last sequence dreamed up in the milliseconds left in a man’s life as he blows his own brains out… Bleh…

What I find interesting is that, by chance, I find this to be a more poignant and significant ending to the game. I certainly do not know the true “meaning” behind the game or if there is even any literal meaning to be taken out of the abstract elements, but it almost felt as if the 3rd area was a baby starting to be born. Time is ticking. Me, being the abortionist, has to do a few things before time is up to abort the baby. Suddenly, the program halts and asks you if you want to Abort the program or Ignore the error. Ignoring does nothing… aborting sends you back to your desktop.

Obviously I read way to much into this, but seriously I sat there stunned for a moment when this happened, sure that this was all on purpose. A missed opportunity perhaps?

Very different ending screen, etc

In Part 3, I suspect I took to long to move on and the game throws up a fake crash dialog, asking you if you want to ignore or abort the program (However, it threw up the lines of code that it apparently crashed on, so maybe this is legit… the abort term is what got me for obvious reasons). If you say “ignore” the problem, the background colors would change for a frame and the dialog would stay up. I figured this was the ending of the game the first time. In case this IS an actual bug, I doubt it’s OS related, but I am under Vista 64 for some ungodly reason.

I don’t have time to confirm this tonight, but maybe someone else can. What happens if you just sit at the 3rd part – it probably too me a good 5 minutes the first time, if not slightly longer? When it “crashed” for me, I was on the last of the orb things and near the middle of the sphere (I had not jumped off).

I will say that the circle part took me a LONG time to complete. Maybe there’s some sort of timer here?

Once I beat it, a screen came up that made it seem like an exception was thrown and then asked me if I wanted to ignore the error or abort the program.