Q:Tell us a little about yourself, what are some of your hobbies outside of games?
A:I've always been drawn to the smaller story within the larger tale, which led to an interest in insects. From there I zoomed in even more, learning of microbes and the amazing things that happen at the cellular level.
When I don't have my nose shoved in a scope or a monitor you'll often find me reading sci-fi/horror/fantasy. I love the microcosm of a used-book store, and rarely buy new books; there's something thrillingly random about wandering around inside of a used book store and hoping I find something nifty to read as my sole reading avenue.

Q:What was your inspiration for creating this mod?
A:Rust on an old junked car. I started thinking about what might have led to that car being forgotten. That, combined with a big fat power pylon ruining my view of a sunset, and chapter one started to take shape.

Q:What was the hardest part about the creation process?
A:Getting the anti-material nano bomb trigger to function properly.

Q:Any plans for future projects?
A:Audrey (Chapter Two) will get quite a few more upgrades. Once I'm satisfied with her development I'll start work on Chapter Three; I'd love to give Tiger Headquarters her own tale told before I'm done with the desert.

Q:What was your favorite part about the creation process?
A:I had a great time building Audrey and Leslie. I saved Audrey for 'last', which made building the notes leading up to her revelation all the more fun. Leslie was fun just for a chance to throw out some crazy voice acting and have a good time.

Q:What are some of your favorite games if Fallout 3 isn’t the only game you play?
A:System Shock 2 remains one of my favorite games ever (I did a bit of a small homage to SS2 in my FO3 mod The Mantis Imperative)
Fallout 2 for the joys of turn-based combat and fun exploration
Half Life/2/Portal for sheer immersion value
King's Bounty/Armored Princess for a fantastic re-imagining of the HOMM franchise

Q:Do you have any advice for aspiring mod authors?
A:1) Tutorials: Yes, they're often boring, and yes, they generally help. It's tempting to skim through the content to get to the part where you can build your rocket-launching gorilla on a skateboard mod, but a stable foundation in basic mod environment concepts will help you greatly in figuring out 'How the heck do I do that?' questions down the road.

2) Scope: Don't shoot for the stars! At least not for your first mod. Mod sites are littered with the corpses of grand designs, mods claiming "dozens of new areas! Hundreds of new NPCs! Eighty new unique weapons! Seventy new quests!' now strewn with cobwebs and cast aside. While ambition can be a wonderful thing, seeing a small mod to completion will benefit you and any future projects you undertake greatly. Better to have a fun little mod that takes 10 minutes for a player to finish signed, sealed, and delivered, than a magnum opus 35-hour adventure that... never quite makes it past the planning stage.

3) Expectations: This is especially applicable to adventure mods. Remember the old preaching adage: "For every minute you spend talking, you should spend an hour preparing." Well, the ratio is (usually) worse with mod making. Do not be surprised if the interior area you spent ten hours building/cluttering/tweaking takes the average player three to four minutes to scour from top to bottom.

4) Maintain a cool head: It's gonna happen. There you are, beaming with pride over your latest 80+ hour creation, and someone will say "Kinda boring - not really worth my time.". It's tempting to lash out in your mod's comments page with a face-melting stream of vitriolic rebuttal, but no good will come of it. Even if you present a compelling argument, you're just adding to an unpleasant pile of growing schlep. Doing your best to act professionally and answer questions will help craft an environment where players feel comfortable asking questions and contributing to discussion of your mod.

5) Back up! Most mod-tools are not officially supported by developers and, as such, are even more likely to crash in unpredictable ways than the program they're modifying. Copying your work to another folder (preferably on another drive) at the end of every modding session will give you peace of mind in the event that something goes horribly, terribly wrong. Only once have I had the GECK stage a coup against me, but it went down in flames so spectacularly that not only did it mercilessly destroy the mod I was working on, but its death throes were so violent that that it succeeded in taking out the entire fallout installation with it as well. Five hours of lost work convinced me of the importance of a using a few seconds every session to back up my work.