Friday, March 31, 2017

Comics

I'm excited about this.

We've been working on a new way to present stories to the player, and we've decided to go with a comic format. The visual style of our generated characters is very "illustrated" and I think they look right at home in comic panels.



The major challenge has been to build a tool that allows us to create this comic presentation quickly, while being sensitive to localization, generated content, and dynamic writing. Challenge number one is what to do if the text is too long to fit. The solution is that each panel has a Text Overflow Strategy, that defines what to do if the text doesn't fit. The default strategy is to insert another, identical panel, with the remaining text. So here's what an event looks like if it has no special processing:


It's not the prettiest thing, but it's not broken, either, and that's key. The next major challenge is how to specify panels in a way that's flexible, concise, and accessible to writers and artists. I decided that since it's intimately bound up with the text of an event, the panel specification needs to live with the localization lines themselves. I settled in on a little homebrew panel tag format. It's a bit custom but the nice thing is that it's very concise, easy to read and easy to learn. Here's what that looks like in the editor.


 But, the panel format is not terribly discoverable, so we also let you click on a panel in order to change everything about it. This will then write the panel spec back out to the localization line. You can change everything about a panel using this editor.


So, we're approaching a place where we can quickly convert an event from a prose format to a comic format. It's taken a lot of work to get here, but it's already having a big impact on how we write events, and I think this comic format will end up on the of most recognizable aspects of our game.


I like it. It's pretty.


Wednesday, March 29, 2017

Hero of the Week: Elmlow

The Hero of the Week feature may not happen every week! It's a fun way to dig our heroes and history. What you're looking at: A pane of our character sheet shows the history a character has accrued. All characters are born with three lines of history, separated into origin, anecdote, and history. We'll experiment with composition, as well as tune the writing, over the course of development. In any case, this is a sample of a character you might get a chance to grow, whose story you can cultivate and bring arc and closure to.  




Elmlow wasn't born.

Not if you asked her. And if you didn't ask, well she'd say nothing at all.

Her heart rose and fell on a current of time rather than circumstance.

Some full moons, she was found shivering by the water in her underclothes. And she would turn and whisper, with damp eyes: "I'm cold."

Friday, March 24, 2017

Progress Update: Inertia

There are certainly times when production on Legacy feels like pedaling uphill in a low gear. There's so much ground to cover, and how busy or tired we feel often belies how slow our progress, how inching our ascent.

There are other times when inertia starts working in our favor. We crest a hill, and can shift up a gear or two. We feel we're involved in momentous things, we fly down on the thrill of our own weight. 

The latest lengthy and involved pass on History Lines is finished. With these lines will come hooks, and hooks will feed into everything that we're doing with narrative. I hope I'm not wrong, but, when I look around...

This feels a little like a hilltop.

It does for me, anyway, on the Writing and Design Bicycle. (Me. ME!)

Our design is largely set, or setting. Our systems feel mostly sound and in place, at least theoretically. While the spooky side of the process (the code and engineering stuff Nate ritually sacrifices fingers of his soul to) may not have reached the hilltop yet, our narrative mechanics appear to be there. And that means? 

Downhill. Into the forest of content. Content is coming, and it will come fast and thick. It won't be easy work, but it will be sure work, effective, player-facing, powerful. Revision will remain important, but there is a direct line to freedom there through the trees.

Excited to pelt towards alpha, and watch this long vision take shape. You'll see more snapshots, as the content zooms in. Let's tell stories, folks!



Wednesday, March 22, 2017

Revision

Developer stories will be more personal accounts of working on the game, that aren't necessarily bound to any of the technical aspects. Being creators doesn't make us different from others, it makes us the same. These are logs of aspiration.

There's something in the act of revision that makes me whole.

Revision is a sanitary act. Mop the floor, scrub the mold away, touch all surfaces for dust. Decide where no one's likely to look, and let the dust there be. Because it's neat to have dust somewhere. It's quaint and secret. Secrets jig inside.

I think we are called to revision by our best selves.

You can be a coward for days. You can stretch it out to months, or even years if you have long ideas. Be a coward until your creative courage makes it impossible. Then revise. You can choose to be kind to yourself until the truth becomes so blatant you feel the need to wipe your face. You can come to it tenderly or forcefully, with reluctance or fervor. But you'll come to it, and you'll fall in love again. With yourself.

You'll love yourself more by revising. You'll forgive yourself for making revision possible. There's something in the act of revision.

It's an enigma taste. If regret made you proud. If melancholy could spark in your fingers. If you know what it's like to want something you own. That's the sensation of revising.

For me.

Open-me wants to know what it's like for others. Greedy-me doesn't.

I've been working on revision across the game's history, our presentation materials, and most of everything I've written for it. I'm also working on revising a book right now. It's awful and extraordinary fun pain. 


Friday, March 17, 2017

Viewers and Editors and Validators

Oh my. I've broken my own rule.

The rule is to prefer Viewers to Editors. There's this temptation that I have, I don't know about anyone else here but I have it, to go and build a Tool. In your head, the Tool will be Very Useful and will save you lots of work, and so it will be a Good Use of your Time.

[Danger: programmer talk ahead!]

It's a trap, because if you pick a sane data format, making a tool that's better than your IDE's text editor is a ton of effort, and if you're not careful when you build it, the tool will break every time you change your data format. Bad bad bad.

Better to make a viewer, and just update the view immediately as the data changes, so you get your instant feedback. That'll get you pretty damn far. So that's my rule. Prefer Viewers to Editors.

But then, there comes a time when your data format stops changing so much, and editing huge json files stops feeling like such a swell use of your time. In particular, looking up source code in order to figure out how to edit the huge json files starts to feel pretty crappy.

Maybe, you think, maybe it would be cool if someone else could edit this data, and I could go back to programming. And then before you know it you've gone and built an editor.


What have I done to myself. Anyway this monstrosity is the Content Editor. It can edit effects and aspects, which are the bulk of the data that goes into the game. It uses reflection with optional custom handling, which makes it moderately flexible. So it shouldn't break too badly when things change, and I can build custom workflows for particular use cases. I'm a bit proud of the inline editors with custom validation and dynamic suggestions:


It was honestly a lot of work. Maybe too much. But either way, this is the tool that we'll be using to write and edit the game data from here on in. It's already a lot nicer than a bunch of huge json files, so it's too late to turn back :-P

But not all the data in the game is covered by the editor yet, so I also made this validator. This is actually just a GUI wrapper for the command line validator that I've been using inside my IDE. But now people other than me can edit data files, and get instant feedback about their edits.


In my career, I've been a UI programmer more than I've been a game programmer, really, and I take a fair amount of pride in my ability to make a good UI. But good lord, that pride becomes a burden when you're building tools like this. It actually takes a prodigious amount of work to make a production-quality ui for a tool. Go figure. (This stuff here isn't what I'd call production quality, it's only as much as I could justify to myself.)

Anyway we have fun. And check out that perforce integration button, eh?

Maybe next time I'll talk about what happens when you press Ctrl+1. Oh oh OR, we can have another infrastructure post!

Friday, March 10, 2017

Progress Update: Hero History

I am a pretentious word-cow. Sorry. But I'd like to tell you that I tend to think of Legacy as story-crafting software.

This doesn't mean it will help you come up with the plot for your breakout novel, or that you can use it to create a new world or idea.

This does mean that, within the game's finite creation-space, players have the chance to tell unique stories based on generated characters and narrative content that is both directly expressed and implied. This is its own source of fun, intended to layer over the game-mechanics (which are hopefully fun as well) to make this rewarding game-lasagna that you can enjoy in the moment and carry memory of beyond the digital world.

It's important to me that the creation-space in Legacy is as wide and various as reasonably possible. I hope to achieve a scope to fit any given player's vision, even as that vision might vary from day to day. The jumping off point for that, at least in my view, will be hero history.

Hero history, made up of multiple "history lines," was always a way to impose concrete narrative into each character, give them origins, stories, and motivations.

Here is what that has looked like, following a couple passes, and up to the current moment.

Tilly Cope has a specific story that gives the player hints about her character, her personality, her ambitions. If you look in the Aspects sidebar, you see that history is bound to stat-adjustments, which will affect the character at a mechanical level.

Much of what I have been occupied with over the past month or two has been refining this system. Refining means a couple of things, here. It means integrating the system more directly with other systems, such as combat, events, relationships, narrative-content. It also means improving the writing, attempting to remove generated inconsistencies of character, and working to create more specificity to match characters' personalities. Lastly, I'd add that an important component of the task is just increasing the sheer number and variety of lines a hero receives.

And. I'm almost. Done.

Here's a screen capture of the work I'm looking at, and adding to, day by day.

First column denotes the type of line, which places it in history (mote stands for motivation); second column is the line content itself, which draws on personality traits of a generated character to often add flavor to a given line; third column is tags associated with the line; fourth column is tags with which the line is incompatible (a way to cull cases of inconsistency where two lines say conflicting things about a character); fifth column denotes a primary-stat boost; additional columns give story-role (personality) boosts and state the hook that the line applies.

It's a relatively simple data-table, but represents a lot of cringing and backspacing (see also: writing things) and some fairly important material in the narrative aspect of the game.

There will always be more words to fix and wonky gibberish, because. Well, because I'm writing this stuff, and I'm a bit of a word-cow, whatever that might be, and also quite pretentious. The exciting part about completing this initial history-dump is that it should give us a clear indication of how character personalities come off, and what sorts of adjustments or provisions may be needed to ensure they are impactful while not becoming intrusive or obnoxious. That being a vital feature of our story-telling model, it's important to get it in, and get it running.

Additionally, new history implementation will put hooks in place, which will open up the potential implementation of relationships, and hook quests, as well as providing a key interaction with events. Events themselves will go into serious production relatively soon, and this is a big component of being able to interact with those in a meaningful way, and thus being able to test and assure quality.

TL;DR - Character history is getting a huge overhaul, and narrative content will be ramping up. I'm freakin' out.

P.S. Apologies for the fuzzy graphics. The important impression for you to take from these graphics is 'That looks like some words about things.' 

Wednesday, March 8, 2017

Regular Updates

Hello, friends and visitors! (And foes, I guess, if you're there.) I'm Douglas Austin, designer, writer, and now digital mouthpiece for a years-in-the-making little game with the working title of 'Legacy.'

I haven't posted much in the past. However, for better or worse, that's about to change. Over the coming months, we're going to be closing in on an Alpha-version of our game. This. Is. Exciting!

I mean it's exciting for us, at least.

As we finalize design and content, we'll have tons to share, from notes on production-progress that will come each Friday, to stories from the inside each Wednesday that will tend to center on what a lonely-beautiful-crushing-freeing-humiliating-empowering experience it is to make a game, and the specific issues and features we find ourselves struggling with. I will take the lead on most of this content, with Nate and I alternating on Friday progress-reports. Nate will continue to offer his view from the spooky and/or technical side. Other team-members will hopefully jump in from time to time, to give everyone a break from my obnoxious and self-conscious style...!

But mostly, there might be a lot of me :3

In the coming weeks, we anticipate another piece of scheduled content to show for Mondays. 'Hero of the Week' will be a casual glimpse at characters generated using the current game-build. We hope this will be a fun way to start imagining the stories you'll be able to tell when you get the chance to play and create!

Anyway, that's all for now. See you Friday for a look at history-generation and the evolution of our hooks and stories system!