8.3

Child of Light Review (Multi-Platform)

Games Reviews
Share Tweet Submit Pin
<em>Child of Light</em> Review (Multi-Platform)

Ubisoft’s DLC, downloadable and hand-held games are some of the few places in major studio gaming where you can play as a scripted non-white-dude character. Child of Light casts you as the young daughter of an Austrian duke who, after the death of her mother and her father’s remarriage, has fallen into a deep slumber.

This happens over the Easter weekend, in case you needed some added significance. Otherwise, it’s fairly standard fairy-tale stuff: young girl, missing mother. Bruno Bettelheim built a career out of analyzing this type of thing.

I mean, it’s also literally a specific fairy tale. Maybe a bit too specific. This girl shares a name with Disney’s Sleeping Beauty. But this Aurora doesn’t lie in her magically-induced coma and wait for someone to kiss her out of it. She ventures through a beautifully-animated 2D world, called Lemuria, teaming up with others, and fighting monsters in JRPG-style turn-based battles. She’s also accompanied by Igniculus (she calls him “Sir Firefly” sometimes), a blue firefly controlled by the right thumbstick or a second player who aids in collecting and combat and puzzle solving through his ability to glow.

Lemuria is a children’s storybook, all hand drawn background and watercolor-washes. While the art really nails the aesthetic, the writing (at least, on a sentence-level) falls short.

Everyone speaks in rhyme. Well, the jester Rubella doesn’t. She (yes, she! there are multiple non-dude characters in this game!) uses a non-rhyming synonym for a word that would complete her couplet, much to the confusion of other characters. They fill in her rhymes.

It feels like it has aims toward poetry—or at least toward the kind of children’s book that uses verse to increase its impact. It stumbles when it comes to meter, though: There’s no rhythm to many of the lines, which is made more apparent during the occasionally-voice-narrated cutscenes. Lines like “for all intents and purposes, Aurora was dead” aren’t delivered as (or seemingly even meant to be) somewhat absurd punchlines or in an affectedly serious Lemony Snicket style.

The game is built on the UbiArt framework, Ubisoft’s 2D engine that we’ve seen in Rayman Origins and its sequel Rayman Legends. The games share a bit of their DNA, too. Rayman collected Lums, which would often burst out of a piece of the background and float in a line, encouraging the player to travel along a certain path. In Child of Light, Aurora and Igniculus can collect “wishes”, blue orbs that appear after being knocked out of glowing bushes. Like in Legends, running into these in the “correct” order (signaled by the change from blue to orange) gives you a bonus. Here, they explode into a cloud of green and purple orbs that refill Aurora’s health and magic meters.

child of light screen.jpg

Like her limbless counterpart, Aurora moves smoothly through her environments: Generally what you expect to happen on screen when you press a button happens. While Aurora’s ability to fly means her exploration is never full of complicated, split-second timing, environmental dangers like giant thorns can cause some pain. But where Rayman Origins and Rayman Legends threw their complexity into the platforming, Child of Light puts it in its combat system.

Portraits of your party and your enemies slide along a bar divided into “Wait” and “Cast” sections. When a portrait reaches the dividing line, an action can occur. These have different Cast times, which affect how long it takes for the portrait to reach the end of the bar. Once that happens, the action occurs. Anyone who is hit by an attack when they’re in the “Cast” portion of the bar causes their attack to be interrupted: They’re knocked part of the way back into the Wait section. The right thumbstick still controls Igniculus . Moving him over an enemy and holding the Glow button slows an enemy’s progress across the Wait-Cast bar. Glowing over a member of your party will slowly heal them (something that Igniculus can do while exploring the world as well). Glowing depletes the Firefly bar, so it can’t be done indefinitely. Battle screens (combat occurs on its own screen, separate from the world around which Aurora flies) have those glowing bushes on them: Here they release a cloud of blue, green and purple spheres to quickly refill firefly, health and magic meters. If the battle goes on long enough, these will recharge and only release blue spheres. Each party member has a variety of offensives and defensive skills. There are elemental alignments that increase or decrease damage, depending.

Using Igniculus’s ability to slow down opponents along with interrupting attacks makes combat a bizarre exercise in time management: it is possible to get through some battles without allowing an opponent to make a single attack. And Igniculus adds a level of spatial importance to the combat that so many other menu-based systems lack. I found that playing solo, I had to keep a mental division between what my left and right thumbs were doing that I haven’t had to engage since last year’s Brothers.

Like I said, it’s complex. And that’s not even getting into swapping party members (only two can be in combat at a time, but they all level up) or the details of their abilities or items. Or the light crafting (small gems called Oculi can be combined into different colors or sizes, which can be put in one of three slots on a party member to grant offensive, defensive, or passive bonuses). Or the skill trees. So many skills in a trio of trees per party member.

You know, it’s not even like the writing on a bigger level is all that bad. The ideas behind the quests are, at the very least, non-standard fantasy fare. Free a town of magic-casting dwarves from a curse that’s turned them all into crows, or help free the economic capital of a town of business-obsessed micefolk (it’s locked in a vault that they can’t open). But when set alongside how well the systems and the art work, the problems with the dialogue are so disappointing.





Brian Taylor doesn’t like skill trees.

ShareTweetSubmitPinMore