Tag Archives: devlog


Regular, meaningful progress is hard to make when you have a full time job and a family. I figured a public blog would help compel me to do it, but it hasn’t worked. So now I am trying to add some structure, and make that public too. I found some open source scrum called Taiga and I setup a backlog and a few sprints of work.
The first sprint, which took place over the past two weeks, was a success –I finished all the things I wanted to. It was about completing a basic set of hero movement content and death, and the (what I thought was a little bit) of code to tie it together. Since I am using 3D models to represent 2D art, to get the character to face different directions it is actually a model swap rather than a sprite swap. In Unity this means switching to a different skeleton and animation controller.
It feels good to queue up a set of tasks to do over two weeks which are a small piece of a bigger puzzle and at the end, you’ve learned something about that puzzle. I totally changed what I was going to work on in the next sprint after move the needle ever so slightly in a different direction and learned just a bit more about what I’m making.

Conversations about cost vs. value add for players

I can’t count the times I have been party to a discussion between programmers and content creators that goes something like this:

Artist: If we do it that way, we’ll have to hard-code the information directly into our content and it will mean we have to create and maintain like four times as many files…

Programmer: If we don’t do it that way, we’ll have to code a whole new system to handle it dynamically and it will cost performance, memory, code maintenance, and bug tail…

Tech Artist: I could write a script that generates the files for us. Everybody wins, right?

Let’s ignore the Tech Artist for now. Both the Artist and the Programmer have valid arguments from their points of view. Each is staring at a potential pile of dirty laundry. If the artist has to maintain four times as many files, then imagine how much beautiful content they aren’t creating instead. If the programmer has to spend time coding and maintaining another system, then imagine how many other feature requests must be rejected…you get the idea.  
The problem with this line of discussion is that it is too focused on how much work one has to do and how that work will reduce the potential cool stuff for players that could be done. An interesting thing happens when you are both the programmer and the artist for the project. Since it is you coding the system or maintaining the files either way, it starts to make very little sense to take either position above as a good reason to do one versus the other.
This image is what brought all of this to mind. To get some trees to show up, I wrote zero code and just added trees to the random list of tiles I’m populating the world with. It turns out that the trees have transparency around the edges. To get it to look right, I could composite the tree and the grass in photoshop and be done with it. But what if I want trees on top of dirt? Then I need two tree images instead of one. What if I want it on grass, dirt, and something else –now I need three. Okay, so what if I composite the tree on top of grass through code? I started thinking about how much work it would be to support tile layers and it was a decent amount of work.  Again, one problem with these lines of thinking is that they are too focused on the cost.  I started thinking instead about whether of these approaches had any bearing on the player experience. If I coded the tile layer solution, that could afford me the ability to remove the trees easily and have the grass remain. If the trees are easily removable, then the player can chop them down, or they can catch fire and burn away. If they are used for cover from projectiles, this could be interesting. Once I began thinking this way, I was much more comfortable thinking about the cost. If I know I never want any of those mechanics, and I am really only going to have 3 types of terrain + trees, then it is an easy choice to just combine them in photoshop.

Ultimately my point in all this is that it is important to consider any potential value adds for a player experience in cases where the discussion to take one approach over another is centered on the costs and the result would look the same either way. You might just discover a fun mechanic or maybe even a differentiating gameplay hook.

Animation test, finally!

So in the last post I covered the easy model creation pipeline I was working on. Since then, I solved the final piece of that puzzle which is to automatically generate the rig. All of that is rather boring so I’ll save it for another day. Today, I want to show the point of all that, which is to animate! I got two animations setup, east idle and east run. Check it out!

I’ll fill out the north, south and west (maybe mirror east?) and then post some more videos.

Easy model creation

In the skeletal animation experiment I created the model by hand, placing one polygon per pixel using an image plane as a template and then manually setting the UVs to match up with the sprite. That was way to tedious and definitely not scalable. I wrote a handy little python function that will take a sprite as input and do all the work for me :-). Check it!

I think I’ll still need to create the “rig” manually. There will be one unique rig per direction, with east/west potentially just being a mirror. After I create one decent quality animation set and I automate the rigging process then I am confident that this will be my pipeline.

Skeletal animation experiment

One of the next things I want to figure out is how I’ll handle the character animations. I’ve been using the tiny dungeon sprites from Oryx Design Lab, and I had been thinking that skeletal animation might help bring them to life in an interesting way. I didn’t quite know how I would do this so I did some research and there are a ton of options to try out, from Creature to Spine2D, to Maya, and even Unity itself supports animation from within the editor. Here is my first test:

I brought the 16×16 sprite into Maya and slapped it onto an image plane, scaling it up 100 times until each pixel was 1 grid unit, and then I made a 1×1 polygon plane for each pixel. I ended up using a planar projection and using the sprite as a texture, but I think it may be more efficient to either use vertex colors or a tiny 1D texture that has the 8 colors the sprite has in it.

This animation is just a simple waving idle, so I want to do another test with more action like a run or an attack. I like where it is going so I want to see if I can take it to the limit as well, with FX and everything. Then I want to see if I can streamline the setup process by automating the manual steps I did to turn the pixels into polygons. Cheers!

Movement and dodging experiment

The game has reached a mini-milestone. All of the parts I need to test movement and dodging projectiles are finished. Like many Roguelike games, each move is a turn and all characters take turns simultaneously, but at different rates. What I wanted to test here is the turn based movement of the Player and the continuous movement of projectiles. The combination of these requires the Player to move in order to dodge.
I’ll be throwing builds into my public Dropbox folder if anyone wants to playtest and give feedback. Next up are the damage system and I want to try another experiment, which is the use of skeletal animation.

Yet unnamed Roguelike

While my wife was at GDC I began work on a Roguelike game in Unity.  I have limited time, so progress has been slow but steady.  I’m currently using art from Oryx Design Lab (http://ift.tt/1iD1s45). I’m close to the point where I can playtest the most basic mechanics.  I’ve definitely suffered from the ‘start a lot of projects that don’t get finished’ problem in the past and I am hoping that keeping a devlog will help push me to ship this game by making my progress public.
Honestly I don’t have a super strong ‘seed’ that everything is growing from.  I am definitely figuring things out as I go.  My current thinking is that the game will have these elements
  1. Movement is turn based like most roguelikes
  2. Projectile movement is continuous, so you’ll have to move to dodge them
  3. I’ll have a pixelated art style, probably 16×16 for most characters and environment tiles, however the characters will use skeletal animation
  4. It will be the inverse of Rogue Legacy in that, you venture outside of a castle into a new environment after each death
  5. There will be weather and survival elements like Unreal World, but less so.  
  6. Your progress is measured in how many days you survive, like in Neo Scavenger
I don’t know much more than that right now.  I’m very close to being able to test #2 from above
This blurb and this image are what sparked the whole thing:
Game takes place across a series of ‘single screen’ battles, al la OG Zelda.
As you move to the edge of the screen, the camera lerps to the next screen
     crazy town idea–it is multiplayer, you get matchmade with players in the next screen
Turn based, roguelike style movement of characters
Projectiles can be dodged in real-time
reverse of rogue legacy–where instead of going into a randomly generated castle, you exit your home into the randomly generated forest
     you only get to keep what you bring back?
     you only get to keep ‘special’ items a la enchanted cave 2
Here is my current todo list
Stay tuned for more updates!