MarkB
Legend
This one's a big 'meh' for me, I'm afraid. If I want to create a unique 'hook' or backstory for a monster in my campaign I'll do it - but it'll be a hook tailored to my setting, and probably of little use in anyone else's.
In a toolkit system like D&D, these story-based creature origins are close to useless - a DM may find, once in a long while, that the story meshes with his campaign to the extent that he can drop the creature in with minimal modification, but once he's done so, that's pretty much it for that creature. Given its unique origin, he can't drop others into the same campaign, nor can he use the same backstory when adding the creature into a new campaign for the same players.
And if the DM doesn't happen to agree that this should be a unique monster - if he wants whole groves of angst-free dryads, or families of redcaps preying upon passing travellers - then the write-up offers him nothing to build upon.
Giving a creature a specific, unique backstory is something best left for a module, not the Monster Manual.
In a toolkit system like D&D, these story-based creature origins are close to useless - a DM may find, once in a long while, that the story meshes with his campaign to the extent that he can drop the creature in with minimal modification, but once he's done so, that's pretty much it for that creature. Given its unique origin, he can't drop others into the same campaign, nor can he use the same backstory when adding the creature into a new campaign for the same players.
And if the DM doesn't happen to agree that this should be a unique monster - if he wants whole groves of angst-free dryads, or families of redcaps preying upon passing travellers - then the write-up offers him nothing to build upon.
Giving a creature a specific, unique backstory is something best left for a module, not the Monster Manual.