As regular readers of the blog may know, my Rogue Trader FATE game recently featured a Bloodletter daemon of Khorne (the blog entry where I discuss statting this bad boy is available here for anyone who is interested); so, now that the weekend has finished and the week has settled in like an unwelcome lump of concrete and I reflect on the game session, how did the Bloodletter work?
Overall I think it worked quite well, given that this is the first real hand to hand combat that I have run in the game since switching to FATE it ran quickly and relatively smoothly being resolved in a few minutes rather than the hours that combat can take with some systems; you don’t really get the same level of ‘crunch’ that you get with more detailed systems (although I have instituted weapon rules (as defined in my Rogue Trader hack) in my game) but i’ll quite happily sacrifice crunch for a game that doesn’t become needlessly bogged down in the minutiae of combat. There were, however, a couple of minor issues that cropped up with the Bloodletter that I think are worth bearing in mind for future combats and that I thought i’d share in this blog post.
- More Stress levels required
The initial three stress levels that I apportioned for the Bloodletter were nowhere near enough and would have resulted in the daemon being overcome in the very first round (without getting to land a blow); I think this is because of the increased ‘damage’ caused by the players weapons. During the game I had to add another three stress levels onto the antagonists total in order to make it any sort of challenge.
Another thing that I have started doing with these NPCs (mainly because they do not have any consequence boxes that can be used to soak stress) is ignoring the rule (for NPCs only) that only a single stress box can be used to soak damage; i’m not sure whether or not this was supposed to apply to nameless NPCs but originally I had been using that rule. I’m considering now making each stress box worth a single stress level and increase the amount of boxes possessed by each NPC, this would make it far easier during a combat to just tick off a number of boxes equal to the damage taken.
- Opponents being overwhelmed by odds
Although the mob rules work really well and are great for representing the mobs of soldiers, tech-priests, fighter pilots and other generic ships crew that the players in my game (rightfully) tend to tool about with, it does create a situation where any single antagonist is liable to be overwhelmed by mobs of nameless NPCs (lead by a much more capable player character) in short order. Part of the reason for this is that i’ve been having mobs directly add their teamwork bonus to the players score and thus it can result in some quite high final tallies (even on a mediocre to poor roll); this wasn’t really a problem in the Bloodletter encounter since it was just a single opponent against a whole ship of crew.
In future I think that i’ll adopt a couple of tactics in order to lessen the impact of mobs:
- Using terrain to restrict their use: If only a certain number of people can assist a roll then the bonuses are limited.
- Having area effects or psychological effects that affect nameless NPC mobs but that the PCs are proof against: Some sort of ‘fear’ effect may be appropriate for creatures like daemons, perhaps some sort of test being required to initiate an attack or even just a stunt that means for the first round of a combat nameless NPCs cannot attack.
- Having mobs roll seperately rather than adding their bonus to a player character: This would result in two reasonable rolls rather than one really high roll.