Seems like it's a far too realistic commercial programming simulation. Underspecified inputs and incomplete testing data, with everything breaking in production and being hard to debugI love these kind of games, but Comet 64 level design is broken. In one of the first levels of the game you are supposed to send double entries from an input list to an output list. The listed elements are years. The solution should have been simple enough, but my attempts failed repeatedly. It is really difficult to debug in this game, but after much effort on my part I was able to figure out that my solution failed due to the integer and floating point registers not being able to handle "null" values from the input list.
However, it does not make sense that "null" values should be included in the input list, the game does not give any hints that "null" values will be included in the presentation of the problem, and the visual preview of input values only shows a couple of years. Additionally, my first input list did not include "null", which made it possible to complete the algorithm in one run. This is outright bad puzzle design in one of the first levels of the game, which does not give the best impression. Add to that silly game design choices like forcing the player to add semicolons after each line, and you have a pretty annoying game on your hands that makes you long for the design magic and quality seal of a new Zachtronics game.
Last edited: