Owner and game developer at Oreganik in Eugene, Oregon. Loves Super Metroid, Celtic Folk Metal, and going to church.
About Ted Brown (twitter: @oreganik)
Ludum Dare 30
Ludum Dare 29
Ludum Dare 28
Ludum Dare 27
Ludum Dare 26
Ludum Dare 25
Ludum Dare 24
Ludum Dare 23
Ted Brown's Trophies
Narrative excellence in LD25
Awarded by Winterblood
on December 19, 2012
Ted Brown's Archive
There have been some amazing games produced — as usual — during this season’s Ludum Dare competition. And usually I don’t bang my own drum. But!
If you want a game that’s easy to play but hard to master, doesn’t take itself seriously, and is basically an old-school arcade game juiced up on mind-altering drugs and a soundtrack that’s so good even I had trouble believing it was made in 72 hours, then you, my friend, want to play Sun God Star Bridge.
Get some. The ending will leave you … er… breathless. Okay, that’s a space pun. I’m sorry. Post is over. Next!
Day zero was the night of the theme announcement. Eight of us sat around and bounced ideas off of each other, trying to identify what people would immediately think of (“one shot,” “one life”) and then move on from there. While wondering about objects that were inherently unique, I thought of the Olympic torch, and rapidly got to a concept where you are a primitive tribesman trying to carry a precious gift of fire through a raining jungle fraught with danger. In fairly little time, I had a 3D capsule moving around terrain tiles in Unity, with fire reflecting off normal maps generated with Crazy Bump. It was a promising start, with the potential for procedurally generated levels.
But something didn’t feel right. At one AM, six hours after the competition had started, I was moving around my world and realized it wasn’t fun. It worked, and it would be challenging once more gameplay was in, but it felt claustrophobic and tense. I think there’s a time and place for that, but if you aim at that target, you have to crush it. Falling short would just result in a comical failure that undercuts itself at every turn.
What broke my momentum completely was the realization that dynamic shadows are a no-go in Unity if using an Orthographic camera. Shadows were critical to the mood, and while I’m capable of creating 3D assets in a weekend, it would soak up far more time than a friendlier sprite-based solution. Tired and emotionally drained, I shut down the computer and left.
On the drive home, I thought about how people would be going through these games like popcorn, and how the games I enjoyed playing were light-hearted and fun. So why the hell was I making a game about a frightened Mayan warrior pounding through the Yucatan in the middle of a night storm?
I had to have an orthographic camera to keep art costs in line, and I wanted a sense of speed and motion. A knowing smile crossed my lips as I realized I would be following one of our medium’s ancient and accepted forms: the platformer.
After four hours of sleep, I returned to the lab, created a new project in Unity, and got to work. By midnight, I had a game with:
- A platforming hero run by physics
- A torch that burns down a stick for fuel (providing a handy in-game meter)
- A realistic fire that dims and eventually dies
- An ability to “blow” on the fire and see it blaze back to life
- Rain that stopped you from blowing on the fire unless you were under shelter
- Terrain that was low friction if a) stone and b) under rain
- Procedurally generated levels that had inputs like total length, number of platforms, gap min/max, height change min/max, enemy placement, rain shelter, big blocks, etc.
- Two enemies
- Game progression (start, level 1, level 2, etc. end)
Here’s a timelapse of all that being put into play. Tomorrow I’ll post the art portion. Thanks for reading!
BONUS FRESH PRINCE DANCING GIF (if you enjoyed the ones in the video)
Reflecting on past successes and, mostly, failures, here are my testaments of game jamming, version 7.
- Go 100%. There’s always something socially fun going on during a game jam. The trade-off to an effervescent social call is a punishing effect on your game project. The project lives forever, while events come and go. If you’re in, commit, and skip the party or campout or tournament or whatever. Shore up social capital beforehand, and recoup losses afterwards.
- Give love. If you are romantically attached or have scions, minions, or children, give them lots of time before and afterwards, because you won’t really interact with them for several days. The project lives forever, but those closest to you are more important.
- Get eight hours of rest. If you sleep for eight hours during the compo, you’ll “only” put in the equivalent of a 40 hour work week. Plus, you’ll perform more consistently.
- Use state machines. There is nothing worse than trawling through pages of switch statements when adding or fixing features. Commit to a state machine early, even if it’s only a handful of states at the start, because then you can expand and collapse easily.
- Mechanics or Story. Pick one, and focus. Trying to blend both at the start is what you do with a full game project, not a jam.
- Avoid learning something new during the jam. Seriously, Ted, didn’t you learn from the flocking fiasco? =)
Because then it’s totally legit to turn Bieber into a Lich. Looking for love. Trying to sing with the voice he traded in for eternal life.
Hey everyone! I’m just dropping by my favorite ol’ game compo site to let you know my solo indie project Chess Heroes is on Steam Greenlight! Please give it your vote, and if it really piques your interest, share it on teh twitterz and facebookin’s! Thank you! =)
This might be my oddest Ludum Dare to date. I started late, and taking sleep into account I’ll only have had 24 hours to create a game. It’s so frustratingly close that I can feel it in my teeth… but deep down I’m worried about crunching the final sprint and not being any closer to A Final Game.
Time to take a break and see if I can plot a course towards the finish line.
Because, seriously, making these little boxes go Bang is quite fun.
All these buttons and bars and light-up indicators actually work, and the big boxes talk to each other, and it’s all in 3D, and I really should have started Friday instead of Saturday afternoon. :/ But I after some sleep, I’m looking forward to tightening the feedback loop between the three devices, then scaling up, adding fail-state scenarios, and giving you ten seconds to figure it out before you’re treated to an explosive ending in full-on cheapo three-dimensional laservision!
The sound effects are pretty decent, too.
This delayed Ludum Dare start (my fifth LD to date!) is brought to you by my independent project, Chess Heroes! Please check out the website and Like it to follow development, and check us out at Seattle SIX on Sunday during PAX!
If you’ve ever been fishing, you probably know the feeling of hooking something big, pulling it to the surface, getting it almost to the shore and… splash! The hook is out and the fish is gone, deep into the weeds, cartoon curse words bubbling up in its wake, and real ones blotting out the sun from the hands holding the rod.
Normally, that’s how I feel after 48 hours of Ludum Dare: like something got away, and I lost whatever I was after. But by stretching this out over seven days, even though the fish got away (like it always seems to do!), I really enjoyed the fight to bring it home.
This was my first compo entry since I officially founded Oreganik LLC as a business. When I started, I tried to balance working all day on one game (Chess Heroes), then coming home, being a good husband and father for a few hours, then working on this game. THAT WAS EXHAUSTING. Then I realized: hey, I make games for a living! I can just do this as my day job! So Thursday and Friday were full dev days, as were Sunday (after waking up deep in the forest) and Monday. All told, this represents about 40 hours of work, and hey! It’s a great foundation! Now I get to see if enough people are excited about what Mobius could have been to see if it’s a candidate for full-time development at a later date.
I also learned some good rules to follow for next time. And, because this is officially “what I do” now, I can take the time to properly write it all down. Stuff like “how to write an extensible transaction model that simplifies functionality and centralizes data.” And then MAKE that model, and then have it in the pocket for the next compo.
Time to wrap things up!
I’m going to think out loud here and write my final task list:
- Finish all menu text
- Finish all upgrade purchases scripts
- Create a health bar for the Hero
- Replace the Red Sky background with a Deep Ocean one
- Implement new gun type: spread
- Implement hero speed and bullet rate increases
- Add Fortress Armor
- Make coffee
- Add Hitbox to Fortress and Hurtflash effect
- Add “bang” graphic for when Flyers and Heroes die
- Make sure Flyers collide with heroes, bullets, turrets
- Add shoot function to Flyers
- Drink coffee
- Set up CPU player to have all towers built at start
- Set up CPU to launch waves at a regular basis
- Set up CPU to make decisions at certain intervals, and either repair or make upgrades
- Title screen
- Game Over screen
- Post builds
- Crash asleep
After waking up early in the Oregon wilderness (because I didn’t get any sleep! LOL) and having a fantastic breakfast, I return to the city, dropped my family off at the county fair, and returned home to lay on my couch.
How long do you think it was before I warmed up a tankard of coffee and got back to work?
NOT LONG AT ALL, MY FRIENDS
I’m putting the finishing touches on upgrades, economy, and in-game menus today. So you’ll be be able to invest resources into getting resources faster, building heroes, building defenses, and repairing damage. After that, I’d love into adding more guns to shooty-shoot with, but there is no opponent at the moment.
Well, there is: it’s a carbon mirror copy of your team, minus the player. Decisions, decisions. Clumsy AI, or giant, evolving boss monster? Or MONSTERS? HMM