Blog Post: 6 Guitars

I recently went to see "6 Guitars" at the Calgary Fringe Fest. It jumped out at me from the listing because it reminded me of the film "It Might Get Loud" and it's always interesting to explore people's passions.

"6 Guitars" is  a one man show staring Chase Padgett. In it he plays 6 different guitar players, from different styles and backgrounds, including an 80-something year old blues musician, a 20-something rocker, a good 'ol boy country music guitarist, a (slightly neurotic) classical guitarist, a self satisfied jazz guitarist and a folkie. The evening unfolds as a talk given by the six of them explaining their love of guitar and their view of music.

The first thing I noticed about the show was how uncomfortable I still feel interacting in plays. In addition to being uncomfortable with Padgett's various personas interactions with audience (rock on Albert Einstein looking guy) I found the proximity to the actor surprisingly overwhelming. I spent the majority of the show watching the back of the chair of the person sitting in front of me.* While I suppose this reduced my total exposure to the show, it also helped the characters in the show cement themselves in my brain, since it allowed them to not look like the actor.

Over all the show was very enjoyable, well acted, funny and engaging. Its easy to see how it sold out all it's Calgary showings and if it's ever somewhere you get a chance to see it I recommend you to go. Despite all that, I did leave the show feeling somewhat unsatisfied, and it took me a little while to figure out why, but I think I have it more or less nailed down now.

As I mentioned at the beginning of this post, I was attracted to "6 Guitars" because it reminded me of "It Might get Loud." If you haven't seen it, I recommend you do, (with the best available sound system you can find). It details the lives in music of The Edge, Jimmy Page and Jack White and their history and their love of music and ends with what must be one of the most epic jam sessions of all time.

The issue I had with "6 Guitars" (and I realize that it isn't fair to critique a piece for not being something else) was that while each of the six characters were passionate and their love of music was clear, they were only characters and somehow, even if the show was supposed to show us Chase Padgett's passion for music, the message gets muddled. I admit that may not actually be the point of the show, but the other "moral" to take away from it seems to be that "music is good," which I'm certainly not going to argue against.

So in conclusion, "6 Guitars" is a great show, that isn't quite as epic as 3 amazing guitar players jamming in an empty warehouse, but still stands very well

* fortunately the show was put on in the DaDe Lab so the chair was actually really cool. If i ever have a project making enumerated chairs, you'll know what spawned it.

Project 2 : The Ogre Manager

One of my fondest memories is receiving Ogre Battle 64 for my birthday (a long, long time ago). It's gone on to be both one of my favorite games of all time, and also one of the games I have the strongest associations with. Every year when the days get short and the weather gets cold and snowy, my first thought is to put Ogre Battle in the N64* and spend the afternoon pitting my army against the morally ambiguous other guys.

From GameFAQs - user Count Dackula

One of the things that's a little unusual about Ogre Battle, is that while it may look like your usual 90s RPG with swords and magic, you don't actually get to control anything. You take the role of the organizing general, setting up units out of your soldiers and then deploying them to the battle field with orders to take over a strong point or defend a town. Once the game starts they march where you tell them and fight the enemies according to their own internal mechanics and you just get to sit back and watch.**

Your units (in Blue) fight the "Bad" Guys (in Red). You sit and watch.

From GameFAQs - user Storm Shadow

The fun of Ogre Battle comes in putting together all the different character's available to you (some you train up from recruit soldiers, some are given to you by the story and some you pick up from the wild) into units that fight well together, then level them up. Like many strategic rpgs (and as I understand Ogre Battle shares developers with it's cousin series Tactics Ogre which basically spawned the tactical/strategic rpg) the challenge in the game comes from leveling the right units up at the right time. In particular, you have to be careful that a unit has the correct alignment (lawful, neutral or chaotic) and that your units don't become over leveled.

The game tells you what each character's level is, but doesn't give you the total for the unit. As a result I started to keep track for myself, using a sketch book a pencil and my high school Casio not-quite-graphing calculator.

The stats for a character. Sadly I can't find a screen cap of the unit info.

From GameFAQs - user Storm Shadow

After a while I started to realize that the unit I left to defend my base sometimes wasn't strong enough to hold its ground.*** Realizing that I also needed to keep track how much damage each unit was dealing, so that I could always leave the unit most likely to win its fights at home, I started to keep track of that too.

Around this time the Computer Scientist in me started to think that keeping track of this on paper was maybe not the most efficient way to do things. In addition to my mitigating my ability to add calculation errors and screw up putting the numbers down in the right places, I thought it would be nice to be able to graph my progress and maybe keep track of a bit more information. So I started bringing my laptop to game time and keeping track of the statistics in Excel.

One set of unit data for one of my play-throughs.

So, having upgraded myself technologically, I kept on playing. In addition to being able to keep track of each of the characters in a unit, both their level and their attacking strength, I was able to keep track of their alignment (which I could have done before, but now we have a whole spreadsheet to play with right?). However, I wasn't exactly happy with this set up for two different reasons.

The first reason was technical. While the spread sheet kept track of the unit at any point in time (before each mission) it didn't keep the history of the changes. I started to keep a new spread sheet for each mission, but without doing more work than I was really willing to do it meant that I couldn't really graph my progress. Doing this isn't essential to the game or anything very important, but it's still something that would be fun to track.

The other reason was more artistic. As you can see in the screen-shots I've included, there's a very strong esthetic to the game. Everything is very medieval in style and switching from that to the ... polish ... of excel is rather jarring (as you may have noticed) in a way that keeping my information on paper wasn't.

Enter: Ogre Manager, a program I'm creating to solve these two problems. It's not an essential thing, in fact I'd be nearly as happy to go back to tracking all this on paper, but it also struck me as a good chance to practice a whole bunch of things that I've let languish far too much.

The Notes panel from Ogre Manager. It shows who should defend the base, who needs leveling and which units should be grouped together. (But not into in game Legions, those are a terrible idea.)

In short, the vast majority of the programming I do is command-line style stuff and as such I don't get much practice working on GUIs. Ogre Manager seems like a good chance to practice that, in a situation where there's not a huge penalty for not getting everything right. Secondly it would be nice to be able to make a program with a graphical look and feel that matches the game. Whether this is in the form of a look and feel for Java Swing, or Java FX, or custom environment, it will be an adventure trying to put this together. Thirdly this seems like the kind of program that would make an excellent Android app, which is another area in which I'd like to have more experience.

Right now I have development mapped out into 4 phases. The first phase is to finish a Java-standard look and feel program that keeps track of all the information I want to track, which as the screen shots show, has been started. The second phase is to implement graphs and other visualizations of the data. The third phase is to create the Ogre Battlely look and feel and finally the fourth phase is to create the Android app.

Time to go make something.



* In fact, Ogre Battle doesn't really come out of my N64.

** Or clutch the controller in impotent panic as your unit gets wiped off the face of the earth.

*** One of the mechanics of the game is that after a battle is resolved, the losing unit (the one who dealt the least damage) is pushed back on the battle map. The distance it goes is based on how much damage it received. When your base defense unit gets pushed then the enemy can beat you by just walking right into your base.

Project 1 : A Blog

So, while I've already said that this blog is about the projects I'm working on, I also intend to cheat a little and use this as a place where I can write about some of the things I'm thinking about.

For the most part this will include discussion related to the fields of software design, user experience and software development (non of which I am actually an expert on, but I certainly spend a lot of time thinking about these things), but might also expand further into academia or what ever else brings itself into my head.

The blogging here will be a project, this means that I'm only going to undertake it for a certain length of time (one year in this case)* and will, I suppose, have some project posts about the progress of it as well. In addition to simply giving myself a platform, I'd like this project to allow me to spend more time writing, which will hopefully make it a less arduous process for me (and make the reading the writing a more pleasant experience for you).  As part of the project I intend to post one blog post a week, usually late in the day on Wednesdays (Mountain Time).

I do intend to keep the blog posts here in Getting Excited, Making Things, but will tag them all "blogging posts" (as opposed to "project posts") if you wish to avoid them.

Go Make Something!

*I think one of the number one reasons many creative projects fail is that there is no end goal. While not universal, this does lead to a lot of people burning out on their projects leaving the audience (or at least me) unhappy that they're not getting their new content regularly. There's a reason that most television shows have seasons.

Yet another blog!

So I've decided to start a blog. I know, the world is not exactly short on blogs, but I'm doing it anyway. You can't stop me, your only chance is my own powerful lethargy.

That's actually the point of this blog, to combat my natural tendency to sit on my butt not doing things. I want (and I recognize this may just be the most elaborate and time consuming way I've ever found to procrastinate) a place to keep track of all the hundreds of things I want to do and a way to keep myself accountable.

I've been a fan of Wil Wheaton for a while now and I've really enjoyed the ethic that goes into his podcast Radio Free Burrito, the ethic that it's Time to GET EXCITED and MAKE THINGS!

Credit to Petaflopism (under CC-atribution-non-com-share-alike)

So clearly enough it's time for me to get excited and make things. I'm a little afraid both of actually getting things done (which I admit to be an odd phobia, but I think it's true), but I'm going to plow ahead. Over all this blog will be a series of posts about the things that I'm trying to get done organized into different Projects, with posts covering information about the progress of the project and hopefully information about the completion of the project.

Thank you for reading, constructive feedback will always be read and appreciated.

Don't be a dick, Be Good to Each Other, To-Be Continued,

Go Make Something!