I think, however, I've found that solution, and like so many things in the last few days, it came with the game's new aesthetic. When I had intended to take a more realistic approach to the game's graphics (and physics), I had tried to encourage sequence breaking through lots of support character dialogue and cut-scenes; break the sequence, I was saying, and you'll find out what really happened in the Colonies. But this approach wasn't particularly compelling.
The support dialogue and mystery story elements seem out of place in the spare, simple world of Seq.Breaker as it exists currently. That's when I started playing with the idea of some kind of silent rival; what if the rival swooped in (in classic villain fashion) and stole whatever you were after once you had done all the hard work for him? And what if you didn't do the hard work-- what if you, well, broke the sequence? He wouldn't be able to do his swooping. And if the player failed to break the sequence, maybe the scene with the rival could impart some kind of information, some hint or clue, as to how they might approach it when trying the mission again.
This all came together in my head in about the time it likely takes you to read this sentence, and the end result is the Ninja:
No comments:
Post a Comment