Bugs
+1
Under review
"Visiting Time" has an alternate 34-move solution that may confuse players
This relies on an input problem available in all generations and builds of Quell (on Android and iOS), but this report's scope is specific to Quell Memento for iOS.
In all puzzles that feature multiple raindrops, play is not restricted to atomically moving a single drop at a time. Indeed, before a drop and other objects finish moving, a skilled player may move one or more other drops in tandem, altering play in ways not designed into the puzzles. This is, for the most part, reasonable: for example, it allows drops caught in infinite loops to remain looping while play continues. The game's expected solutions are otherwise reliant on the player moving only a single drop at a time.
"Visiting Time" presents a problem: it has an obvious alternate solution involving moving a drop to occlude the path of a second moving object (a pair block). This also obtains a "Perfect" of 34. Didactically, this may trick players into thinking they're *expected* to do this, both proactively and retroactively.
I believe that this open-ended input problem should be technically closed if possible. If this is infeasible, then some documentation within the game may be desirable.
In all puzzles that feature multiple raindrops, play is not restricted to atomically moving a single drop at a time. Indeed, before a drop and other objects finish moving, a skilled player may move one or more other drops in tandem, altering play in ways not designed into the puzzles. This is, for the most part, reasonable: for example, it allows drops caught in infinite loops to remain looping while play continues. The game's expected solutions are otherwise reliant on the player moving only a single drop at a time.
"Visiting Time" presents a problem: it has an obvious alternate solution involving moving a drop to occlude the path of a second moving object (a pair block). This also obtains a "Perfect" of 34. Didactically, this may trick players into thinking they're *expected* to do this, both proactively and retroactively.
I believe that this open-ended input problem should be technically closed if possible. If this is infeasible, then some documentation within the game may be desirable.
0
Lewis Boadle 13 years ago
Issue acknowledged! I'll make sure our programmer hears about this and we'll see if there's something that can be done. Thanks for taking time to document it so fully.
+2
Toothless2603 12 years ago
I found a way to do Visiting Time in 33 moves using this technique. I put my solution on the "Which Quell Memento levels have been solved 'better than perfect'?" topic.
Customer support service by UserEcho
