Showing posts with label Tactics. Show all posts
Showing posts with label Tactics. Show all posts

Sunday, September 26, 2021

Clean-up Blips - Janitorial Random Encounters

I had a dream last night that I was a rat-man in a dungeon that human adventurers invaded.  Lacking the strength to confront them and their hunting-cats directly, I worked to douse their light sources, lead them into ambushes, and change the environment behind them to make it more confusing.

It occurs to me that this is basically the life of a sensor-blip-style random encounter, where they linger in the dungeon near parties rather than moving to confront them directly.  And the idea of having random encounters behind the party "clean up" the dungeon is one I hadn't considered before; I know the idea of "dungeon clean-up crew" monsters appeared in some of the older books, but I took it as an ecological consideration, something that happened between adventures rather than during.  It amuses me, the image of a crew of ratman janitors armed with a mops and buckets, doing their part to fight the humans by hauling away the bodies, cleaning up the blood, erasing the chalk or charcoal graffiti, trying to put out the oil fires, maybe even moving the furniture around so that they'll have a harder time finding their way back out of the dungeon.

Thursday, September 6, 2018

Random Encounters and Space Hulk's Blips

Blindsight got me thinking about Space Hulk, which got me thinking about the blips.  Space Hulk has a mechanic where the alien player conceals his forces and moves them as "blips" on the human player's radar until they come into line of sight of a human unit.  It's a nice way to handle information asymmetry and partially hidden movement.  I think something like it might solve one of the issues with random encounters as they are played.

The way a random encounter in the dungeon goes in D&D (certainly in my games, at least) is usually something like this:
  • Party is doing stuff
  • DM rolls d6, 6 for random encounter
  • DM generates wandering monsters
  • Surprise roll
  • Reaction roll
  • Initiative roll
  • Combat 
  • Return to exploration loop
What's missing here is tension.  The encounter happens, it is resolved, it probably doesn't really link to anything else in the dungeon because it was just generated.  Resource costs are applied and then life goes on; there is no qualitative change unless the random encounter was on the way out while the party was already resource-exhausted.  It's almost like Bad Trap Syndrome, but with a combat intead.

The other thing missing here is that a rule has been ignored - the random encounter distance rule, another roll between generation and surprise.  Nominally should be 2d6 * 10 feet in the dungeon, in ACKS at least.  That's a long way (in expectation).  That's outside torch radius on average (30' of bright light, 20 more feet of shadowy illumination).  It's also outside of average monster infravision radius (60').  If you, like me, tend to not have 70' hallways, generally that's going to be around multiple corners or through multiple doors.  This is not typically a "the monsters come around the corner or through the doorway, roll for surprise" situation.

The reason this rule is ignored is straightforward - tracking runtime-generated state outside of PC line of sight is a hassle.  If you're using a graphpaper map, there isn't a good way to track groups of monsters moving through the dungeon.  Digital tools could probably handle this better.

But if you're willing to pay the price to track these 'blips' outside of PC detection range, the atmospheric and gameplay benefits are, I suspect, significant.  They turn random encounters from "fire and forget" into lingering threat, things just outside your vision, eyes reflecting your torchlight.  Waiting in the dark for you to make a mistake, stalking you, looking for an opportunity to pounce (or maybe just to eat your dead).  A heavily-armored party might not even be able to close with and engage such groups due to speed differences.  I suspect these lingering random encounters might encourage the use of thieves in the shadowed zone (where they can quickly pin down or drive off such enemies; pickets) and other "lightweight" play.  Multiple random encounters might lead to multiple groups of uncommitted creatures - morlocks ahead, morlocks behind, nowhere to run.  Depending on the monsters and the ecology of the dungeon, multiple "open" random encounters might fight among themselves (presenting an opportunity to players) or join forces.  Players might detect them with listening or detect evil...  blips on the paladin-scanner.

These things in the dark become a source of tension, a source of potential energy for the dungeon.  The other shoe, ready to drop.

On reflection, this difference in use is reflected in the old naming - "wandering monster" instead of "random encounter".

Tuesday, November 22, 2016

ACKS: The Recon Team

My players have run up against time and speed limits.  The dungeon portal only stays open for up to six hours, and they've started running up hard against this time limit during their last couple of expeditions.  This has severely limited their ability to explore outside of their currently-mapped area.  Most of my players seem to be in favor of setting up a safe zone and camping in the dungeon, but one of them was asking me about the encumbrance rules yesterday and talking about doing a low-gear, evasive reconnaissance operation one week, and then sending a more heavily-armored follow-up expedition to selected targets the next week.

I think this is a very interesting idea.  I hesitate to call it a good idea, because I've never seen it done before, but it's very much in the style of "dungoneering as heist movie, not action movie", and I think it'd probably work well if done cleverly.

So let's think about this a bit.

To move 120' per turn, you need to be carrying less than 5 stone.  90' requires less than 7 stone, and 60' requires less than 10 stone.  An unarmored wardog has a speed of 150', while an armored wardog has a speed of 90', and a mule can carry up to 20 stone at 120', but drops to 60' above that.

There are a couple of proficiencies which might be unusually good for this type of operation.  Endurance lets you skip rest turns, increasing your effective movement speed by 20% (although notably, skipping multiple rest turns doesn't seem to stack up increasing penalties under rules as written).  Running boosts your base movement speed by 30' in chainmail or lighter armor.  Skirmishing lets you disengage without pre-declaring it (I'm not sure this is actually good if your doctrine is evasive, though, because in that case you probably tend to declare disengage?).

Dexterity really shines as a stat in this type of party composition, because it lets you get your AC up into the 7-8 range without having to compromise your speed with heavy armor.

In terms of party composition:

Wizards, thieves, bladedancers, bards, and nightblades are not inconvenienced in the least by requirements for reduced gear, and can all easily maintain 120' speed.

Barbarians, explorers, and other classes limited to chainmail might have to make some sacrifices to maintain 120' speed.  I think our current explorer is in chainmail with an arbalest and a spear, which is 6 stone of gear for 90' speed.  To hit 120' with a real ranged weapon, she'd probably have to downgrade chainmail to ringmail and spear to sword.  But 90' might be an acceptable movement speed; it's still 50% faster than our party's current speed, and at 90' you can use armored wardogs.

Assassins are already a weird case, because they can use heavy armor, but they lose a lot of their abilities if they do.  For 120' speed, leather, a polearm, and a ranged weapon is probably a good bet.  At 90', they have more options.

Assassins and explorers are both notable because they have Dex as a prime req (so they can boost it during character creation), and they get fighter damage bonus.  In a high-speed low-drag party, they're both good front-line options.

Thrown weapons might actually be decent in this paradigm; each javelin is an item rather than a stone, so you can fill out your last couple items of encumbrance with them (say you're an explorer going for 120' speed in chainmail with a sword; that puts you are 4 stone and one item.  You can still carry four javelins or oil flasks, which put you at 4 stone and 5 items, one short of 5 stone and 90' speed).  Slings are also substantially less horrible here than usual, because they have decent range (more than double that of javelins) and only weigh one item of encumbrance with their ammunition.  d4 damage sucks, but fighter damage bonus, Inspire Courage, and Bless all apply...

Fighters, clerics, dwarves, and spellswords all have some difficulty at high speeds.  To hit 90' speed, you have to lose any two of plate, shield, and spear.  Best possible AC without magic or dexterity at 90' is 7, via banded mail, shield with fighting style, and a sword (and four flasks of oil or javelins).  It goes without saying that the weight-reduction effect of magic armor is fantastically good in this context.  Plate with a one-handed sword used in both hands is not a terrible choice if you don't have FS:Shield (as if), and banded+spear (or polearm) is probably doctrinal for second-liners (including spellswords).  At 120' speed, all of these classes are going to have real trouble without magic armor.  Fighters do get more proficiencies than most classes, and for one specializing in this sort of thing Running is actually a pretty strong option.  Chainmail armor, shield with fighting style, and a spear weighs 6 stone, which would normally put you at 90', but Running boosts that back up to 120' with AC6.

Thrassians and ratmen, unfortunately, are in a whole 'nother level of trouble, since their base movement speed is only 60'.  Besides Running, their best option is probably to ride mules.  We've previously ruled that an adult human weighs about 15 stone.  Since mules can carry 20 stone at 120', a thrassian gladiator in chain (19st total) could ride one at 120', and then dismount to fight with tooth and claw at AC7.  This poses some difficulties, as mules can be killed and you need to remount if the party decides to retreat, but Riding as a proficiency scales well into the late game and solves the more pressing of those two problems (I am not so cruel a DM as to rule that Riding (Mules) should be separate from Riding (Horses)).  The other can be solved by bringing more mules, which you were going to want to do anyway for mundane adventuring gear and hauling treasure; if you're not going to need a piece of gear close-to-hand in combat, put it on a mule.

So with all that said, I think 90' speed is very doable.  Three of the five PCs transition very well to lightweight play (mage, bladedancer, and explorer).  The elven enchanter and bard henchmen do as well.  The fighter henchmen are mostly either expendable or replaceable with wardogs (of which the party already has two).  The five characters who run into difficulties are Scarth's two cleric henchmen, Clarence the dwarf, Chathis the lizardman, and Dogeater the ratman.  Clarence runs plate and two-handed warpick, but could hit 90' by switching to a one-handed pick used in both hands.  Slagathor the Cleric runs plate and polearm with Martial Training, and could drop down to banded and polearm.  I think Rheingold is plate+shield with Lay on Hands; dropping the shield is probably the best option for him.  Dogeater and Chathis really don't have many options besides being mule-dragoons.

Anyway, I'm excited about this proposed alternate style of play and hope it happens.  I've been a little bit bored with the dungeoneering game recently, and mixing it up would be good.

Monday, June 27, 2016

Breaking the Phalanx, Better Thieves

Previously, I mentioned that the reason that thieves suck in my games is that there are no traps, and they aren't good in combat.  I don't want to add traps, so I must change the circumstances of combat.

The consensus among my players is that dungeoneering combat is largely "solved" by the Dungeon Phalanx - a formation of ranked fighters with plate, shield, and spears, supported by a wizard or two and a cleric in the rear.  The phalanx is very strong in melee in hallways, and when met in open rooms by a foe with superior numbers, it tends to hold the doorway through which it entered and let the wizards do the heavy lifting.

But, there is little place in it for thieves, assassins, explorers, and other lightweights who aren't packing sleep.  If placed out in front of the phalanx, the expectation is that they will be cut to ribbons, and can't retreat through the shield wall.  If placed in the rear, their targets for archery are typically restricted to those already engaged in melee, and as a consequence Precise Shooting becomes a proficiency tax and they still won't hit anything because -4 is brutal.

There are a couple of ways to address this.

One potential fix is suggested by Jeff Rients, in his old post on miniatures scale, where he cites an early source suggesting that back when, a 1" square on the mat was typically ~3 feet instead of 5.  This lets you put three guys in each rank...  or leave a hole in the middle for your thieves to retreat through.  Ultimately, though, this increases the concentration of firepower possible in the front of the phalanx, making it stronger in its typical combat situation (though massed melee humanoid foes probably benefit similar from this change), so I'm not sure it solves the problem.  Making some hallways 20' wide instead of 10' would have similar effects, stretching the frontline.

Another option is area attacks, which wreck close formations.  Unfortunately, area attacks also wreck thieves, who have few HP and no Evasion-equivalent in ACKS (Blast and Breath is actually their weakest save).

Probably the correct option is larger open spaces and much more skirmishy enemies, with archers, hit-and-run attacks from the sides and behind, and ambushes along avenues of retreat.  Basically, Tucker's Kobolds.  Notably, one of the main failures of the Phalanx in previous campaigns was under archers in a very large room.  This was also possibly the only time a backstabber (in this case a nightblade) was presented with a golden opportunity to make use of that ability in that campaign.  So that's a dungeon-design and monster management problem on my end - smart, prepared foes unwilling to just engage in a slugfest with the phalanx place a premium on surprise and ability to engage at range, and larger rooms give thieves some room to maneuver, hide in, and shoot from.  Thieves and assassins also excel against intelligent opponents standing guard with an alarm system (gong, war-horn, whatever), who need to be eliminated quietly before they can trigger it (though sleep can also solve this problem).

Clarifications on the nature of light and shadows might also help.  I believe that the rules intend for Hide in Shadows to be usable in the fringe-areas of the zones of shadowy illumination emitted by torches and lanterns, though this is never made explicit.  This provides a relatively safe place out in front of the party for thieves and assassins, from which they can surprise enemies (because they aren't in the bright zone), in which they can hide, and from which they can retreat to behind the party's front line.

In terms of mechanical fixes to thieves themselves...  It probably wouldn't hurt to trade away a couple of rarely-used skills (say, Find Traps, Remove Traps, and Picking Pockets in my game) for some subset of Precise Shooting, Weapon Finesse, Swashbuckling, Skirmishing, Combat Reflexes, Acrobatics, and Skulking.  Seriously, Picking Pockets is not even close to as useful as basically any combat-oriented class proficiency.  Even Weapon Focus triggers about every 20 attacks, so maybe once every session or two, whereas Picking Pockets is useful basically never.  I'm more than willing to let thieves continue using Picking Pockets at its nominal value the one time per campaign it actually comes up (and for hijinks, just standardize all hijinks into a single uniform throw by level, a la Magic Research Throw, but modified by Dex.  Maybe with a new class proficiency like Magical Engineering that grants a bonus to hijinks).  The thief suffers from a proficiency tax problem to be combat-effective, and frankly being in melee with d4 HD and AC ~5, even with all of those proficiencies, is not exactly low-risk.

Honestly, the correct solution is probably HD 1, Fighting 1, Thief 3.  Thief 2 is just so bad that even at 6 skills, Fighting 2 / HD 1 / Thief 1 beats the crap out of Fighting 1 / HD 1 / Thief 2 for not that much more XP.  So we're doing it this way instead.  This costs 1700 XP, right on par with Assassin (great, advances my goal of reducing XP divergence slightly between classes), and ACKS' class-points system be damned.  For skills, you pick up Hide, Move Silently, Backstab, Climb Walls, Hear Noises, Open Locks (I'm on the fence about Open Locks...), Read Languages at 4th, Read Scrolls at 10th (together count as 1), and then three class profs, probably Precise Shooting, Weapon Finesse, aaaand...  Swashbuckling?  At low levels, Precise Shooting and Weapon Finesse mean that you can actually attack and hit, and Swashbuckling means you might even survive it.  At high levels, Precise Shooting and Weapon Finesse fade in importance (Swashbuckling somewhat less so because it scales slowly), but your stealth skills pick up the slack as their success rate rises.

If you wanted to get really crazy, you could even change up those proficiency-sets like Barbarian does.  So you might have Merry Robber with Precise Shooting, Swashbuckling, Alertness, and green tights, Rake or Bravo or Hoodlum with Weapon Finesse (or Fighting Style: Two Weapons, for main gauche), Swashbuckling, Combat Reflexes, and a big hat, Footpad or Cosher with Skulking, Skirmishing, Weapon Finesse, and an ugly brown medieval hood...

Saturday, December 5, 2015

The Nonlinear Effectiveness of Armor Class

Or, why Fighting Style (Shield) and Plate is pretty great.

So you're playing ACKS and you find a ring of protection +1 (a rare and extremely valuable thing).  The wizard with AC0 wants it, because having any AC at all would be nice.  The fighter with AC10 (plate +1, shield +1, fighting style shield) also wants it, because he thinks AC11 is much better than AC10.  The wizard argues that this isn't true, the fighter has enough AC already, and he should stop hogging all the magic items.

(Then the ghouls attack while the party is arguing, but that is neither here nor there)

Who is right?

It turns out the fighter will actually gain (much) more survivability than the wizard will.  Here is why.

The more AC you have, the better each point of AC is, on average across all reasonable monsters (up to a point).  Let us consider four characters: wizard in no armor (AC0), clumsy thief in leather (AC2), barbarian in chain (AC4), and fighter in plate (AC6).  Let us also consider a couple of hypothetical monsters: an orc (THAC0 10+), an ogre (THAC0 6+), a stone giant (THAC0 3+), a woolly mammoth (THAC0 0+), and a great wyrm dragon (THAC0 -3+).  If each of these monsters attacks each of these PCs, what is the probability that they will hit?


AC 0 2 4 6
THACO



10 0.55 0.45 0.35 0.25
6 0.75 0.65 0.55 0.45
3 0.9 0.8 0.7 0.6
0 0.95 0.95 0.85 0.75
-3 0.95 0.95 0.95 0.9


Looks pretty straightforward - +2 points of AC reduces your probability of being hit by 10%, as we'd expect (up until the monsters only miss on a natural 1, which is what the 0.95s in the bottom left mean).

But what does having your probability of being hit reduced by 10% actually mean for your survival time when fighting this monster?  It can mean a lot more than a 10% increase in survival time!  Consider AC4 vs AC6 in the case of THAC0 10+.  AC4 gets hit about once every 3 attacks.  AC6 gets hit once every 4 attacks.  So assuming each PC can take the same number of hits, the guy in plate lives 33% longer on average than the guy in chain.

What happens if platefighter gets a shield and Fighting Style, bringing his AC up to 8?  Or fighting style and various levels of magic shield and plate for ACs 10, 12, and 14?



AC 8 10 12 14
THACO



10 0.15 0.05 0.05 0.05
6 0.35 0.25 0.15 0.05
3 0.5 0.4 0.3 0.2
0 0.65 0.55 0.45 0.35
-3 0.8 0.7 0.6 0.5


AC8 only gets hit by an orc once every 6-7 attacks.  He will live twice as long as the PCs in chain, and 1.5 times as long as if he were in plate.  At AC10 (shield +1, plate +1, and fighting style), he is hit by an orc only on a natural 20, once every 20 attacks, and will live five times as long as if he were in nonmagical plate with no shield (or about three times as long as if he were in nonmagical plate+shield+fighting style).

This is what I mean by the nonlinear effectiveness of Armor Class.  The more AC you have, the more each point increases your life expectancy in combat, up to the point where your opponent needs a natural 20 to hit.  Just that one point that pushes them from 19+ to 20+ to hit doubles your life expectancy.

On the flip size, the increase in AC from 0 to 6 only changes your probability of being hit by an orc from 0.55 to 0.25, slightly more than doubling your survival time (assuming the AC0 character has the same number of HP as the AC6 character - an AC0 wizard with d4 HD thus has about a quarter the combat life expectancy in melee of an AC6 fighter with d8 HD).  At higher THAC0s, the increase from AC0 to AC6 is even less effective - it means the great wyrm will hit on a 3+ instead of a 2+, which is right around a 5% increase in life expectancy.  At that point 6 stone of armor is a liability.  Go magic or don't bother.

By comparison, at high THAC0s, even small increases in AC continue to matter.  AC12 vs AC14 at THAC0 -3+ is 12 hits per 20 attacks vs 10 hits per 20 attacks is about a 20% increase in life expectancy.  Against a stone giant (THAC0 3+), AC 14 survives one and a half times as long as AC12, and twice as long as AC10.  Those last couple of points that push your AC up into the low teens are really, really good.

(I strongly suspect that there is some connection here with something like the harmonic progression or some other known sequence, but mathematical insight is failing to strike today)

Incidentally, this also explains why some of my past players felt vehemently that classes who can't use plate shouldn't be in melee, and that if you roll an 18 Dex and a 9 Str, you should use that statblock for a fighter (AC11 with shield and fighting style at 1st level and no magic?  Yes please) rather than a thief, explorer, or other dex-based class.  This is also, I suspect, why there are basically no spells that increase other peoples' AC in ACKS (except protection from evil, which has some drawbacks).  Shimmer (+2 AC for 3 turns) with range touch is probably absurdly good for keeping the monsters from breaking through your fighter-line.

To return to our AC10 fighter and AC0 wizard, the wizard gains, against opponents with THAC0 10+, only 10% survivability by increasing his AC by 1, and that falls as THAC0 increases to the point where it is irrelevant against opponents with THAC0 1+ or better.  The fighter, by comparison, doubles his survivability against opponents with THAC0 9+ by increasing his AC to 11, and even against great wyrms with THAC0 -3+, that +1 point of AC increases his expected survival time by about 8%.

Then the question becomes, "Is expected survival time in One Monster vs One PC combat a representative metric of utility in an adventuring context for item allocation purposes?"  I think it's pretty arguable - you can't do the party any good if you're unconscious in a pool of your own blood.  Likewise, if you live twice as long, you get twice as many chances to attack before dying, and your odds of successfully escaping from combat are much improved too.

This post roughly reflects the state of the dungeoneering fighter metagame in my group - shields are king.  I am curious under what circumstances other fighting styles make sense for classes who have access to plate and fighting style shield.  I think constructing an ACKS combat simulator and just running like a million trials is probably a better plan that doing math for that, though.

Monday, October 12, 2015

ACKS in the Wilderness

I have a confession to make.

As much as I hate using grids for combat, something they really do make things better.

In this case, last session we had our first real wilderness combat in ACKS.  We'd had some during previous campaigns, but in the theater of the mind things tended to get very muddled in so open an area of engagement, and the party's melee contingent tended to assume they could always get in and engaged.

This combat was very different.

The party was hunting a group of ghoul woodsmen in the mountainous forests north of Ostergot.  Their cunning plan was to catch and field-strip a deer, hoping that the smell of blood and meat would draw the ghouls to them.  They were correct, and over the top of the ridge advanced a group of 8 ghouls with bows in a broad skirmish line (I play ghouls as "of malign intelligence at least equal to a human's").  The PCs were mostly 5th-6th level at this point, and the PCs fighters have ACs in the 8-9 range.  Eight ghouls at this level is somewhat concerning, but not normally a dire, mortal threat to a PC unless something goes quite wrong.  The ghouls advanced down the slope, trading arrows with the party's archers and taking a fireball in the center of their line.  The ghouls began a fighting retreat and two of them managed to inflict some pretty serious damage on the party's unarmored witch.  The party's heavily-armored fighters were unable to catch them and engage, and in the end it was the archers that did them in.

This was a very unusual combat for us in ACKS.  Ranged enemies are not particularly viable in the dungeon, but in the wilderness even weak ranged foes can still be dangerous as long as they're fast.  This fight was not the melee fighters' to win; instead it was the assassin and the explorer's (and those few fighters who had thought to bring bows).  In the absence of archers in the party, I expect the ghouls would've exhausted their arrows before downing any of the party's superheavy fighters, but the party's wizard and witch would've been toast long before then.  I see three counters to this:
  • Superior ranged firepower (as happened in this case) - beat the archers at their own game.  Honestly a party of mid-levels fighters can be a competent ranged force if they're willing to carry; most archer-types aren't super-high AC, so losing out on dex bonus to hit them is probably not a huge deal, and strength+fighter damage bonus applies to bowfire.  The problem with this approach is that it means you can't use a shield, which drops the fighters' ACs by anywhere from 2 to 5 points in this party (shield +3 and fighting style shield), leaving them vulnerable to missile fire and cavalry charges themselves.
  • The phalanx / testudo / hedgehog - huddle up (perhaps aided by favorable terrain), shield your casters, and wait for the enemy to run out of arrows.  Not a whole lot of fun, and honestly pretty risky, because they are going to get some lucky hits even against high AC PCs before running out of arrows.  Also requires a very high ratio of shieldbearers to squishy casters, because a more-mobile enemy can encircle a fixed defense and strike from any side.  Performance against horse archers should be comparable to that against foot archers, but might actually be able to receive and stop a heavy cavalry lance charge if done properly.
  • Superior speed - mount up and run the bastards down.  Takes a proficiency (Riding) and requires a horse (in short supply), leaves you vulnerable to having your horse killed out from under you, but also the premier delivery system for heavily-armored melee fighters in the wilderness, and massed lance charges are spectacular, especially with fighter damage bonus and cleaves.  Also scales well into the high levels with monstrous mounts.  Still somewhat vulnerable to light cavalry / horse archers, but not in the same way that infantry is to infantry archers - if the horse archers are in range to fire on you, you're in range to lance-charge them.  The lance charge can also bog down against tough / high HD foes, leaving the party's fighters engaged with something scary without a good way to retreat (particularly if their horses are slain).
  • (Situational) magic and trickery
In any case, I look forward to more exploration of tactics outside the dungeon.

Friday, March 15, 2013

Miscellany - Of Ships and Burning Oil

Wasn't feeling well last night, so no real post today.

I've been reading up on naval tactics and strategy with the idea of getting some context for Starmada and Full Thrust.  Found two interesting things that kind of mirror our experiences with Starmada.  First, from wikipedia:
Naval tactics throughout the 16th century and well into the 17th century, however, was focused on countering the oar-powered galleys that were armed with heavy guns in the bow, facing forwards, which were aimed by turning the entire ship against its target. Though far less seaworthy than sailing vessels and highly vulnerable to boarding by ships that rode higher in the water, the galleys were a serious threat due to their ability to aim accurate heavy gunfire low in the hulls of larger sailing ships.
So there is historical precedent for G-arc superweapons!  Doesn't make them any more fun, though :\

The other interesting point was a discussion of the continued usefulness of aircraft carriers in the missile age, with arguments made here (caution - pdf), here, and here.  I thought it was neat to see kind of the same discussions we had go down in the Real World.

Also, looking at ACKS again, I think we were playing military oil wrong the entire time.  We were applying fire damage every round for standing in a burning area, which (as we noted at the time) was strictly better than using oil as a single-target weapon for 1d8 damage for each of two rounds.  However, further inspection shows that oil spread on the ground covers only a 5' diameter rather than a 10' diameter, which means that there're large non-burning areas in a 10' square containing fire.  Also looks like area-deployment of oil require careful pouring, rather than throwing, so it can't be done at range.  So I think the tradeoff is that poured deployment requires either pouring oil in the front line (in which case intelligent adversaries will realize what you're up to) or pouring in the rear and then retreating, which yields ground, while thrown oil can be used to immediate effect from the rear but has lower damage potential.

Tuesday, February 5, 2013

Of Reliability and House-Rules

You should not have a favorite weapon, or any other exaggerated preference for that matter. To become overly attached to one weapon is as bad as not knowing it sufficiently well. You should not imitate others, but use those weapons which suit you, and which you can handle properly. It is bad for both commanders and troopers to entertain likes and dislikes. Pragmatic thinking is essential. These are things you must learn thoroughly.
- Miyamoto Musashi, The Book of Five Rings

This post was originally a comment in response to tyflec's comment on my post on spell selection and reliability (reproduced below for ease of use).  It got a little long, though, so I decided it warranted its own post.
I feel like gravitating towards perfect reliability spells is sort of what you get for going combat-as-war. If everything is going to do its level best to kill us, and we don't have some kind of guarantee that they'll be on an even footing with us, then we as players simply can't afford to use spells that aren't reliable. Now, if you wanted to make a status-effect spell worthwhile, why not make it save-partial as opposed to save-negates? Like Blindness, say. If Blindness always blinded someone for at least one round, with a save determining whether they were permanently blind or not, it would be much more useful. Or, you could make it save-ends with a minimum duration of one round. That would solve the problem of perma-blindness instantly ending a fight, which is also not very fun. Although a minimum-one-round spell does lend itself to chain-casting to keep the creature blind for as many rounds as you have wizards... 
I disagree that desire for perfect reliability is a symptom of combat-as-war; I think it is more of a problem of general human risk-aversion.  Humans dislike failing more than they like succeeding, as a rule.  Perfect reliability means no failures, which is awesome, and something we'd expect most any reasonable human to pursue.  Further, I think that there is a case to be made for unreliable single-target spells in a combat-as-war game like ACKS.  If you're up against a 20 HD dragon and you've got one round to cast a spell, you're a damn sight better off casting Charm Monster than Fireball, because it absolutely will survive the fireball, but it might roll a 1 on its save against the Charm Monster, and then you will survive (and have a useful new ally).  An unreliable chance of success is sometimes better than an reliable certainty of failure.  Of course, an even better plan would be to run away, or, if playing combat as war, to not have gotten yourself in that position in the first place...

I think a better counter-argument for "reliability focus follows from combat-as-war" manifests itself when we look at 3.x character design (say for Tim's campaigns) and unreliable mechanics.  When we design 3.x characters, we usually design towards a specific concept or purpose, and then our satisfaction with the game is strongly correlated with how well we fulfill our intended function in combat (I'm a little bit this way, and it seems very true of my conversations with Alex; what with Shin Yao and Torrison I think you (tyflec) may be of somewhat the same mind).  When the mechanic we want to build around is unreliable because of the way the system implements it (save-or-suck casters, maneuver fighters, crit-fighters), we end up disappointed because we feel like we're not fulfilling our Aim In Playing, the successful application of the chosen mechanic, frequently enough for the game to be worth it.  Hence the push we see from you and Tim and others to make these mechanics more reliable; you want to build around them, but they are sufficiently unreliable as to be unsatisfying if you make their application your sole aim.  Thus, even in a combat-as-sport setting we still see this reliability problem within our group.

Getting from reliability to your second point about status effects, I'm not really concerned with making status effects 'worthwhile'.  At this point I'm of the mind that parts of the game are tools for different purposes, and my aim is to figure out how to play it well, to learn which tools are good for which tasks, and to build characters with a broad enough array of tools to meet a wide variety of challenges successfully.  If you want to play a dedicated save-or-suck caster, go for it...  but pick your targets and know their weak saves, bring a wand of magic missiles for mindless undead foes and a crossbow for golems, and don't complain when a reliable damage caster one-ups you most of the time.  Save-or-sucks are a good way to dispose of a weak foe or two quietly and with high reliability, in situations where bloodstains, fire, and screaming aren't going to work (eg, infiltrating a castle, hold-personing sentries), or to try for a lucky knockout-punch against a big foe.  Why are we trying to make them something else?  If you're a save-or-suck specialist, then yeah nice packaged level-appropriate encounters against foes with good saves are going to be frustrating, because the guy with the fireballs is going to be effective all the time and you're only going to be sometimes.  Take it as a challenge; what're you going to do about it?  The easy way out is to not play specialists!  Use the right weapon for the right fight.  If you must be a specialist, seek out situations where you can leverage your specialty (knock-down, drag-out fights probably aren't those, for this sort of specialist).  Play smarter, hop the railroad tracks, and tell the DM where he can stuff his balanced encounters as you Charm Person Warduke's family rather than the baddy himself.

Mostly I'm kind of tired of a trend I've been seeing in this group for a while.  xk says it well:



Our first reaction to issues in a game is usually to start proposing rules changes and stealing rules from other systems.  Rarely are we willing to admit "I chose a dumb thing to specialize in" or "I applied this tactic in a situation where it was clearly a dumb idea."  Tactically, we're idiots, a lot of the time, and we absolutely do not pay attention to what the system is telling us about how it wants to be played.  We adapt slowly and infrequently, and we just keep doing the same thing that our characters were 'built' for, even when it is an awful plan.  But instead of admitting that we're bad, we shift the blame to the rules, and decide to go mucking around with those.  Rather than having our characters adapt and diversify like people in a 'real'-esque world would, we bend the laws of physics because it saves face.  And then hey, we get to look fancy because we're doing Game Design and out-thinking the professionals!  Feels good, man.

But the game never gets better, because some guy (possibly me) will eventually choose to super-specialize his character in touch-range-only necromancy or fighting with two shields or some other Clearly Stupid But Mechanically Vaguely Plausible Idea, so we keep contorting the system to make that viable, and (more often) houserules cause cascades of unintended consequences and then we have to patch those...  It's even better if you add supplements and other peoples' houserules from the internet.  Been down Houserule Road, burned several home games over the years.  Sorry dad; I think I might've finally learned my lesson.

At this point, I'm all for clarifying and interpreting places where the rules are unclear, or for altering the rules to better conform to the intended setting, but changing the rules for the sake of 'making the game better' is not currently of any interest to me.  The fact that the few alterations I made to ACKS were arguably causal for some of the terminal issues with the campaign leaves me very leery of altering things without fully understanding them and properly considering the implications of the changes I'm making.  The flaws of a game, in my experience, are often with how the rules are being applied, with the way it is being played, rather than with the rules themselves.

If a class or strategy 'sucks,' the interesting solution isn't to patch it; it's to either not play it, or to figure out a way to play it which makes it not suck, and to diversify your strategy so that you're still useful in some way when you come up against a hard counter to your standard plan of engagement.  When I say "Dismember is a bad spell for PCs, the thief is an awful class, and 3.x archers are terrible", there's an implicit "but I challenge you to prove me wrong in action, using the tools present in the system-as-written."  When Dan's TB rogue sucked, the general opinion within the group became "TB rogues suck," and I responded by building Asmir and running him in a way which did not suck.  I'm actually seriously considering running a thief for Drew's ACKS game for just this purpose; the group is convinced that thieves are bad, and for every time I try it and end up dead, the victory when I do finally crack it and play a successful thief will be all the sweeter.

In sum: I'm tired of asking and being asked, "What about removing action points, or adding inherent bonuses in place of magic items, or banning certain feats or classes, or making guilds available to non-thieves, or building custom trade hijinks for non-criminal venturers, or making domains available to sub-9th characters, or improving sunder and save-or-suck?"  I want to play the game, really play it, adaptively and with a chance of defeat, rather than playing with the game.

...  but if you absolutely must make new save-or-suck spells that are Save Partial and strictly better than the current versions, at least make them higher level and give them new names, for god's sake :(

Wednesday, January 30, 2013

On the Application of Mercenaries

Towards the end of the ACKS game, we started to see the deployment of large numbers of mercenaries for hex clearing operations.  This wasn't necessarily a problem, and one of my players really wanted his PC to be a 'leader of men', so it was mostly OK barring issues of resolution.  We have a decent combat system for combats involving 10 individuals per side in the ACKS core, and a decent system for resolving combats of hundreds per side in the Domains at War preview, but there is not a particularly good way to resolve a battle between 34 pikemen and 57 ratmen.  We considered scaling down the DaW rules, but never got to it.  There's an order of magnitude range missing in there, which is unfortunate.  This meant that my options for fights using mercs were "OK, you win" or "I think you're going to need more mercs."  I've no problem with the "OK, you win" approach, but I felt there needed to be a clear cost for using it.  The natural and obvious cost is casualties, but determining how many casualties a group of armored L0 men take while engaging a small integer number of 6+ HD monsters was not at all obvious.  That the mercs were also cavalry archers further complicated matters of casualty estimation.  In the end I ended up dividing combats mostly into "fights which your mercenaries will win with no or minimal casualties" and "fights that your mercenaries will be effectively unable to help you with."

There was, though, in the metagame, definitely a conflict going on with regards to the types of monsters considered acceptable to destroy out-of-hand with mercenaries.  I was of the notion that there were certain monsters that took heroes to deal with; the litmus test for me was "Are the PCs and players legitimately afraid of this?  Yes?  Then the mercs probably are very, very afraid of this."  My PCs disagreed, employing mercenaries not only against beastmen and animals, where I was in agreement that they were appropriate, but also against proper monsters, and I felt kind of bad about mostly 'nerfing' their effectiveness for lack of a resolution system.  Upon further reflection, though, I realized that there are already several "Protection from Mercenaries" effects in the game.  The two that jumped out at me immediately were dragons' frightful presence and the immunity to non-magic weapons of gargoyles and incorporeal undead.  The first is effective because it means that low-HD creatures just can't engage a dragon effectively; a L0 man in ACKS flees in panic from a dragon with a fear aura, 100% of the time, no save, and characters of levels 1 through 3 are similarly out of the action.  This is a wonderful mercenary-proofing mechanism, and the fact that the penalties for characters higher than 3rd level are minimal suggests that this might be the original intent of the mechanic.  Similarly, immunity to non-magical weapons prevents the application of large forces of mercenaries to monsters, since it is effectively impossible to outfit hundreds of mercs with magic weapons unless you have many wizards working on that full time and a huge amount of cash and monster parts to burn.  I don't think that this is the original purpose of immunity to non-magic weapons, since we see it on much smaller monsters like gargoyles which are often encountered in low-level dungeoneering settings, but it is a nice bonus.  Lycanthrope resistance to non-silver weapons kind of qualifies too; you could buy silver weapons for all of your mercs, but it might be prohibitively expensive (and difficult to do with the equipment availability rules).

I still kind of think that mercs should think twice (ie, check morale) on meeting a 30-foot-long centipede with a giant venomous shark head, or other freaky supernatural monsters that eat villages (since mercs are trained and hired for "military campaigns"), but I do feel less bad about letting them engage and possibly kill such creatures since there is a distinct subset of monsters which is effectively immune to mercenaries.  Of course, on a re-read of the morale rules, it looks like we've been playing those wrong too.  Mercenaries, henchmen, and monsters are supposed to check morale not just when half of them have been slain or disabled, but also the first time one of them is slain.  There is some ambiguity here with what 'slain' means due to ACKS' mortal wounds system; is a merc at -12 HP 'dead' for the purpose of provoking morale?  If not, can you postpone morale checks by not seeing to any of your wounded in the field?  So there's some weirdness there, but I feel fairly justified in mercs, henchmen, and monsters all checking morale more frequently than we've been having them do.

Tuesday, January 22, 2013

Conquest vs Resource Extraction, and Phases of Play

My ACKS game is kind of coming apart under various pressures, but it's shown us a lot about the system itself.  In this particular case, we had a few 7th-9th level PCs with early domains who were pushing for hex-clearing to be the primary activity of the campaign, and largely succeeded in directing things that way.  What we ran into, though, was that hex-clearing for a party of 4th to 7th level (as the rulers were frequently non-participating) was both difficult and not all that rewarding, since there were a great many low-yield beast lairs like giant catfish and crocodiles, while most of the remaining ones were medium-yield high-danger humanoid villages, occasionally backed by spellcasters (as they discovered to their peril while plotting a morning raid against weaselmen).  There was much boredom and frustration, and many grievous injuries and henchman deaths.  When brought to discussion, part of what came up is that "going through places and killing everything there just isn't that interesting."  And this comment brought to my mind a more general distinction in playstyles which is present in ACKS.

When dungeoneering at low levels in ACKS, you're not out to clear the dungeon.  You're there to find and steal treasure, because treasure gets you XP, and fights are generally to be avoided because they're dangerous.  Generally fights in low-level dungeoneering are a result of either a careful risk-reward calculation ("We hear what sounds like a snoring dragon on the other side; I vote we chance the fight because we have surprise and dragons have good treasure"), which is the unusual case, or the result of something going wrong - a bad random encounter check, negotiations going poorly with a group that were thought to be friendly, poor exploration technique, or what have you.  Those are more common in play than the first type.  This type of play I will term "resource extraction"-motivated; the party is in an environment seeking a particular resource, with fights being incidental and not the aim of the endeavour.

What we saw last semester in ACKS was a shift from extractive play to conquest-driven play.  The first two sessions last semester were the Conquest of Fort Camarone, and centered around clearing an abandoned Zaharan fort for use as a forward base, domain seat, and trading post.  All of the inhabitants of the first level were either slain or brought into the service of the PCs, the level was fully mapped, and the entrance to the second level was fortified to prevent things from getting out (mostly).  This was a very different style of play; whereas normally a dungeon lair of humanoids might be bypassed as "too dangerous for the treasure they'll probably have", it was now imperative that the threat of the lair be eliminated.  More fighting and less emphasis on treasure ensued.  It became somewhat reminiscent of a 3.x dungeon crawl, where, since the only source of XP was killing monsters, you wanted to kill all the monsters because that was what the system mainly rewarded. 

It was an unfortunate turn of events that this dungeon-clearing operation happened just as the semester started and we picked up three new players, who were never exposed to ACKS dungeoneering in the low-level style.  I suspect that this group of new players in the conquest mindset, combined with the focus of the players who had domains on expanding their domains, was what led us into conquest-driven wilderness adventuring straight from dungeoneering.  And it was there that we started having serious not-fun, which was further aggravated by hijink hijinks on the parts of some of the party and late-surfacing issues with the Venturer class.  And so the game goes on hiatus.

But, the upshot of this whole process was the realization that, if dungeoneering can be done in both resource extraction and conquest modes, wilderness play probably can too.  Once I realized this, it dawned on me that I had in fact run one session which was just such a wilderness adventure in extraction mode, and this was the Expedition to the Crocodile Temple.  In this particular adventure, the players had been informed by a treasure map that there was a valuable treasure to be had in a particular place in the wilderness.  They went to go extract that treasure, and any fights along the way were either accidents (random encounters) or against the treasure's guardians, well-justified by the expected value of the hoard.  This revelation also made ACKS' "treasure maps as treasure" mechanics make more sense.  Previously I'd mostly had treasure maps point to full-blown dungeons, but that was rapidly becoming infeasible due to elevated PC levels and prep time constraints.  Having maps pointing to high-value lairs as drivers for expeditions in the mid-levels is a much more sensible solution.  This means that mid-level parties should generally avoid tangling with low-value lairs like the weaselman village or the river full of giant catfish, and focus instead on large, high-treasure monsters like dragons where the party can focus fire, probably win via 3rd-level arcane spells (I really feel like d6 / caster level is where you start to get into proper Monster Killer spells that can take out real beasts), and gain large enough treasures to earn significant quantities of XP (part of the issue with knocking over crappy low-value lairs was that nobody was levelling, which made people grumpy).

Further, if this strategy is pursued at mid-levels, then by the time the party reaches name / domain levels, there will be 1) fewer lairs in the vicinity, since some will have been cleared in expeditions, and 2) the remaining lairs will be mostly of either humanoids or animal-intelligence creatures with no treasure.  The former poses significantly lower threat to 9th-level characters than to the 6th-levelers we were trying to take them out with (even given equal mercenary backing); a trog chieftain is about the equal of a kitted-out 6th-level fighter, and has a decent chance of winning a one-on-one fight against such, but is unlikely to win against a 9th-level fighter due to superior hit points and to-hit and probably better magic gear.  The latter category, giant animals, are generally not horribly dangerous (relatively), but there's just no compelling reason to kill them off unless the domain ruler is offering a bounty, you're the domain ruler and want the hex cleared, or you're sick of the random encounter result for that particular hex being giant spiders.  They're also much simpler tactically to deal with via mercenaries, area spells, traps and bait, and similar tactics which are readily available by high levels.

The other realization I had on this topic is that the trade rules are probably meant to be used in this mid-level range.  The party is supposed to pool cash, buy a boat, and start travelling as a group with the twin aims of reaching faraway high-value lairs and moving goods at a profit.   At least I think this is how the ACKS trade rules are supposed to be used; as a supplementary income to lair raiding for mid-level parties capable of dealing with wilderness random encounters, and therefore able to travel long distances.  Unfortunately, we were using trade as something more like "hijinks for the rest of us", where the party invested in autonomous caravans or the venturer PC's merchant company, and those went off and did their thing and many many die rolls later came back with a bunch of money.  This was the wrong way to play it; I should've been rolling random encounters for each wilderness hex traveled, which would likely have brought the PCs out into the wilderness in defense of their assets.

My conclusion, then, is that we accidentally skipped a 'phase' of the game.  OSR games are notable in that their gameplay changes significantly in manner and motive over the level range, as compared to 3.x / 4e where at first level you're fighting monsters in a room, and at 20th-30th level you're fighting scarier monsters in a bigger room.  In ACKS, though, what I'm seeing is more like:

1st-4th levels: dungeoneering.  You don't have the firepower and durability to take out wilderness encounters, so overland travel is probably a bad idea.

5th-8th levels: your wizard picks up fireball and the wonderful world of overland travel is now a lot safer.  Your thief and a few of his buddies start pulling treasure hunting hijinks to get you treasure map locations, the fighter leads the mercenaries, and off you go to fight dragons and other fun critters while avoiding the annoying crap like weaselmen whenever possible.  Optionally, engage in trade for a bit of extra cash or, if closely-affiliated with a local ruler, possibly pursue bounties for annoying critters that he wants out of his lands to get in good enough with him to get a grant of land when you hit 9th.

9th+ levels: the domain game, conquering hexes, realm politics, guilds, ???

And we made the mistake of skipping that middle one...  Definitely something to remember for the next campaign I guess.

Wednesday, April 25, 2012

Sometimes they win... (or, On Dragon Tactics)

Source: https://www.wizards.com/default.asp?x=dnd/ag/20031108a


In Tim's campaign this last weekend, we spent most of the session fighting the green dragon guarding the green chromata (one of five elder draconic artifacts).  Tim was rather disappointed with the fight, and in some respects I was too.  But first, the good:
  • Snatch + Throw was very cool.  My dwarf was thrown forty feet into a hut.  Nothing says high-level / badass like being thrown into a solid object, demolishing it in the impact, and then getting back up and daring them to do it again.  Also sweet was being able to do the "Tordek hits the dragon in the nose while in its mouth" art from the PHB; rolled a crit for it, too (guess I got the eye).
  • The dragon enfeebled Drew's monk.  That was a smart / rat-bastardy move, and I approve as a result (sorry Drew).
  • Decent use of fly-by attack to disrupt our ability to full attack, and a very interesting interpretation of its interaction with breath weapon.
  • Good terrain / scenery; cliffs to fall off of, rivers to jump over, huts to demolish, and so forth.
  • We managed to execute our planned tactics more-or-less flawlessly; Drew removed fear while I disrupted its spellcasting with arrows, Matt punched an enfeeble through its SR, Jared hobbled its wing with Sunder, and then we beat the living tar out of it.  With buffs up, we were all doing terrifying amounts of damage (70-120 points per full attack each for Drew, Jared, and I).  If Tim hadn't made it a Trailblazer Solo Monster for x4 HP, we'd've downed it within a round or two of engaging.
Which brings us to the not-so-good...
  • I had planned and prepped for a mature adult green (CR16).  We're level 10-11ish, so that would've been about CR+6.  This meant that all the buffs were go for this fight, because at CR+6, you need every last bonus.  I was justified in the belief that this would be such a fight because the black guardian had been a mature adult as well; CR14 when we were at 8th level, so +6.  And that was a hell of a fight.  (Yes Tim, it actually was a mature adult - black dragons aren't huge until mature, it had AC29, and it took about 250 points of damage to bring down.  An adult would've been large / AC27 / 200 points).  So I was a bit let down when it was actually just an adult green at CR13, for CR+2-3, which would've been a challenging fight...  if we hadn't buffed.  As it was, we were hitting with most attacks, and it missed me with about half of its full attack routine, which was highly unexpected.  This dragon was significantly weaker in terms of core numbers and raw melee power than the one we killed three levels ago.
  • Many poor tactics on the dragon's part.  
    • It knew we were coming for it, and it had 5th caster level.  It could reasonably have had some hour per level buffs up before the fight (Mage Armor), and during combat it should've been casting stuff like Haste and Displacement rather than Mirror Image and Fog Cloud (fog was great for the black dragon in a confined space, but I am dubious of its potential utility in the high-mobility fight we were in).  Slow would've negated our Haste edge, too.  The mature adult I was expecting would've had CL7, so I was prepared for stoneskin, improved invisibility, and potentially a mean dimension door + crush combination on Barradin (our sorcerer).
    • Failed to exploit its mobility edge to the maximum extent possible.  Better tactics would've been to continuously use fly-by attack with breath weapon, staying out of reach of our enlarged spearmen.  Once we were out of acid protection, we'd've had to head for cover or the woods.  Alternatively, if we split to avoid breath weapons, a good move would've been to snatch someone isolated (Barradin would've been a prime candidate, as would I) and fly off...  and then drop them from 200 feet of altitude for 20d6 falling damage.  For bonus points, drop into the nearby lake full of sea monsters.  Either of us would probably have survived, either by feather fall (Barridan) or being made of solid hitpointium (me), but it would've split the party and rendered a quarter of our force ineffective.  For a creature with three feats invested in flight (Flyby Attack, Hover, and Wingover), it spent entirely too much time on the ground.  Hover in particular would actually have been a fantastic plan; the 60 foot radius cloud of concealment that it generates would've forced the reach fighters into the dragon's own reach, and would've protected it from most of Barradin's offense (and hindered his casting).  Note that this differs from fog cloud primarily in that 1) it moves with the dragon, 2) it isn't burned off by fireballs or gust of wind.  Hence, useful.
    • Exceptionally smart play would've combined both of these elements.  Engage briefly to determine if we're a serious threat, determine that we are, use fly-by breath weapon to escape melee without provoking AoOs (and deplete acid protection), maybe snatch and drop to split the party or neutralize a particularly annoying foe, and fly off.  Wait 9 minutes so the party's minute per level buffs start expiring and maybe provoke the party into starting a short rest.  If significantly damaged, instead short rest off the damage dealt by the party; what's good for the PCs is good for the monsters (this also relates strongly to Al's advice on Monster Hunts; large solo monsters that are going to disengage need some way to heal, and TB's short rest is a beautiful way to do it).  Then, cast buffs of your own including the Cats / Bulls / Bears suite, Invisibility, Mage Armor, Protection from Good, Shield, Haste, Displacement, and so forth.  Meanwhile the party is either trying to track you (good luck) or sitting around your lair sweating bullets as their buff clocks tick down.  Return and engage with the buff advantage now back in your hands, and crush them beneath your scaly talons.  
    • Also entertaining is the possibility of combining the flight mobility advantage with fireballs from long range for the AC-130 effect, since we weren't warded against fire.  Probably a losing proposition against a party with an artillery sorcerer, though (but he had used most of his 3rd-level slots for elemental protection and haste...). 
    • If, after disengaging, buffing, and re-engaging, it was still losing, retreating back out was certainly a viable option.  A good plan after that would've been to shapeshift into a bird (the dragon's shapeshifting capability, while technically not rules-legal, was established previously so that's a fair move), follow the party back to the ship, and then do one or more of the following:
      • Sink the ship while the party sleeps; huge dragon with water breathing should have no problem punching a few holes in the bottom.
      • Kill the henchmen, crew, and mule if / when the party goes back out into the jungle to find you, then lie in wait aboard the ship.
      • Enslave via green chromata (mind control artifact against which we were warded) the henchmen, crew, and mule.  Attack the positions your opponent cannot defend...  like the minds of his allies.
      Then you end up with an unbuffed fight against the fully-buffed dragon and your former crew at the same time aboard a sinking ship in a lake full of sea monsters in the middle of the night. A third-engagement final climactic showdown.  Exciting!
    • Finally, a relatively minor mechanical error: forgot to utilize combat reactions.  For a creature with 20+ HD and full BaB, these generate giant defensive bonuses that can help keep you from catching rays of enfeeblement or from being hit with dragonbane weapons.
  • No minions!  Every quality villain has a few mooks to get in the way and Aid Defense at the very least.  If you're extra-lucky, they might even grapple the wizard.  Minions the party trusts (like mind-controlled henchmen) are a good choice, as are your own children.  Cultists are slightly less good, and undead are worst as a rule.
So...  short version is that the dragon played like a videogame boss rather than a giant evil intelligent lizard who has dealt with adventurers before (Int 16 is certainly enough to come up with any of the above strategies, especially given what was at stake).  Tactically, it played to our strengths (melee damage output and short-term buffs) rather than its (mobility), and we absolutely ripped it apart while sustaining minimal damage (yeah, Jared took half his HP in damage, but he takes half his HP every fight, so that's nothing special).  Strategically, it didn't play at all, refusing to turn the fight into a running guerrilla engagement or to escalate to total war against the PCs' allies.  Tim ran it in combat-as-sport mode; limited to the immediate battlefield, with no apparent long-term contingency plans in place despite this being its place of residence.  No explosive runes on the treasure, no caged tigers waiting to be released, no hidey-holes out in the woods to run to and lick its wounds...  Nothing.  The dragon existed only in the immediate place and moment; it had no past and no future.

You might ask, though, "Is a fight against a high-mobility flying combat-as-war dragon that neutralizes the party's strengths fun?  After all, isn't that what we're here for?"  And my response to this is that if the party simply tries to engage such a dragon with standard tactics, they will die like chumps.  While this can be entertaining in and of itself, hopefully they will realize this is the case before dying like chumps (this seems fairly likely, given dragon flying maneuverability and our acid protection).  Once this realization is had, the Crazy Plans begin.  Plans like "Let's polymorph the monk into a giant eagle and try to Stunning Fist the dragon out of the sky" and "Let's try to toss the dwarf onto the dragon's back" and "Maybe we can use the [mule | henchman | bard | halfling] as bait get him to fly low enough for the half-orc to break his wing, and then we can gang up on him on the ground."  I, for one, enjoy Crazy Plans much more than standard move-around-the-grid-and-roll-dice-until-it-dies combats.  Then, if and when the Plan goes right and the dragon is slain, the players can claim that it was by their cunning and skill, rather than purely by their numerical and mechanical superiority.  That they truly earned their victory, rather than having it handed to them.  That !!FUN!! was had.

Further, dealing with high-mobility flyers is one of the standard dragon-hunting tropes; comes with the territory, and shouldn't be ignored for the sake of a nice set-piece battle.  Used every dragon fight?  Maybe not; stuff does get old and annoying, and PCs will fall back on old crazy plans again, which then become not-crazy.  But this one in open wilderness?  Hell yes.  We failed to corner or ground the dragon; flight was a natural and suitable strategic consequence of our tactical error (which stemmed from the planning error of not bringing harpoons or giant nets of iron chain, which stemmed from the systemic error of the exotic weapon proficiency subsystem...  but that's another post).

In conclusion: Tim complained of the lack of cinematism in this fight.  I will agree that little was to be had (except throwing through buildings).  Retreating and re-engaging later builds tension; it's almost like having a legitimate recurring villain.  Crazy Plans beget cinematic moments; ergo, if you want cinematism, fight dirty and watch the players scramble.  Eat the henchmen, sink the boat, burn down their hometowns, and so forth.  This is a dragon, goddamnit, the biggest, baddest scariest monster in the book; anything goes.  It has a name and 16 Int, and it's on its home turf; this whole thing should've played out a lot more like Predator, complete with piles of dead henchmen (and potentially PCs), explosions, and traps (starring Shin-Yao the half-orc as Ah-nold).  Good stories do not come from standard "run up and hit him" combats - in the words of a sig on EnWorld, "When Perseus fought Medusa, the math didn't work and combat was really swingy.  Perseus was a hero.  The good stories are never about balanced encounters."