Here are a coupla features that went in a while back, but I think are pretty cool.
Combat Lab is a stage where we can control both sides, both heroes and monsters. This is useful for iterating on combat, and generally makes our work easier.
Here it is showing off the variety of heroes we're generating.
The Character Sheet is a pretty simple affair, but really helpful for debugging game content. You can see, for example, where your stats are coming from, what history lines, aspects or gear contributes to each one.
You can review the history of each character (which will grow as you play) and see how each line affects the hero.
And you can inspect gear. This is where we've hooked up our gear cheats so that we can test out all the new gear we're implementing!
...So yup! I think this tooling (some of which will grow up into player-facing UI) is going to be crucial as we embark upon our first real content pass. Exciting!
I'm starting in on some mini suites of concept pieces for monsters in the game. It's a way to work out material without worrying too much about the implementation - later, I can go back to these materials, pick them apart, and put them back together differently. It's almost like starting with a puzzle that is all put together and then taking it apart and sorting the pieces as a final result. Anyway, I thought it would be interesting to follow the progress of a piece and share my process for it here.
My first sheet of scribbles is pretty typical for me - I'll break down what is happening below.
(note to self: light pencil marks don't scan very well)
At the start of projects inspired by existing material, I like to establish rules. It can be something as loose as a picture or as detailed as an instrumentation list and acceptable time signatures. Anything that I don't want to contradict. Some composers call them "constraints".
I got my rules from three places - one, reading a great descriptive document by Doug about the Thrixl origins/culture/behavior and how they have been perceived by the people of the Yondering Lands; two, Annie's inspiring artwork; and three, Elise's incredible bank of Thrixl noises, all the way from first pass to current assets. This is a lot of material, and I wanted to distill it down into something a little more bite-size and focused for myself. I put together a list of words, which you can see at the top. It's a bit of a mish-mash of words about the Thrixl themselves and the sounds they make:
These are my rules. I use them as inspiration. I can go wherever I want after that, but I am constantly referring back to them, checking to see if what I'm writing is really in line with what I wanted to express, or if I'm veering too far off path. If I get stuck, I pick one and run with it. Once in a while I find that my rules don't really work out and I start over, but I have gotten pretty good at rule-making over time, I think. Mostly now when I change things I find myself crossing items out, making the list smaller and more focused. This one is much longer than usual. Most likely I'll be separating some things out into unifying aspects and rules that apply only to specific movements of the suite.
After rules comes one of my favorite parts - an idea dump. I get things down as quickly as I can and then move onto the next thing. I don't think much about development or how things will or won't work together (although sometimes I think they might, and I draw arrows and scribble stuff about it - I try not to work out the particulars at this point or see if I'm right or wrong). For example, you can see above a phrase I wrote "Add lush harmony? Romantic port[ato]s, etc.". These are particulars to work out later. Right now I don't bother because #1 a lot of this will never get used and #2 the key is absolutely to dump as much as possible as fast as possible. It's like collecting a random assortment of Lego pieces that get assembled later into some unknown construction.
Often I don't write melodies or even melodic fragments - sometimes it's just a gesture - like "wide 1/2 step vibrato", or "Bernard Herrmann/Stravinsky-esque [downbow retakes]". Lots of composers use this, but the thing that was in my head at first was some stuff from the Psycho soundtrack (Herrmann) or Rite of Spring (Stravinsky). Oddly enough what comes into my head more often as I continue to work is a small part of "Mars" from Holst's The Planets. But that fits in with the "cosmic" rule so, fair game ;)
Start at 2:11 - I fail at embedding with a start time
There's quite a bit of Stravinsky in my idea dump, actually, although I didn't realize it at the time. Those sixteenth notes on the sixth staff are strongly reminiscent of this bit of "Ritual of the Ancients" (also from Rite of Spring). I suppose it's not surprising, since Stravinsky is one of my favorite composers, Rite of Spring is one of my favorite works, and both left a huge impression on the collective psyche of every composer and orchestrator in the 100 years since (I swear to you - you can find Stravinsky or Holst in like 95% of film scores today*).
In an idea dump, everything goes, especially the dumb stuff. This is something I kindof wish someone had told me, but I'm proud of having figured out for myself - if you get the stupid thing that you hate down on paper, it stops inhibiting you. Otherwise, it'll be there knocking on the back of your brain and getting your whiny self-doubt voice's attention, and then they'll just be having a conversation while you get frustrated and distracted. Sometimes when I get blocked I will purposefully write the dumbest, most derivative idea I can, and laugh at it. It gets the creative juices flowing.
I usually try to do at least three idea dumps; this is the first. Sometimes I'll do as many as five. I purposely try to veer away from the direction the first one took when I do the second one. If I have more directions to try, I do more dumps. Then the last one tends to be a natural amalgamation of and progression from whatever stuck with me out of previous dumps. It helps me refine my direction and also results in material that is not obviously derivative. Usually the first dump is almost flat-out stealing - not on purpose, but that's how my brain works. It's grabbing at touchstones. Many times I'm stealing from myself as well as other composers, both of which are evident here (those wide half-step vibratos? Classic creepy Candy). But throughout all of this, the rules remain constant.
Lastly, you can see up in the top left corner an idea for the movements of the suite - "Awakening, The Hunt, Control". The titles will almost certainly change, but I'm feeling pretty good about the ideas themselves. An ambient-ish first movement, composed mostly of gestures, that represents something within the realm of Thrixl dreaming (After all, they want peace - they just don't see it the same way we do). The second movement is about collecting their slaves; the process of getting someone (or a bunch of someones) under their control. Lastly, the implementation of a Thrixl will. I think three movements should do a good job of capturing everything I want for the Thrixl, but if anybody has ideas on what else is important about them, I'd love to hear about it :)
Thanks for reading thus far! As I move forward things will be more show and less tell.
*I have not fact-checked this but seriously, I dare you to listen for it
Work is progressing well. We've made some changes to combat, with the goal of keeping it simple, strategic, and focused on the characters. By way of simplification, Heroism was confusing, so we removed it. Then we added a pair of rules that encourage careful positioning of your heroes. Walling: when a hero is standing directly adjacent (not diagonal) to an ally, she gets +1 armor. Flanking: every attack on a unit that is at a 90-degree-or-more angle to a previous attack this turn is considered flanking and is guaranteed to hit.
Walling encourages heroes to stand close together, and flanking encourages them to split up. We think this tension is going to be interesting. To make it easier to think about, we've added in-world feedback during the move interaction. So as you hover over a square, you will see who you will be walling with, which enemies you can attack from that square, and which you can flank. Hot sauce.
Another big change is that we've removed randomness from hero weapon damage. There's still a chance for the attack to miss, but with flanking it's possible to mitigate that significantly. We think that making hero performance more predictable will encourage players to make more complicated plans.
To reintroduce some variation, we've added weapon and armor types, and weapon wield, which is how light/heavy the weapon is.
Wield affects hit chance by interacting with the monster's block and dodge stat. Heavy weapons are easy to dodge but hard to block. Light weapons are easy to block but hard to dodge. So, depending on the enemy's defense, a light or heavy will be preferable. Armor Type affects hit chance and damage. Certain enemies will be rigid, or slippery, or tough, and weapons will be classified as thrusting, bashing, and hacking. An attack can have advantage, or disadvantage, or be neutral.
Together, these rules should add variation without relying on randomness. We think it will be satisfying to pull out that ultra heavy mace against the rigid blocker, but the intention is more to add flavor, not to make the heroes useless if they bring the wrong weapons.
Instead of crits, we have stunts. Stunting now has a variable effect on the enemy, depending on the enemy type. These follow the theme of the enemy and should add some nice flavor and strategic depth. Here are a couple of examples:
Gorgon Animal -> Confusion: The seed of corruption is momentarily disrupted, and the animal wanders aimlessly on its next turn.
Thrixl -> Feedback: The being loses all interfusions and takes one damage for each interfusion lost.
So, a stunt against a gorgon animal means you can safely ignore that creature, because its next turn will be harmless. On the other hand, many thrixl rely on interfusions for defense and control, so a stunt presents a perfect opportunity to focus down an otherwise tough foe, or disrupt the battlefield in other ways.
Certain weapons and skills will give bonuses to your stunt chance, and we think it will be interesting to build some characters for stunt chance instead of for straight damage. Unlike crit, it's not simply higher damage variance. Instead, choosing to build for stunt chance is a tradeoff between damage and tactical opportunities.
So, those are the big combat changes. Next time maybe I will to talk about where we are with character development. Lots of progress there too!
What we're probably going to do is get these first versions of the Thrixl into the game without waiting for me to spend time detailing them or building in any customization. The reasons for this are twofold:
1.) We don't know what kind of combat mechanics we're going to want for these guys yet. So when we do figure that out, there will probably be art tweaks so that you can vaguely tell how an enemy will fight just by looking at them. For instance, Wormy up there is probably your bruiser melee unit, Two-Head might spit magical acid from its belly, and maybe the Roach-Wizard does the psychic attacks.
2.) Getting basic versions of the different "races" of enemies into the game quickly makes it waaay easier for our sound designer to get started on enemy sounds. If you know ahead of time how you want to differentiate Thrixl sounds (skitter hiss!) from Morthagi sounds (clink clank bellow!), I have to imagine that's a big plus.
Next will be Morthagi, then probably a few forest spirits that we'd like to try out some in-mission extra gameplay stuff with.
We've finished a UI Pass on the game. Everything has a new look and feel, based on a paper metaphor. The UI now scales depending on resolution, which is nice on its own and is a step towards supporting retina. I think brings us close to beta quality for UI and HUD art. Which makes it by far the most finished aspect of the game.:-p
Characters now face eachother when fighting, and face the direction they're walking (but still cheat to the camera.) And we have some demo visual effects present for combat, which you can barely make out here:
(It's hard to screen grab them and it's too loud here to make a video right now sry)
This is possible because we've integrated Spine for character animation, which lets us add in arbitrary visual effects and get a lot more advanced with animation. Here's a test in the tool where we separate the head piece and add facial expressions to see what kind of emotions we can communicate:
We've got audio in the pipeline now too, which I'm eager to show off as soon as it's ready. So, in total, I'm feeling real good about the game's skeleton, and we're talking more and more about how to add content. Onward to Alpha!
Our grouchy tree-dwelling lizardfolk are finally getting a real, built-out art pass so that they can start showing up in the game.* We want the drauven to feel like individuals even when their "class" stays recognizable, so what you don't see here is that things like feathers, horns, masks, and outfit details are all broken/layered out. That way, we can mix and match them. Between that, size tweaks, and slight color tinting, hopefully all the Grunts coming at you won't look like complete clones, but will still be distinguishable from say, Priests. (The big label that says "Drauven Grunt" above its head will also help. Probably.)
You may notice that almost all of them are clenching a fist. They're JUST THAT ANGRY ALL THE TIME. Nah actually, that's where weapons will go. Those haven't been drawn yet. Probably spears and clubs will be their go-tos, since they won't have much metal, except for what they loot off of their enemies. Maybe one brute will be carrying the Ancient Sword of So-And-So, and you get to win it back.
Drauven are probably the most humanoid enemies in the game. They definitely have a society, they have values, and you may even be able to talk to them. If we throw in scope-creeping design shenanigans like "You can make a decision to negotiate with these guys instead of massacring them," Drauven will be strong candidates for that sort of thing.
*- Once I actually break out all the assets, somebody designs their specific abilities, and Nate's list of "Stuff to Implement That's Way More Important Right Now" gets shorter.
So Thrixl are another type of enemy that we're hoping to have scuttling through the Yondering Lands. They're the least fleshed-out of our enemy types but can be summed up right now as "telepathic magic-using insect-dragons."
Side-note: "giant insects" have always been one of my least favorite types of enemies in games, not because I find them particularly creepy, but because they're usually kind of boring and unrelatable. So I'm hoping we can combine these guys with dragons (who are way cooler, but we didn't want dragons overtly in the game's universe) and mages/mind-controllers.
They may weave webs of magic in which they catch prey, or they may use magic the way normal animals would use venom. They may be more interested in eating your soul/energy than eating your body. I have a feeling they're going to be the enemy where we can throw all the abilities that might not fit anywhere else: mind control, dropping from the ceiling to ambush you, some "area-of-effect" type attacks, various magical debuffs.
I'm not sure yet whether they can talk, or plan, or whether they have any kind of society. Maybe they do creepy things like broadcast "hunches" in order to lure you into a trap, thinking another adventurer is in trouble.
I also have very little idea about what their environments look like, though I really want to avoid "they live in holes in the ground" because ugggh drawing a bunch of dirt and rocks is not my idea of a good time. Right now I'm leaning towards mountains or ancient ruins. Ruins might make sense because a.) there could be leftover magical energy there from the previous inhabitants, and b.) ruins and their treasure draw lots of hapless, squishy adventurers with very yummy souls.
The quickest way to make progress on an environment is to post a mockup and say it was "authoritative." You and your colleague will promptly sit down afterward and discuss all the things you want to change.
The first thing we want start addressing is an issue we're having where the 2D art doesn't feel quite "intentional" enough. We don't want it to feel like the 2D art is standing in for 3D art, shuffling its feet and avoiding eye contact. And so, we're looking for ways to play up the "paper diorama" idea.
One of the things we're trying is having the non-character stuff on the map actually look folded over, like cutouts that are being propped up. I'm also continuing to mess around in this vein—simpler shapes, looking like paper cutouts—with the set pieces in the background, though I'm not sure if it's improving things or not. (I would appreciate any thoughts people have on this, comparing it to the background in the mockup from the previous post!)
I'm trying the same thing in the village too, along with another change:
We enjoy the shapes of the cottages, and we realized that there was a lot of vertical space that we could take advantage of in the village. I think adding the roof to the sides (that face the camera) helps you understand what kind of place you're actually in. Again, because we're not doing real 3D art, you end up with an empty space where the top plane of the roof would be. But between the fixed camera and embracing the paper-construction feel, I think it's worth it.
So then, once a hero goes inside a house (or if you zoom/pan to an appropriate spot?):
We switch to a cut-away version of the front wall, revealing the inside. (I'm keen on adding fireplaces to the inside versions of the walls.)
Oh also remind me to draw bearskin rugs that can go on the floor.
In the rare pockets of time that I drag my carcass in front of the Wacom these days, I've been working to get mockups together for other environments, in the vein of the Gorgon lair mockup from a while ago.
These help us figure out things like, "What happens at the edge of the map?" "How do we keep the background from getting too busy?" "What has outlines vs. what doesn't?"
These aren't quite production-level yet:
I didn't extend the map-edge treatment.
There will be a secondary floor texture in the forest, the way there is in the village, so that the ground can fade between them and look better.
Maybe we'll need to do something different with those fading-out house walls.
The background set pieces are mostly flat, blocked-in vectors, since I wanted to make sure they worked at all before taking the time to texture and detail them. I learned that I will need WAY less detail than I thought I was going to, and I count that as a bonus.
I'm sure there are other things I'm forgetting.
But they'll help Nate have a visual target to shoot for when creating atmospheric effects and whatever algorithms create out the backgrounds, and they help me build out an actual asset list for environments, as opposed to "I dunno, I guess it'll need trees or something." Asset lists are my life raft in a sea of vague indiscipline.
Next up, I'll probably try to make a version of the village that's under attack & partially ruined/on fire, or a Drauven forest treehouse, or a differently-colored version of the forest (magical twilighty?) featuring some more prominent ruins. These will all require a lot more drawing... sigh.
My last few months have been about infrastructure. I know that doesn't make for the best blog posts but I also want to record it because, well, it's important. We're getting ready to shovel tons of content onto this game, and the frame needs to be strong enough to support it all.
That means getting confident in the various systems that run the game. So one thing I did was eliminate several of the campaign-specific systems by merging them with the mission systems. This was a huge success: now there is one way of doing things, and it works everywhere.
The downside was that this gutted all of the campaign content I had developed, and so I needed to spend some time putting those systems back together under the new regime. That's basically done too.
Then, I ran into the problem that a lot of my code was difficult to reach. Specifically, code that controls conflicts in the campaign, mission resolutions, that sort of thing. Since I can only access that code (normally) by playing the game for a few minutes, it's very difficult to iterate on that code.
That is not acceptable. Now, I'm a happy-go-lucky sort of programmer, most of the time. I think it's ok to make mistakes and to iterate, and that well, not everything needs 100% test coverage. BUT I do strongly believe that if you can't see your code running, you're not done. And Legacy is at a point where I can't easily see all my code, so, therefore, I can't make easy progress.
So I booted up an integration test framework, using Cucumber for java. It runs the game server and a headless client, and the idea is that it should be able to access all of the non-ui behavior of the game with a series of scenarios, like this:
Scenario: Player can start a mission scenario Given I am logged in And I am not in a game When I select the first mission scenario solo Then I should enter the mission And I should get a welcome message with lots of visible entities
I'm kinda excited. On the one hand, anything that takes me away from forward progress toward a playable game is suspicious. On the other hand, as a one-man shop without a QA team, I just can't afford to spend hours and hours of my time on manual regression. This is the right thing to do.
It doesn't have to taste great to be good for you. :-)
Have we talked about Morthagi much? They're basically the "clockwork undead," created a long time ago by Mortificers. Mixing bone with machinery and adding a little pinch of (magic? love? saffron?), you get a servant who draws on the energy of its former lives and never tires or ages.
Which isn't to say they can't be destroyed. I mean, that's why your heroes are here, let's be honest. But perhaps many of them long outlived their creators and now guard ruins or old labyrinths.
I can't imagine they'll be happy to see you, and they'll make that known with acid, fire, crossbows, pointy bits, or a big ol' dragonskull handshake. There will also probably be nefarious plots based around them, depending on your playthrough.
I've been working on developing an "authoritative" mockup for the Gorgon lairs, which means:
a.) Making a lot of practical decisions about each part of the environment (how do we treat the edge of the map? How wide is that edge? Do we have walls? Doors? How many layers of background will there be? What happens below the floor?). These give Nate something to shoot for when he actually starts making all these things happen.
b.) Figuring out a lot about the enemies themselves—e.g. what are these Gorgons up to anyway? What sorts of things are in their lairs? What materials do they use? How detailed/carved out is the space? What design motifs are here?
c.) Getting the environment to feel unified. Picking a color scheme, having consistent shapes, making the important parts pop out and the unimportant parts recede, keeping it interesting but not too busy, all that art director stuff.
Turns out! Art director stuff is scary, and is not my default state. My default state is wandering willy nilly across styles day by day. I was offered a promotion to an art direction role at a job once; I turned it down. So this whole environment-design thing has been a learning experience for me (by "learning experience," I mean, "over a dozen iterations of this particular picture and more crying than you might think").
We're getting closer though. Next step is to create art that Nate can put into a map, and we'll see how it feels & update/add from there. Interspersed with that, I'll probably start in on some other environments (forest, ruins, other types of lairs) and see if I can then get those to feel different, but like they live in the same game as this one.
The new rig is in and working. I think it looks really good. It's a lot more flexible than what we had before (and a lot more work for Annie, too!). It lets us make really unique and (in my opinion) charismatic heroes, which is a major goal. Here's a video that shows off some of the features.