I’m in, probably, but I’m not going to be able to submit my usual level of terrible game. I’ll be interviewing in Washington Friday, which means WOO PLANE RIDE.

To be fair I could have picked any time when I was scheduling this, but I totally forgot LD was that week. I can only blame myself for this terrible predicament.

So with that in mind, I’ll likely be at the interview, or just getting back to my hotel when the theme is announced (Timezones, woo). Then I’ll be on a plane from 6am sat till 3:30 (Timezones, woo), so I’ll get back and likely pass out from jetlag, giving me the plane ride to sketch out a prototype (for as long as the battery on my laptop lasts) and whatever productivity I can squeeze out of my worn out husk of a sleep deprived body Saturday night/Sunday.

In keeping with tradition, I’ll be developing with:

• Language: C#
• Engine/libs: Flat Red Ball (XNA/.NET4)
• Art (lol): GIMP, Graphicsgale
• Sound: bfxr/burnstudio audiotool/audacity

I’ve found more than one Love user now who uploaded nothing more than their game’s .Love file. Now technically this is fine, since it’s everything needed to run the game AND source! How convenient!

Unless you don’t have the Love game engine installed.

Now in a normal circumstance it might be reasonable to ask someone to install the engine to run your game. However, in the case of Ludum Dare, we have a mere 599 games to play, test, and rate. When I find games that require much more work than “click link and play” or “download, unzip and run”, I find it very tempting to just move on to the next entry.

The fantastic part is that there’s a very easy solution to this! As detailed here, you can easily build executable packages for windows, linux, and mac! These binaries will be easy for users to download and run without being burdened with installing whatever additional software you might have happened to use in your project, making it quick and painless to rate.

Note that this process falls under “Porting” which you can do at any time after the submission window! So go forth my minions and make your entries ready to run!

After breezing through two previous LDs, I felt this time I should push my game design out a bit further, both technologically and in design. I wanted something that I knew would be challenging; not just a game I knew I could complete in the timeframe.

With this in mine, I added some goodies to my game such as an upgrade system, expansive map sets, multiple weapons, and complex enemy types. I looked at parts of games I loved and used them as foundations for various game mechanics. In the end I had a lot more than I could hope to achieve, so i had to trim some fat, and began coding.

At first progress felt a lot slower, dangerously slow compared to previous LDs. I was worried I wouldn’t make the deadline so I trimmed out multiple weapons, shortened the game a bit, and scrapped additional enemy types. I figured I could add these back in later as time allowed.

When I woke up on Sunday I was pretty unhappy with the game. The nature of projectiles made them frustrating when facing Banshees, which were the most common enemy type in the game. I tried nerfing the banshee’s move speed and changing the movement patterns, but nothing really helped.  The game had content and was going well progress wise, but it wasn’t fun. I actually considered throwing in the towel here.

After about an hour of level design to take my mind of gameplay, I had a bit of an epiphany. Prior to LD I had been playing Quake 4, and started drawing connections to my gameplay flaw and my frustrations with Q4′s nailgun. Ultimately the machine gun worked better in Q4 due to not giving Strogg any time to dodge your attacks. While the AI in my game didn’t dodge, the movement patterns were hard to properly lead. So I changed the player’s gun to an instant fire laser.

Everything just clicked at once. Suddenly you could easily hit most targets with minimal issue if you lined up your targets well; and early game energy limits prevent you from just spamming down everything in a quarter of a second. Upgrades made you choose between various gameplay styles. The aiming mechanic of enemies made sure you couldn’t just camp one spot and shoot when everything lined up; but instead rewarded you moving WITH the banshee, constantly leading its shots but still keeping lined up.

After taking some time to balance upgrades and flesh out some levels, I was cutting it a bit close so I ran a final polish run on the level set (though I would have liked to expand it), and submitted.

In the end I have mixed feelings about the final result. The endings aren’t really “proper” endings, and there’s no menu/config/pause/etc. It feels incomplete to me. But despite having some spare time at the end where I could have mocked up some quick simple menus, I was sick of coding it when I submitted; and I felt that a rushed menu would be worse than no menu at all. On the other hand it’s a lot more than I could have done previously, so as a progress indicator it’s great. LD is never about winning to me, it’s about seeing what you can do. Testing your limits and learning new things. Seeing what you’re capable of…. And in that regard it’s been a roaring success.

Play/Rate: http://www.ludumdare.com/compo/ludum-dare-21/?action=rate&uid=3130

I’ll see you nerds in October :3

A lot of XNA users get flak for it because lots of older and simpler video cards won’t run it. A good example of this is Intel HD graphics, which are common on laptops.

Did you know you can fix this? Well you’re about to.

XNA has two profiles. Each profile has different minimum requirements, and as a result different capabilities. If you were developing a retail game you might stop me here and say “But FireSlash, I need shader model 3.0!”. However, in almost all Ludum Dare cases you’re never going to break outside of the XNA Reach profile’s limitations. These limitations are effectively the limits of DirectX 9, which are fairly generous for most games.

The best part of this is that using Reach is very easy; especially if you’re using the XNA content pipeline. Simply right click on your project

Now click properties. You’ll get defaulted to the XNA studio tab (probably, if not it’s a mere click away!) where you can change your profile to Reach. Do this early in your project as it saves you possible issues later with recompiling textures.

Also note that if you use any kind of engine or supporting libraries, you’ll need to adjust the profile there as well. If your engine has compiled textures in HiDef you’ll need to remove these and recompile them for Reach. I suggest doing this before you start as it saves time and rage later.

Going for my third LD entry. So far each one has been progressively easier as I get a better feel for the time constraints and workflow. I feel LD has become a bit of a benchmark on how I’ve grown as programmer. I love it.

The tool list hasn’t changed from last year much

Code: FlatRedBall (C#/XNA 4.0)
Sound effects: Sfxr
Art: GIMP / Corel Draw / GraphicsGale
Music: Audiotool

Target platform will be Windows again. I’m hoping this theme is a bit more focused, as the previous theme was basically a non-theme.

Also for anyone who enjoyed my previous entry, I may be porting it to Windows Phone 7 soon, followed by android.

Sitting here at the 24 hour mark, and things look to be way ahead of schedule.. which is odd.

What we have is a polarity shmup. Most of the vastly different ideas got canned due to balance issues, but I’m still tweaking it a bit. Currently later levels introduce blue ships which can’t be absorbed.

I got a bit ahead of schedule so I’m adding unplanned boss stages in now, which are turning out to be quite fun and very challenging. General polish should be easy to meet and some has already been started. I’ve been going at a fairly relaxed pace too. Overall its a nice change from last year, and makes it far more enjoyable when I’m not frantically looking up documentation every 30 seconds

Participating in my second Ludum Dare! Woo.

Tools:
- FlatRedBall (C#/XNA) for le code
- GraphicsGale + Corel Painter for graphics
- sfxer for sound
- Unsure on audio. Been playing with AutoTracker-C and openMPT, so maybe that.

I learned a ton last time, and hopefully I can release an even better game now that I’m used to the pacing and a bit more familiar with the tools

I’ve spent a lot of time doing game development, but I almost never release stuff. Always base code, game logic, and abandon. So going in I had a bit of a fear of not finishing LD.

Looking at it now, I can safely say LD has been the single most educational thing I’ve done in my entire life as far as game development goes.

Its so easy to fall into the trap of scope creep, or to say “Oh, I can’t work on this yet! I don’t have graphics from the artist!”. But when time is tight and you ARE the artist, it’s easier to start looking at solutions instead of problems; and it’s that line of thinking that keeps you moving.

I’m really looking forward to the next LD. In the mean time, maybe I’ll actually finish some of my other projects for a change of pace.

Obligatory timelapse:

Looking back at the clock, at the start I felt way ahead, by the middle I felt I was behind, and in the end I finished 3 some hours early. Not bad for my first attempt imo.

Next time I’ll challenge myself more, now that I have a much better feel for things and my work flow has improved. However I’ll need to practice on my music and art skills, as they’re severely lacking.

While the event had its stressful moments and sleep deprived coding sessions, it was quite fun, and I look forward for the next one.

Fresh blood! Notch told me to :creeper:

I’ve never done ANYTHING to this level before, so priority will be release ready code, graphics and such can come later if time permits. I’m probably going to take a few days to brush up on my C#/XNA to save precious time googling.

The plan right now:

• Engine: FlatRedBall (Windows XNA)
• Sound: sfxer
• Music: Modplug maybe? Depends on time.
• Graphics: Inkscape or GraphicsGale. Will depend on the theme.