Category Archives: Game Mechanics

Dreamblazers Update: Week of November 30, 2015

It’s a little tough for me to think super clearly right now; I just might have pushed myself a bit too hard last week—Thanksgiving time here in the US and also making some more preparations for my trip later in December— since I seem to have either come down with some kind of sickness for the first time in several years or the fatigue has finally caught up with me.

Fortunately I did have some time to write about what I intend to do with grids, so let’s talk about it anyway!

Grid-based battles in RPGs are typically handled in one of two ways. Probably the most common of these is the Fire Emblem style, also seen in other games like Tactics Ogre:

Fire Emblem Battle

In this style of battle, all the blue characters are in your control and all the red characters are enemies. You can move your characters in any order one at a time and they move within a certain number of square spaces, e.g. the one riding a horse can move farther than the ones on foot. When you’re within range to battle an enemy, heal an ally, etc., you can do that. After you’ve moved everybody, then the computer takes its turn (or “phase”) and also moves its characters in any order one at a time to battle yours.

This is probably more straightforward than I’m making it sound! If you’re on your computer or for some other reason won’t mind streaming video from YouTube, then you could start here around 2:19:49 to get a feel for it:

Fire Emblem is one of my favorite game series, but everything about the design comes with its pros and cons.

Moving each character one at a time is mentally engaging because of the needed strategy to readjust your plan after every one or two moves depending on how battles play out, but it can also feel somewhat tedious physically later in the game when you’ll be moving twelve or more characters in each phase.

During your turns, almost everything goes according to plan and even in cases when you’re rolling dice (e.g. you have a 65% chance to hit the enemy), you’re told upfront what those odds are and you don’t get blindsided by anything, so it has a strong feeling of fairness; on the other hand, since you don’t get blindsided by anything during the moments when you’re in control, the game can feel a little less dynamic compared to other RPGs where your attacks might be interrupted by enemies and you have to adapt.

The system of switching between your phase and the enemy phase is simple in theory and gives you maximum control over coordinating your characters’ movements and attacks, but it also comes at the expense of making sense from an in-universe standpoint. For example, a horse-riding enemy who might theoretically want to run away from your mage, who’s running on foot, can’t get away just because it’s not the rider’s phase, not because of something in the game world that would explain how this happens. Another example is that you can move your character with 3 Speed before your character with 20 Speed.

The bottom line is that there’s a reason this type of grid-based system is reserved for strategy RPGs, emphasis on the “strategy.” Just by the nature of each “player” taking their entire turn at a time, there’s not as much back-and-forth between you and the enemies, but instead you’re switching roles frequently between being the active player and the passive observer.

The second most common way to use a grid in RPGs is the Final Fantasy Tactics style:

Final Fantasy Tactics Battle

Yikes, have those graphics ever aged ungracefully. :P

Anyway, in this setup, characters on both your side and the enemy side act one at a time according to their Speed stats. So it could be that one of your characters moves first, then an enemy, then two of yours in a row, then four enemies in a row, then three of yours, etc.

To a certain degree this makes more sense from an in-universe standpoint than the Fire Emblem style, but it still makes a lot less sense than the traditional Final Fantasy style (like, say, FF through FFX). This is because of the component of movement. Why does the character with 7 Speed get to move 5 entire spaces before the character with 6 Speed gets to move 5 entire spaces? It would be incredibly tedious if they traded off moving only one space at a time until finally the character with 7 Speed gets one extra space at the end, so we know why the developers didn’t design it that way, but that doesn’t explain how it works in the game universe.

In games like the traditional Final Fantasy series or Chrono Trigger, characters act according to their Speed stats, but with no movement in the game to muddy the waters. Of course the character with 7 Speed gets to cast one magic spell before the character with 6 Speed, but that’s all it is… one action. Makes sense. It’s the old spaghetti Western trope of whoever draws the fastest. (Things do get complicated when characters get to take multiple actions per turn later in a game, but more on that perhaps another day. :P)

An upside to the FFT style of system is that there’s more of a give and take. Your plans are always being interrupted or thwarted by enemies getting in your way, which can feel a little more authentic, and you aren’t simply setting up your goals and then moving toward them with no obstacles.

…but a downside is that it can also be a bit overbearing. In a Fire Emblem or Tactics Ogre style of game, at least when it’s your turn it’s really your turn because you get to move all of your characters with full control. In FFT, when it’s your turn, it’s only that individual character’s turn. Even though the battle technically comes across as more realistic and dynamic, in a way it can feel slower to only be offered one character’s action menu at a time.

Both of these previous styles were strategy RPGs and Dreamblazers isn’t a strategy RPG, so let’s look at one more game… This one doesn’t use an explicit grid, but it’s still one of the closest examples I can find to what I have in mind.

Lunar Eternal Blue Battle

Lunar Eternal Blue Battle 2

These are two screenshots of Lunar: Eternal Blue (albeit from different versions of the game), a traditional turn-based RPG. In this style of battle system, you choose actions for all of your characters and the AI chooses actions for all of its characters, then that turn (that round of combat) plays out according to each character’s Speed. If any character on either side dies, gets put to sleep, etc. before they get to take their action, then they lose their opportunity until next turn, so you try to plan in advance, but not too far in advance.

These are the very fundamentals of a turn-based RPG and Lunar basically doesn’t deviate from them except that depending on which enemies you want your character to attack, they’ll move automatically across the battlefield toward whatever they’re attacking and can’t hit it until they’re close enough.

In theory this sounds pretty cool to make close-range fighters and long-range magic users feel more distinct, but in practice it didn’t mean all that much (at least for the melee side of things) because generally both the heroes and enemy monsters would always be rushing toward each other on the relatively small battlefield anyway. You were always close enough to attack, so the only question left was more about keeping Lemina’s delightful self out of harm’s way.

(Or at least that’s what I remember. It’s been over fifteen years since I’ve played the game. :P)

Now that I’ve constructively criticized everything, what am I going to do differently?

Here’s the idea… Let’s take a look at a battlefield:

Dreamblazers - Forest Battle Grid Mockup Part 1

Right now all you’re seeing is the beautiful sprite work from Becca, Alex, and Liz, so let’s instead break it down more mechanically into a grid…

Dreamblazers - Forest Battle Grid Mockup Part 2

Becca’s tiles were specifically built to be 16×16, so that’s the grid I used here, but I’ll figure out how to handle the differently-sized sprites when that time comes. In any case, now you can start to get a feel for how much space there is for our protagonists and these kobolds to move around. But now my idea comes in! Imagine this field is divided into two sides…

Dreamblazers - Forest Battle Grid Mockup Part 3

…where you can only move your characters within the blue area and the AI can only move enemies within the red area. Because characters can move extremely fast in the Dreamblazers universe, I don’t want it to ever be the case that anything is ever “too far away” to be battled even with close-range combat techniques.

So either side can attack anywhere from anywhere. But my thought is that rather than targeting an enemy specifically, you’re targeting that enemy’s current space and a certain range around it depending on your form of attack, e.g. a burst of icy wind covers a wider area than an icicle crashing down from the sky. You can loosely think of this like the board game Battleship, but instead of taking a shot at a single spot, you might take a shot at a 3×3 square or a diamond with a diameter of 5. Here’s a visual illustration:

Dreamblazers - Forest Battle Grid Mockup Part 4

Let’s say you’ve targeted the green, yellow, and pink areas. The Kobold Chief in green hasn’t moved yet and has no chance to avoid the attack because it isn’t able to move its entire body out of all of those spaces. The Kobold Rogue in pink was originally at the center of that rectangle and moved to the left, but because it’s still inside the rectangle, it also gets hit. The Kobold Rogue at the upper right part of the yellow plus used to be in the center of it and already moved up and to the right, but that’s still within range, so it gets hit… and the Kobold Warrior at the bottom of the plus also gets hit!

Please keep in mind that I don’t actually know yet what will be in ORK’s grid feature (assuming we get enough contributors anyway), but this is the gist of the idea I’ve been tossing around in my head. :D

The first benefit is making it feel like it’s possible for characters to narrowly avoid taking a hit. Of course, it’s still possible to use your pure Evasion stat to dodge a hit, but this would add a second method of artful dodging.

The second benefit is making battles feel more awesome—because my intent is that it should be much less likely that your targeted enemy will dodge your attack than that an enemy you didn’t target will also step into range!

Exceptions, of course, include big duel scenarios with top-level warriors involved. Kobolds themselves might be able to transcend light speed in bursts, but they’re not the fastest things around. If you ever just so happen to play as Leaf training to grow stronger with her best friend Celty, who is the fastest character in the game and has the ability to teleport on top of it, then you could certainly expect her to step out of range of your attacks more often than a very large majority of enemies.

But that would be an unusual scenario to play since Celty has never once defeated Leaf in training. Maybe the opposite will happen. Who knows? ;)

Anyway, that’s the gist of the idea. All of this is within the context of a turn-based system, so you can use the first turn to gauge the Speed of each enemy, then plan out your next moves accordingly! (Except when enemies get faster or make you slower, of course…!) Sounds exciting to me and I’m definitely hoping the funding for this goes through so I can see what sorts of magic I can work. :D

Dreamblazers Devlog: Week of December 1, 2014

Last week’s achievements

* Made functional ally-summoning enemies
* Tested out EarthBound-style HP drain and inadvertently figured out how to do Pokémon-style HP bars
* Tested out one-turn-delay priority attacks

Current focus

Touching up various features.

Weekly goals

* Send art feedback for final Winter design
* Integrate animations with ORK
* Make the 2D camera follow the player
* Design layouts for Seaside Slime Cove, Den of Kobolds and the Unicorn, Spring Lake Valley
* Write bestiary flavor text for remaining enemies


Since I’ve been on animation for a while, I jumped back into tweaking the battle system for the past week (aside from visiting family for Thanksgiving). Somewhere in the ether exists an incredible RPG, simply waiting to be created, with priority attacks that change turn order on a one-turn delay, but I feel that the entire game would have to be built around that mechanic with methodical and strategic battle pacing. It’s kind of like Flamberge, a recent Kickstarter strategy RPG where both sides take their turns simultaneously: a very interesting idea that demands an RPG’s full attention and commitment.

(I will say this: if delayed priority was going to make sense in any game, then it might have to be one with physics like mine where everyone has super speed; mechanically it feels sort of like the turn-based version of bullet time.)

And then there’s EarthBound HP drain. Though it’s a great mechanic for adding some real-time flavor to turn-based battles, it turns out that most of the reason why it works is because that series, like its inspiration Dragon Quest, has very easy decision-making. My decision-making is more akin to competitive Pokémon, so rolling HP either puts too much pressure on players if it’s fast or looks silly if it’s slow.

It also conflicts with my Last Stand battle mechanic, where a character at 0 HP loses EP until finally going down (basically like a certain showdown in Final Fantasy V, but active in every boss battle); because they’re similar concepts, Last Stand gets lost in the shuffle if HP also drains that way under normal conditions. I still love the idea of HP drain, but like with delayed priority, an RPG needs to be built around it. The good news is that now I know how to do justice to Pokémon HP bars!

That brings me to the bigger success of the week: enemies can summon allies now! They’ll mainly come in two varieties of summoning multiple fragile enemies or single strong ones, but a certain puzzle-esque “boss” also has her own spin on the idea. I didn’t keep many ideas from 1999-2001-era Me without major tweaking—not even my magnum opus boss battle—but that one’s staying mostly unchanged. =)

Anyway, of the first continents’ enemies, Kobold Chiefs are the best at summoning because they can give party-wide stat boosts to whatever they summon. Kobold Rogues used to outshine them since they could (and usually do) blind the player party, but now there’s real choice in deciding whether to go after Chiefs or Rogues first. And worse yet are the Chiefs who have tamed Greatwolves. Greatwolves only call more of their pack when they’re weak, so one might try to leave them alone, but their stats are almost as good as party members, they can be buffed by Chiefs too, and they can pin party members to take away their turns and feast on them for massive HP recovery like those cannibalistic hydras in the final dungeon of Chrono Trigger.

Ahhh… If it isn’t obvious, this is the stuff I love talking about in these updates. ♥ If I had any good business sense then maybe I’d find somebody and pay them to figure out all the animation stuff and create maps while I do what I like, but I do appreciate knowing what is and isn’t difficult in this process. So back to that I go!

One last note:

It’s a crazy thing to find yourself singing along to a piece of music when you’ve never heard it before, but I actually have heard it before. : D Going back to things from an earlier era that I’ve thrown away, the story of my RPG’s 2001 version opened with the heroine wondering whether people dream of adventure for a reason and launching into a solo musical number about loving her steady life but still wanting more.

I was 16 and so the lyrics are mostly embarrassing and I’m not posting them now—except for the ending. I haven’t thought of that song in years upon years, but the first time I heard 0:20 of that Pokémon Omega Ruby and Alpha Sapphire theme, the two repeated choruses came rushing back to me:

And I think I will find—no, I’ll find out, I know
What awaits me if I just move on

There is loving and living and so much I’ll never know
Until I’m out exploring what’s beyond
And so very soon, I’m sure, I am going to find
What awaits me if I just move on

The bold part has almost the same cadence as the Pokémon piece except that it pauses before “no” instead of before “me”; the notes and scale of the first line in particular are exactly what I had in mind way back when. <3 It also fits even better with the “And so very soon, I’m sure” line other than having one fewer note. Sometimes I write lyrics for pre-existing game songs for fun, but this might be the one and only time where things happened in reverse. =P

Dreamblazers Devlog: Week of May 26, 2014

Last week’s achievements

* Minor menu fixes
* New “status effects”: Battle Cry, Expert Evasion, Focused Aim, Heart Rally, Hypercelerate, Light Poise, Reckless Abandon, a dozen variations of Speed modifiers, and ten more related to attacks/abilities/magic listed below with a (*)
* Minor fixes to traditional status effects
* Adjusted damage formulas
* New equipment for Tango, Evelyn, and Telia: Grand Guard, Charming Cap, Traveler’s Cloak, Black Pants (I’ll figure out a real name later), Traveler’s Boots, Brave Belt, Lilty Lute, Archer Half-Gloves, Three-Quarter T-Shirt, Sunshine Shorts, Bold Boots, Archer Core Plate, Brave Bandana, Battle Band, Lightweight Leotard, Telia’s Shirt (see Black Pants), Bruiser Gloves, Dragon Dares, Bruiser Boots
* Changed party to Tango, Telia, and Lucky
* New enemies (in terms of stats and names only): Impini, Archweaver, Gigarat, Greatwolf, Griffinaire, Harpilure, Impedi, Impega, Kobold Chief, Kobold Rogue, Kobold Warrior, Norian Raider, Ogre, Orc Mage, Orc Outcast, Slimary, Slugwall, Troll Warrior, Vivavines, Wyvern
* New attacks/abilities/magic (in terms of pure gameplay functionality only): Accelerate, Artful Combo, Battle Cry, Binding Vines(*), Body Slam, Captive Piledriver, Cling, Corkscrew Stab, Crushing Punch, Dark Force Fist, Diving Slash, Double Smash, Double Whip, Earthen Shield(*), Fireball, Fire Wall, Flame Spray, Flare Spark, Freezing Wave(*), Fury Gale(*), Giga Bite, Great Tremor, Half-Shield(*), Inferno, Javelin Throw, Light Flash(*), Mega Bite, Mega Fang, Mega Slash(*), Mighty Charge(*), Mirage Attack(*), Muck Shot, Needle Storm, Noble Hammer(*), Poison Drops

Current focus

Balancing and testing enemies and enemy groups.

Weekly goals

* Send in art feedback for everything that comes in
* Finish creating moves used by overworld enemies of Miharu (the first continent) and assign all the enemies to learn their appropriate moves
* Assign battle AI to at least 25% of all Miharu overworld enemies
* Put together enemy groups for the Miharu overworld
* Test a range of player party attacks against various early-game enemy groups and vice versa


It’s amazing how much more productive I get when I’m doing what I really care about: putting down all the groundwork to start watching numbers fly around in battles.

…or so I say, but honestly, the impressiveness of the above list compared to some of my previous weeks is mostly an illusion. It took ages to get my basic menu layout right too, but “made a menu layout” will never sound as cool as “made 35 attacks and 20 enemies” even if it took longer. Still, illusion or not, it feels so much better making gameplay than UI layouts. =)

More of the Miharu enemies’ moves are in place now than not. Once they’re all set up, the enemies just have to learn their moves, use them in balanced and appropriate patterns, and join forces to start battling my test party. Excitement ahead!

Dreamblazers Devlog: Week of April 21, 2014

Last week’s achievements

* Primarily damage formula testing
* Simplified energy attacks concept

Current focus


Sample stuff

Pretty glorious.

Weekly goals

* Send in art feedback for everything
* Continue ironing out damage formula balance


Thought of the week:

I’d extend it to not only projects, but components of projects. As I implemented moves in battles, one of the first steps was setting up damage formulas. No problem, thought I; I already know what my damage formulas are, so I only need to add them in.

Little fine-tuning here and there, but things were going great! I picked eleven reasonably diverse characters and matched them against their own stats to test. All the calculations seemed fine, so hey, cool! Just as a final check and to have a reference lying around in a spreadsheet, I’d match them against each other—

Uh-oh. This quickly revealed that energy attacks were too powerful. They’re meant to be powerful because they bypass defenses, not because they’re inherently four times better than physical or magical attacks. I had modeled my damage formulas after the Pokémon series because there’s no RPG I’m more familiar with, but I had gone overboard with my changes for energy attacks.

Days of testing later, you see the spreadsheet above! Even now I’m not confident that I’ve settled on a final formula, but it’s infinitely better off than before. Continuing to plug away!

Dreamblazers Devlog: Week of March 3, 2014

Last week’s achievements

* Restructured some hidden stats in a more logical manner
* Set up various aspects of the equipment system
* Preliminarily finalized stats for 201 (yes, 201) fashion-based “status effects”
* Implemented ~40 of those status effects

Current focus

The equipment system followed by battles.

Weekly goals

* Finish off implementation of the remaining fashion effects and test all of them
* Write flavor text for at least 60% of the fashion effects
* Begin testing battles: damage formulas, battle text, etc.
* Order new computer


Even though—no, because it’s fully optional for the player, my fashion system ranks high as one of my favorite ideas. At best guess I’d say I thought of it in late 2012 or early 2013, but in any case, it’s certainly my newest large-scale idea.

One uncommon element of Dreamblazers that I’ve had in mind since at least 2010 is that equipment never becomes irrelevant; even starting equipment can be used until the end of the game. Like so many of my ideas, this was inspired by Pokémon (with a huge hat tip to The World Ends With You). The average player simply blasts through the game with their favorites, but a competitive player like me will reset twenty times until that Bulbasaur from Professor Sycamore has the right nature.

I aimed to appeal to both. A casual player never needs to look at a character’s outfit—and yes, I’m calling my equipment screen the “Outfit” screen to stress this point. The serious player, though, might look at Astrid, see that all of her stats are great but none are exceptional, and give away her Trailblazer Tunic, Agility Anklet, and Enchanted Earrings to, respectively, Power-centered, Speed-centered, and Magic Power-centered characters.

Could I do more, though? Could I create a middle ground between ignoring outfits and having the most intense optimization experience since Monster Hunter? Could an equipment screen be… fun? Maybe so! Each piece of clothing has at least one theme, like Cool or Playful, and piling on similar clothing gives the character a theme and boosts her Style stat. If you give her two or more themes, some have natural synergy, such as Sporty + Swimmer or Girly Girl + Princess, while others oppose each other, like Innocent + Military or Everyday + Formal, increasing or decreasing her Style.

In the end I sifted through 433 theme combos and wound up with 201 ways for players to change their Style. My hope is that seeing status effect names like “Disco Knight” or “Ribbons, Lace, Angry Face” or “Sparkles and Swag” pop up as you change clothes will be as fun as opening the menu in Dragon Quest IX and seeing what myriad of new titles Stella would shower on you.