Spy20 Design Diary

So I came across Spycraft 2.0’s Back to Basics. Basically it’s D20 Modern’s base classes redone for Spycraft 2.0. In short it’s what I was trying to do, merge D20M talents with a spy game.

So Spy20 is basically going to be Back to Basics merged with Spycraft Lite with some ideas taken from SWSE and D&D 4e. Twenty pages for classes plus 32 pages for the base rules plus a few pages for premise/setting.

Next to revise the equipment system.

Spycraft Saga Design Diary

So after watching a bunch of Veronica Mars and Alias I got thinking of playing a spy RPG. Back in the day I really enjoyed Spycraft, but it wasn’t perfect and it’s new version went detail heavy … the opposite way I like my games.

What I really would like is a game that had the beat stuff from Spycraft but in a simplier package. Then it occured to me you could use the framework of Star Wars Saga Edition with the details from Spycraft and D20 Modern to build a modern and streamlined system. Why D20 Modern when I’m a hater of that “game”? Simple it has good stuff worth stealing like Talent trees in a bad framework.

So basically I take the bones of Star Wars Saga and drop in the feats, gear and chase system from Spycraft and the Talent trees from D20 Modern. Tweak so it’s more xXx than Tom Clancy and serve with Doritos and Mountain Dew.

Now the heavy lifting. Build classes using SWSE and D20M Talents. Then tweak Spycraft feats. Then tweak Spycraft equipment rules.

Next post, character classes. Wish me luck.

New Template

OK, so after about a year of threatening to redo my template, I broke down and … stole Donna’s template and tweaked it.  It’s barely functional and really more a proof of concept, but it sure beats the default and the other broken templates.

Hopefully I’ll keep tweaking it or else it will stay this way.

Think Big

“Make no little plans. They have no magic to stir men’s blood and probably themselves will not be realized. Make big plans; aim high in hope and work, remembering that a noble, logical diagram once recorded will never die, but long after we are gone will be a living thing, asserting itself with ever-growing insistency. Remember that our sons and grandsons are going to do things that would stagger us. Let your watchword be order and your beacon beauty. Think big.”
—DANIEL BURNHAM, CHICAGO ARCHITECT. (1846-1912)

Microlite Games

I’ve developed an interest in microlite games of late. Well not technically microlite as in one or two pages, but lite RPGs that take less than 10 pages.

Now in order to make a complete game in as few pages you have to give up on a few things. First is setting. Your game has to imply a setting rather than explain it. That’s OK since the big dog D&D already does that. A lot of details also have to be vague since you don’t have the space to explain all the uses for the electronics skill. That means a freer system when playing, but again this is nothing new to people used to (A)D&D. The real task is to boil a game down to it’s essentials and finding simple solutions where more detailed systems could eat up pages.

My interst in lite games is really from a curiousity design stand point and from a practical playing stand point. Can you make a game so small that is still worth playing and why should a game take 200 pages to explain how to play? I’d guess that most RPG players use only a small core of the rules of their favourite game most of which could be summed up in less than 10 pages.

Now to see if I’m right.

The Decade In Review

So let’s look at the past so we can move on to the future.

The high points are the birth of my son, my awesome wife, my cheeky doggy, my daunting mortgage, my first new car and leaving the continental America for the first time in 20 years.

The low points … pretty much the rest of the decade. I kid, but sometimes it feels that way.

Things I want to do in the new year in no particular order:

A) excel at a new job
B) eat less red meat
C) skip empty calories
D) spend more time with family and friends
E) redesign this blog
F)launch my other sites and ideas
G) play more games

Iain.

Android == Fail

OK, I’m going to go out on a limb and be all predicty.  There is a lot of noise about how Google’s Android is about to run rough shod all over the iPhone.  I don’t believe it.  In fact Android will be in about the same place as Windows Mobile in a few years. (That’s the prediction part.)

So why do I think that hundreds of Android phones won’t kill a few iPhones?  (Re-read my question before preceding.)  Android is an operating system that will run on many different combinations of hardware.  There is no guarantee that any two android devices have the same specs and therefore it will hard to develop (killer) apps for Android.  I had a Palm back in the day and when you went to download software there would be a list of devices the software would work on and devices it wouldn’t.  That was by one company who controlled both software and hardware.  It means that a killer app for one Palm often did not run on the other Palms.  And unlike PCs, apps for smart phones don’t have an adaptive OS or device drivers to help them out.

The iPhone is often mistaken as a smartphone.  In actuality, like a Mac it is an experience.  Yes, that sounds a lot like I’ve been drinking the Kool-Aid, but it really is the only way to describe the Apple philosophy.  Apple treats the iPhone as both a personal computer and a console.  The former is illustrated in that some models of iPhone have capabilities that others don’t.  This is mostly because of actual hardware differences in the different iPhones.  But by treating the iPhone as a video game console developers know they have a fixed target to develop for.  They always know the screen resolution and the input method.  There are no questions about what devices the program might end up on.  All iPhones have a minimum base level with a few more options on different models.

Of course this prediction is beased on Apple sticking to the formula it has.  If it creates a iPhone 4G with a higher resolution display then we get into the situation with Palm and start down the same path as Android.  Change too much of the underlying hardware and you fracture your own base.  Luckily there is only so much you can do with an item that is constrained by its own size.

So what about the rumoured iTablet?  It’s not an iPhone in the same way that the iPhone is not a Mac.  The tablet platform may have many things in common with the iPhone (an OS and input methods for instance), but the tablet will have its own App store and ecosystem.  See the way to get away from having multiple devices running the same OS is to differentiate the devices into different categories.  I love my iPhone and I use it for email, browsing, tweeting and even making phone calls, but a tablet would be much better for reading and writing documents.  DocumentsToGo on a 10″ tablet is a viable alternative to a net/notebook.  I can do more real computer stuff on it, but it’s not an iPhone.  Developers will be familiar with programming for the new device, but it will have it’s own base level that all developers will be able to develop for.  Another similar platform, not another device running the same OS.

Iain.

Rainy days and Mondays get me …

Rainy days and Mondays get me down.

New Twilight movie smashed box…

New Twilight movie smashed box office records. Come on, it’s just My Little Pony for the 21st century.

Sitting in Langley. Not Langle…

Sitting in Langley. Not Langley bypass or city, rural Langley. I fear we might be snatched by hillfolk. This toy better be worth it.