Creature Preview: Wurfrur and Vocoeur

The blink dog and the displacer beast are two of the creatures I most remember falling in love with when I started playing D&D. Good-aligned extradimensional dogs ? Predatory phasing cats? An ancient enmity between them? Sign me up!

An interesting thing about blink dogs is that they’re sapient, meaning they’re not only intelligent but they have their own language. In AD&D, displacer beasts didn’t speak, but they gained that ability and an evil alignment in the 3e days, both of which they retain in CORE20. When I shared the ohoomwi, I mentioned that CORE20 is making a point of having all sapient creatures named according to what they call themselves, so that CORE20 names the blink dog as the wurfrur and the displacer beast as the vocoeur. But the naming of the vocoeur actually has an interesting side story to it.

Back in the early 2000s when Wizards of the Coast opened up D&D to third-party development by way of the Open Gaming License, that license called out elements of so-called “Product Identity” that were declared absolutely off-limits for third-party products. If you wanted to make material compatible with D&D using the Open Gaming License, you couldn’t use the name of the game or the titles of the core rulebooks, or the names of a bunch of planes, or a dozen specific monsters — including the displacer beast. 

Thankfully, with CORE20 built around the Creative Commons version of the Dungeons & Dragons SRD rather than the OGL version, the limitation on using the displacer beast no longer holds.  But what I and a lot of other people found hilarious about the displacer beast being in WotC’s list of “we own this and are protecting it so you can’t use it” monsters in the first place is that the displacer beast was stolen by Gary Gygax when he created it for the AD&D Monster Manual. As Gygax himself talked about openly, the creature’s appearance and abilities were lifted from a short story by science fiction author A.E. van Vogt, in which the creature’s name was Coeurl — with both those names giving the vocoeur their CORE20 identity.

(Click on the stat block header below to download the full stat block in PDF.)

Creature Preview: Peryton

You know you’ve done a good job at bringing a horrifying monster to life when your developer tells you, “Please don’t ever use this in a game I’m playing.”

A feral magical predator, the peryton is known for their predilection for feeding on hearts — and for the fear that instills in characters who fight them even, before the fight begins. They are a creature both old (in game terms) and new (in real-world terms), having been around since the AD&D Monster Manual. But they were sourced not from ancient mythology (as many of the creatures of early D&D were) but from Jorge Luis Borges’ Book of Imaginary Beings, written in 1957. 

The peryton’s hunger for hearts has traditionally been mostly flavor, with versions of the creature from AD&D through 5e detailing how a peryton will bite out the heart of a hero only once that hero is dead. But for CORE20, I thought it would fun (for the GM; players’ opinions may vary) to tie the peryton’s heart harvesting to the mechanics for death and dying — allowing the peryton to take a fallen character from dying to dead with fatal speed.

(Click on the stat block header below to download the full stat block in PDF.)

Creature Preview: Ohoomwi

I am digging into a final pass through a bunch of new creatures, getting ready to add those creatures to the CORE20 Playtest Creature Package v1.1 update. While that’s happening, I thought I’d post a few choice creatures here, giving folks a playable preview of a few favorite monsters of mine, and offering a smattering of thoughts about what goes into a CORE20 monster, design-wise.

•

The giant owl has been a mainstay of campaigns since the AD&D days, where they were noted both for their ability to surprise prey 83 percent of the time, and for being intelligent creatures who spoke their own language. But that second part has always raised the question for me of: Why does a creature with their own language not get to use that language for the name others use to refer to them?

For me, the answer in a very broad sense is a) lazy writing, but also b) colonialism. Because the colonialist mindset lurking at the heart of D&D via its evolution from tabletop wargames works very much around the idea that the fantasy realm is human-centric, and that humans decide what place all other creatures have in “their” world. And though the names of classic D&D monsters are absolutely the least of colonialism’s evils, they’ve always nagged at me, so CORE20 has taken a shot at fixing them.

As with the eapachni (from the giant eagle) in the first version of the CORE20 Playtest Creature Package, the ohoomwi is understood to be named from their own language, as is true of all other sapient creatures. When coming up with the name (because I don’t speak Ohoomwi, unfortunately), I wanted something that not only had an owl-like echo to it but felt intrinsically non-European. At some point, I tripped across a reference to “hohomisiw” as meaning “owl” in one of the Cree languages, and from my childhood, I remember “ukpik” (which I learned as “ookpik”) as the Inuktitut word for the snowy owl, and “ohoomwi” fell out from that.

(Click on the stat block header below to download the full stat block in PDF.)