Monday, August 26, 2013

Chimeric Banes - The Swamp Kraken

Just as the Chimera has produced countless different varieties of Mongrels, she has also produced a broad range of different banes to serve her. During the Bane War, the vanguard of her army was largely her Accursed, though many of her lesser creations—particularly stench goblins—were present in very large numbers. Other more specialized creations complemented her military forces, as monstrous terrors that could overcome even the most disciplined and well-armed opponents. The Morrigan insisted on sending cauldron-born to join the Chimera, but these were either redirected to aid the other Witches or used on the periphery of major battles. It was always the Chimera's horrific creations that played the central role in the battles she led.

In addition to the creatures that served in well-organized units, some of the Witch's creations struck independently of the main battlefront. Working apart from her structured elements, they instead sowed fear and panic among Morden's populace. Hundreds of miles away from the regions that her armies conquered, the banes effectively served as a warning of the dangers to come. In some cases, their presence or even their legend was so threatening that entire towns sent letters of surrender to the Chimera months before her armies could reach them.

The swamp kraken is one of the banes that the Chimera unleashed to work independently of her main forces. Though it is named for the swamps that it commonly inhabits, the creature has also been observed in lakes, streams, and even some fast-moving rivers. Its body is seldom seen, and many legends surround its full appearance. Instead, its prey most commonly sees the massive tentacles, which emerge from bodies of water seemingly far too small to contain them.

When hunting, a swamp kraken typically lies in wait near the shores of the bodies of water it inhabits. It is believed that they burrow beneath the beds of streams or small ponds to better conceal their bodies. When prey approaches, they use their agile and powerful tentacles to grab and crush their targets. Often leaving pieces of their victims scattered across the shoreline, the swamp kraken then drags their prey into the water for consumption.

Swamp Krakens represent a significant threat to isolated communities, as they are capable of completely isolating a small town or village from its primary source of water. In a few cases, residents have abandoned entire towns when the risk became too great to try to obtain water.

Swamp Kraken


Attributes: Agility d10, Smarts d4 (A), Spirit d8, Strength d12, Vigor d10
Skills: Fighting d10, Notice d6, Subterfuge d12, Swimming d8
Pace: 4; Parry: 7; Toughness: 8
Aquatic: Pace 8
Tentacles: Each round, a swamp kraken has 2d4 tentacles available for use to attack its prey. Tentacles always select the Grappling attack action. Once a foe is entangled, the swamp kraken attempts to incapacitate its prey. Only after they have stopped resisting is the prey dragged into the water for consumption. Tentacles can reach 2" from the shoreline of the body of water where the swamp kraken dwells. They may simultaneously launch their attacks from a region of up to three adjacent water-filled map squares.
Because the bane's body typically remains concealed beneath the water—characters can only engage the swamp kraken's tentacles in combat. Any time a tentacle is shaken or wounded, treat it as severed. Reduce the number of tentacles available for attack on later rounds by the number of severed tentacles.
Any round where the swamp kraken has no tentacles available for attack, it attempts to flee from the fight—most commonly by burrowing beneath the bed of the body of water or swimming away from its foes.
Wild Card: Swamp krakens are considered Wild Cards.

2 comments:

  1. It appears that the last two paragraphs belong to the scarabs instead of the swamp kraken.

    ReplyDelete
  2. Whoops! Thanks for the catch. I'd Copy and Pasted from that blog post in order to grab the stat-box formatting. Apparently, I was insufficiently thorough in my deleting. That's now been fixed.

    ReplyDelete