The Princess of Vestria

Adapted from an IFCOMP22 Review

This was a fun story divided into 7 chapters, that played out in three phases for me.

The first phase was “the setup”, and I found it to be deftly and confidently executed. The stakes were established efficiently and effectively in very few screens. There was a lot of political, magic/religious and historical context to establish, as well as family background. There were three terrific choices right out of the gate: 1) the political/historical complexity was just right for this size game - specific and intriguing with enough breadth to feel lived in but not so much to drown in details. 2) the information was conveyed using multiple different scenes and interactions rather than a single massive textdump. 3) integrating it with player choices that also established the protagonist’s character. It doesn’t seem like the early choices have far reaching implications (maybe barring one), but they do give a chance to establish the Princess’ voice in the choices the player is making. All in all a very strong start.

The second phase was “the escape and journey”. This was a series of moral and physical peril scenarios (ie series of player choices) that would either establish character or set up potential future stakes or both. By and large I also enjoyed these. The fact that I paused to agonize over options a few times is a good indication that I’m sucked into the stakes of what’s going on. Most of them gave you a chance to flex different dimensions of the Princess’ character and skills. One of them though, involving an abusive street performer, added a new twist that I wasn’t crazy about it.

Prior to this encounter, the choices could result in death, or “luck” loss, but you had a few of those to give and if you didn’t hit a death scene, you got info or character established. With the street performer encounter, the game explicitly warns you if you want “success” you need to navigate a magic sequence of actions. On the one hand, appreciated the warning, make sure to save. On the other it changed the tenor of the game. No longer were you collaborating with the author to establish the princess character and story, or even how much backstory you were exposed to. Instead, you were guessing a puzzle sequence. Further, there were no discernible clues in the choices to inform your guesses. It devolved to trial and error where the focus was on ‘beating’ the scenario, divorced from any prior character or goal choices.

Unfortunately, the last “destination/resolution” phase was more in line with this previous encounter than the first 2/3 of the game. There are timed puzzles that lock out interesting story information. More guess-the-magic sequence encounters. But most disappointingly to me, a final boss fight that had little narrative surprise, nuance or complexity. Through the course of the game, the lore was a key underpinning of the quest, gaining more knowledge of the true vs reported history of the realm. While yes, arguably this lore informed the motivations of the final boss, that final battle didn’t build on or modify or subvert anything that came before. Given how strong the world building had been throughout the game, it felt like a let down.

Ultimately, it leaves me with Sparks of Joy where the first 2/3 of the game were that spark. Its always a shame when the ending is a let down, because that final flavor can overshadow everything that came before. In this case I want to refocus on the first 2/3 that were a true accomplishment of character and world building. Here’s the metaphor I am committing to: its like you get so much pleasure from the sound of two lego blocks clicking together, then you suddenly look up and realize you built a scale model of the Parthenon. Even if you smash the Parthenon after that, that is pretty cool.


Played: 10/10/22
Playtime: 1.75hrs, finished w/ final battle walkthrough
Artistic/Technical rankings: Sparks of Joy/Mostly Seamless
Would Play Again? No, experience seems complete

Artistic scale: Bouncy, Mechanical, Sparks of Joy, Engaging, Transcendent
Technical scale: Unplayable, Intrusive, Notable (Bugginess), Mostly Seamless, Seamless