I’m going to try to get into the habit of blogging more often, so I figured I’d start it off with talking about how I got into developing LightWalk full-time.
Back in 2013, Nick Alereza (a college friend of mine from Cal Poly) made a prototype of a game, with the intention of using it to get independent study credit for making a level editor. Unsure what to name this game, he called it Hour1 because it was the first hour of his working on this independent study class project. The game was simple: a puzzle platformer where every platform is a laser that you can stand on, bounce on or will kill you. Objective: get to the goal portal. Here’s the rub though, lasers block one another when they intersect, thus creating a maze-like structure. The player is given the ability to block lasers – but given the physics, blocking one laser can cause the entire level to reconfigure.
I liked that concept a lot. Simple, with a lot of opportunity for depth and emergent mechanics. So me being me, I jumped on board to do all peripheral coding and asset work. Make it look and sound good, and provide things like menus and option settings. We would eventually get an artist and composer on board, as well as a voice actor, a marketeer and a few level designers. We really thought this was gonna be the one – our first published game, and the team was doing well.
But as time went on, we added more features and more polish and it became harder and harder to motivate ourselves. We set ourselves a goal of submitting to IndieCade and IGF, which we did, but alas we didn’t get accepted into either competition. We got a cool trailer because of it though:
Not making it into the competitions killed the project for the remaining members. The code seemed unmanageable and the changes recommended by the judges seemed a stretch. A lot of feedback we got was related to the art looking like it was done by different people (which it was) and the story not making sense (which it didn’t, not unless you shotgunned all 4 hours of the game and managed to remember all 3 cutscenes by heart). We had a good set of mechanics and good sense of humor though, so not all bad news.
Real life hit and I got a job working for a big software corp. Motivation to work on Hour1 dwindled even farther. Nick Alereza decided to use the game for his Master’s thesis, which has proven to be something of a curse for his motivation. And thus Hour1 development halted.
I got massively depressed at my day job after about half a year. I yearned to be passionate about something again. I yearned for game development. But as I went around interviewing, I would always hit the question of “What have you published?” Suffice it to say, answering “Nothing, but we got close with this one game called Hour1” led to pretty awkward conversations. So no job offers came through from game dev companies I wanted to work for. Eventually my blood boiled hot enough that I planned to quit my day job and go indie, with the focus being to publish something ASAP, allowing me to use that game for interview credibility. And what better game to attempt to release quickly than Hour1?
Nick and I talked it through. We chose a simpler, more abstract art style that would be possible for me to create on my own (so we sidestep the issue of multiple artists producing inconsistent work). We wanted to feature our composer (Earvin Ramos)’s work more prominently, so we’re planning to theme the game around electronic music concepts. We decided on a set of features that would be needed to polish the game. We picked a story that made more sense: no story at all – per John Romero’s suggestion (he played Hour1 for 20 minutes). The point of Hour1 was never to convey a story, but rather to provide mind bending puzzles – that’s what we’re good at and that’s what we’ll capitalize on. And finally, we agreed on a name that makes way more sense than ‘Hour1’: LightWalk.
So then the day came. I quit my job, took a few weeks to rest, sleep off the nightmares and write to-do lists. The first week or two of my working full-time on Lightwalk were dedicated to converting the project from XNA to MonoGame. My laptop is running Windows 10, on which one cannot develop XNA games. I must say, the conversion process to Monogame was painless with a very low learning curve. All the functionality I wanted was there and working. I guess the open-source community has a little less head-up-ass than big corps do ;P
And here I am now. I’m working on redoing all the art assets, which has been quite the undertaking, and the visual style is very different from Hour1. But seeing the game in full-screen and 1080p feels good. It’s good to be passionate again. Here’s hoping it pushes me/us to finally publish this sucker.