I think one major reason most voters dislike When Help Collides is that they expected to see a "text adventure with a coherent story" in a text adventure competition, and nothing else. Which is a fair criticism, I suppose, but ultimately one that is too narrow-minded, because the game was legitimately coded with a text adventure language (Inform, in this case) and offers you a parser to interact with. Moreover, it was not the first competition entry that is not strictly IF. For instance, Andrew Plotkin's Lists and Lists in the 1997 competition is much less IF-y than this game (it was basically an interactive introduction to programming). When Help Collides is not a coherent story. It is a collection of three virtually unrelated mini-games, all of which are amusing and obey their own weird brand of internal logic. I see nothing wrong with that. The only gripes I have with the game are the confusing and unfairly difficult prologue, and the fact that it is virtually impossible to "win", from the way the mini-games are structured. After struggling through the disappointing prologue, I had a blast with all three main sections of the game, and even replayed it a few times to see if I could do better. No, I didn't "get" the story – if there was one to get – and I didn't know what was really going on. But I don't think that is necessarily a bad thing. After all, we don't get upset when we realize there is no backstory to abstract puzzles like Rubik's cube. Like the cube, When Help Collides is a clever and neat puzzler that will entertain you – if you are willing to suspend your convictions on what a "text adventure" should be like. Highly recommended.