With several 15mm sci-fi armies now painted up, my focus has started to shift towards finding and/or writing some rules to actually use them in tabletop games.
15mm sci-fi armies on my painting table |
My internet searching didn't turn up any 15mm sci-fi systems that really appealed to me. Stargrunt or Tomorrow's War work at 15mm, but I'm not a fan of those. Epic: Armageddon, while intended for 6mm, would probably work at 15mm. But while Epic is an extremely good system (one of my favorites) I already play it a lot, so I kind of want to use something else just for variety. I looked at a couple of homebrew systems people had shared on the internet. Most of them looked decent enough, but none really jumped out and grabbed my interest.
In the end I've landed exactly where I started - writing a sci-fi adaptation of the Flames of War / Team Yankee system, which I'm referring to as Sierra Foxtrot.
(If I'm being honest with myself the internet searching for 15mm scale systems may have been a waste of time, since this was what I had in mind from the beginning. Even just the way I based up the models was deliberately styled on FoW / TY units.)
Now the core Flames of War / Team Yankee system is (IMO) very good, so at least initially I'm not going to change much. They do use a simple IGO-YGO turn structure (versus many games I've been playing recently that use forms of alternating unit activation). But there's nothing wrong with simple IGO-YGO, so I'm going to stick with it. Really the main thing needed (apart from the huge task of writing, and especially balancing the army lists) is not so much changes as additions - writing up special rules for various sci-fi specific situations. Things like force-fields, giant creatures/mechs that might take multiple hits, teleportation, vertol or grav vehicles, and all these sorts of things.
The first special rule I'm going to take a crack at writing up (since I have the tokens made up for them) is force-fields...
Malroid Scorp-mechs with 3 shields |
Serpent Nest-Queen with 5 shield tokens |
No comments:
Post a Comment