The Boy Who Stole The Sun - Devlog #3 - Can't Stop the Movies
Can't Stop the Movies

The Boy Who Stole The Sun – Devlog #3

Guardian Concept © Seth Gorden

Whew! July was rough. The tools update from last time has had some consequences in the clean up phase. While the tool for assembling terrain data was relatively simple to put together, the update to the loading code for maps that use this terrain data breaking a bunch of assumptions from the previous revision. Or rather, it would have been simple except that map data for the game and the editor are slightly different, and I have some work to do to make sure the terrain file loading goes smoothly in all cases.

As a brief aside, I have a little episode from the home life to share. It's part of the journey that things go poorly sometimes, and it's not always code that causes trouble. The problems revolve around getting a new roof put on our house. The positive side is that insurance is covering most of it. The downside is that it took WAY too long to complete the job by any reasonable standard. There were reasons given, and some of them were understandable, but the cumulative effect is that our house was under siege for a whole month. We didn't have access to our driveway or garage due to a giant dumpster parked there. We had some rain leaks due to portions roof being left in unsuitable conditions prior to stormy evenings. The workers often showed up late in the morning, and departed around lunch time or early afternoon. Many days they didn't show up at all. The worker team itself had a lot of arguments, and I'm pretty sure two workers quit as a result of all the yelling. After some calls to the company's owner, they applied some discounts to the project. That was nice, but there were continued communication and reliability problems all the way to the end.

Guardian Concept © Seth Gorden

Suffice it to say, this whole ordeal ended up triggering my anxiety pretty hard in the last week of July. The wife and I had navigated most of the upsets pretty well together in the first couple weeks, but that week was so full of disappointments that I buckled under the pressure and it got the better of me. Work was affected. Doing well again this week, but the recovery time is at least in part due to having support and accountability in place. I'm a pretty high-functioning anxious person, and a lot of the mental game of the condition is under control. But one of the sneakier side-effects is a hesitation that sticks around after these incidents. Which leads to getting stuck on decision making points. However... despite the stress, several important gameplay decisions got made last month... excited to share, and also excited to have a clearer plan for the player progress through the game.

One of the "Aha!" moments was deciding on having a series of guardians for boss encounters. From the early design, I only had one guardian encounter in mind, a giant bear, altered by uncanny magics to guard the Sun Stone which is our MacGuffin for the game. The Guardian at the end. When explaining this creature, and asking about how to mark out major challenges in areas between... my brother (kindly acting as a sounding board for ideas) asked me about the Guardian's origin. I explained that one of our major NPCs had created it. And his response was "If they can create one, they can create several. Just have a bunch of guardians." Seem so obvious  now. But at the time it felt like an epiphany. Of course there could be several. Sometimes when I'm bogged down in tools code, and wrangling things on a micro scale, some of the obvious choices for the macro scale elements can be missed.

Once this was decided, we went to work on figuring out how to make sure guardian encounters would be significant for both gameplay and narrative. The basics are that each guardian will be placed at the entrance to some area of exploration, rather than at the end. The choice to void violence as the primary language of interaction make boss design tricky. I don't think we can avoid violence entirely, but aiming for problem solving as the primary experience. We won't need to teach the player tools and weapons (Zelda-style) to lead up the boss fight at the end. Guardian encounters are instead going to block access to explorable areas. Each one will introduce basic gameplay and navigation concepts needed in the areas ahead, and will include a narrative-affecting choice during or afterward.

Guardian Concept © Seth Gorden

Specifics: each guardian has a power stone that it protects. The stone is not placed in a room. It is rather strapped to the animal itself and feeds power to the animal, distorting it from its natural state. These stones are essentially lesser versions of the Sun Stone we're after. These lesser stones will be necessary to unlock the path up the final mountain. When the stone is removed from a guardian, they will shrivel and be left in a state of suffering. The player can choose to move on from there, running off with the power stone and leaving the animal in such a state. I plan to include some audio of suffering noises (wailing, mewling, etc) that can be heard some distance off to play on the emotions and cue the player that the guardian encounter may not be quite done. They'll be free to ignore it, but I'll set up as much encouragement as possible to get them to investigate further.

Players who remain and explore will discover they can, mercifully or otherwise, kill a defeated guardian. But I wanted to dig into that further to see if it was possible to create a gameplay experience that hinged on the manner or attitude of killing a creature over which the protagonist suddenly has power. It's hard to distill abstracts into gameplay like that. But the idea that surfaced from discussion was the potential of setting the creature at peace before killing it, and that doing so would alter the dialog and story in a few controlled ways. It essentially amounts to an optional side-quest for the completionists. There'll be some backstory and details available to those who figure it out. We talked through several mini-game ideas, including some Ocarina-like song or rhythm elements. But ultimately decided upon some light interactivity and narrative feedback.

The game revolves around the idea of making murky choices without enough information, and letting the player feel their way through the narrative feedback they receive. I'm planning for replay value and I hope each of the paths being offered will have enough ups and downs to be a rich experience no matter what personality the player brings to the game. Easier said than done, but taking it a step at a time. The main thing is that now I have a map of encounters and a layout for the how the player will mark progress.

Posted by Seth Gorden

Comments (0) Trackbacks (0)

No comments yet.

Leave Your Thoughts!

Trackbacks are disabled.