The Arms of Erdrick

Now that I've finished documenting every major location in the original Dragon Quest trilogy for The Saga of the Ortegids, my next priority is going to be statting up a few magic items from the games. I've used them plenty of times in my campaigns, but it's high time I got something written down somewhere. I'm going to make a series of posts detailing some key items from each of the first three games, but I think it warrants a separate post for the Arms of Erdrick - the equipment used by the legendary warrior Erdrick the Aliahanian, a member of the Ortegid Dynasty and subsequently passed down through several generations of his successors. The equipment appears in each of the first three games, typically as the strongest equipment available - in the first game it's mainly just that it has the best stats, but later entries would establish additional perks and abilities of each item, which have been fairly consistently applied in later appearances, and it's these that I'm primarily basing my renditions on.

Optional Rule: I should note that in Dragon Quest I, carrying an amulet belonging to Erdrick is considered acceptable proof that you are descended from his line. Based on this, and the fact that in DQ3 the equipment is only accessible to the main character, you may wish to allow only PCs with the Ortegid Scion background to attune to these items. In a tabletop RPG with multiple players, this would limit their utility and may be unfair to players playing non-Ortegid characters, especially if they would mechanically benefit from the items. If the only Ortegid in the party is a wizard, it's not very fair if the fighter can't equip items designed for more martial characters, for instance. Thus, I've made this an optional rule for if you care about authenticity.

Cynebrand, the Sword of Kings

Artifact

The sword Cynebrand was forged by Erdrick the Aliahanian himself from orichalcum - a rare and nigh-unbreakable metal, so hard that it can only be shaped and formed using advanced techniques known only to a select few. This in and of itself makes it a weapon of considerable power.

When wielded by a character that has not attuned to it, Cynebrand behaves as a +2 longsword; additionally, due to its unique construction, it cannot be broken or bent by any nonmagical means. The latter property is a physical property of orichalcum and not an enchantment; thus, it will behave as such even if subject to anti-magical effects.

However, in the hands of a trusted wielder who understands and masters the blade, Cynebrand posseses additional magical powers. If used by a character that has attuned to it, Cynebrand instead behaves as a +3 longsword. If the wielder is also attuned to the Shield of Heroes and the Mail of Erdrick, as an action, its wielder can hold the sword in front of them to call forth a thunderclap that shakes the earth with the effects of a thunderwave spell at a spell save DC of 10. This can be used three times per long rest.

Haelescyld, the Shield of Heroes

Artifact

Originally carried by a legendary hero of ancient times, this shield was swallowed by the earth after his death in battle. Centuries later, Erdrick retrieved it from the depths of the Nailmark, the vast cavern formed when Zoma, Forbidden God of Death, dug his way into reality in the God-War. Now dubbed Haelescyld, the Shield of Heroes, it protects the user against magic.

When wielded by a character that has not attuned to it, Haelescyld behaves as a +1 shield. When attuned, it instead behaves as a +2 shield, and grants the user Resistance to fire and cold damage. If the wielder is also attuned to the Sword of Kings and the Mail of Erdrick, it also gives the user Advantage on all saving throws against magical effects.

The Mail of Erdrick

Artifact

This suit of armor was forged by Gaius, god of fire and the forge, as a favor for Rubiss, the goddess of life and creation, who in turn gave it to Erdrick as a token of thanks after he freed her from a curse of imprisonment put on her by Zoma, her twin brother and equal and opposite in power. In addition to its legendary resistance, it is wound with potent healing magics.

When worn by a character that has not attuned to it, the Mail of Erdrick behaves as a suit of +1 plate armor. It is forged from adamantine, which causes critical hits against the wearer to be treated as regular hits instead. When attuned, it instead behaves as a suit of +2 plate armor. If the wearer is also attuned to the Sword of Kings and the Shield of Heroes, it also allows the wearer to heal one additional hit die of damage, plus their Constitution modifier, when healing during a healing surge or short rest.

Modules As DM Screens

As ridiculous as this will sound, this idea came to me in a dream. It was really just a minor detail of a dream I had the other night, but it was one that stuck with me, because I woke up thinking that it would actually be a pretty brilliant idea. Why not publish modules in the form of DM screens?

There's plenty of discussions out there in the RPG community about the ideal form for published adventures and modules. How much text is too much? What's the best layout and organization? How do you efficiently describe a room with all the details you want to impart to the players without getting bogged down in flavor text? I don't really have a good answer to this myself. As long as it's something I can use effectively at the table, I'm not picky. But I realized that you could pretty easily pack all the important information for a small module into a DM screen.

There are definitely some advantages I can see. A DM should be able to reference any information on their screen at a glance, so by printing the module on the inside of their screen, you minimize flipping back and forth through a book to find what you need. Furthermore, since a DM screen is already used to hide information from players, you could just as easily put all the room keys and important plot events you don't want your players to know about there, and they wouldn't be able to see it. It would also make for an easily produced, inexpensive adventure, since it'd just be a single piece of printed cardboard rather than a full book. If you did it as inserts for a modular screen, it'd be even less production costs.

Due to the amount of information you'd need to include in a limited amount of space, this is probably something best suited for one-page dungeons and other small adventures, of the sort that could be completed in one or two sessions. The DM's side would include maps, room keys, stats for monsters and traps, and maybe a random encounter and/or rumor table. Me being me, I'd also put a space for notes that the DM could write in to customize the adventure, if they wanted to add their own features or change things to fit their setting or preferred style of play.

You could even use this to provide the players with easily accessible reference material too - on their side of the screen, you could have a map of the general area with sites of interest, expository material, lists of important NPCs and what the PCs would know about them, and such. That way, they could look at the screen to consult what options are available to them and what information they should know, saving time that would otherwise be spent asking the DM for reminders. You could also put inspirational art on there to help set the scene for the players.

The biggest obstacle I see here is that you'd need to make sure the player-facing information would be readable from across the table, which would likely require a larger font than on the DM's side, limiting the space that could be used for this material. But on the whole, I could see this model being used to produce an entire line of short adventures suited to pick up and play with minimal preparation, on the cheap.

Has anyone actually done something like this? If not, am I on to something? I've got a short dungeon percolating in my head, so maybe I'll try seeing how well this format works for it. But if it does, I think this has potential to be revolutionary.

Friday Encounter: Elvish Negotiations

Art by Zara Alfonso

This encounter is, admittedly, a bit specific to the Lunar Lands. It was in part created as a way to introduce players to how I run elves, and to introduce some exposition on what they're like in the setting. But it could also work in a setting where elves are of a similar quality (I make no claims that my take isn't heavily influenced by things like The Elder Scrolls, Dwarf Fortress, and Magic: the Gathering's Llanowar Elves). And it presents an interesting opportunity to use elves as antagonists - something I feel is all too underused.

Plenty of ink has been spilled on the trope of inherently evil races - if it's worth what it brings to the table, if it's too limiting, if it's necessary. But I don't see anyone talking about inherently good races. Let me ask you: when was the last time you've had random encounters where you had to fight elves, dwarves, or halflings? Humans show up as bandits plenty of times, but it seems like many DMs struggle to think of the traditional PC races in roles beyond those of helpful allies. To me, that's a missed opportunity. I think there's room for evil elves just as much as there's room for good orcs. If anything, elves should be antagonistic to the party more often - not only are they traditionally aloof and disdainful of other races, there's plenty of literary precedent in tales of the fair folk, with whims and customs utterly alien to those of humans, to say nothing of the Mirkwood elves in The Hobbit, who are just as dangerous as the goblins of the Misty Mountains. So let's forget about Legolas for a moment, and explore an encounter with elves that might not go so comfortably for the party.

Elvish Negotiations

This encounter is best used in a wilderness setting, preferably in a forest. If you wish to use it in other environments, you may wish to make adjustments to fit the terrain.

The party should come across a clearing where a band of elves is harrassing some human woodcutters. There are three men tied to the tree with animal sinews, surrounded by six elves holding spears to their throats. Another elf, Misleikkuri, stands overseeing them, his arms folded and an imperious glare fixed on the woodsmen.

If questioned, the elves will explain that the woodcutters were caught tresspassing near an elven glade and felled a few trees. The woodcutters insist that they did not know the lands belonged to the elves, but the elves refuse them any mercy. In fact, they are prepared to subject them to a slow and torturous death by sawing them in half with a dull blade, one by one, citing that it is what they did to the trees. After they are dead, they will tan their hides, devour their flesh, and sharpen their bones into knives. The elves show no emotion about this, viewing it as perfectly natural and relating it in as casual and nonchalant a matter as an elf's way of relating anything can be so called.

A DC 10 History or Religion check will reveal that elves commonly view the trees as their gods and ancestors, so killing one is viewed as a grave transgression. A character who grew up around elves (usually if they themselves are an elf, but not always; eg. an elf raised among humans would not necessarily know this) will know this automatically.

If the PCs attempt to bargain for the lives of the woodsmen, Misleikkuri will accept a deal. He will accept their ransom at a rate of 500 GP's value per man - he sees such foolish and short-lived things as humans as little more than commodities, and will barter them as such. However, he will not accept the payment in coinage, as the elves have little use for the shiny metals of humans. Mundane items will be accepted at their value in GP, uncommon magic items at a rate of 100 GP each, rare magic items at 200 GP each, very rare magic items at 300 GP each, legendary magic items at 500 GP each, and artifacts at 1000 GP each.

Additionally, the PCs can attempt to haggle with Misleikkuri to lower the ransom on a given man. A successful DC 15 Persuasion check will cause him to lower that man's ransom by 100 GP; elves have Advantage on this check, as Misleikkuri is more trustful of them than humans. However, if this check is failed, Misleikkuri will grow frustrated with the negotiations, and his attitude will grow more hostile. If any items he is offered are made of wood, or another plant product, he will also be insulted, as their existence is proof that a tree was felled to make them.

If Misleikkuri is insulted three times (either through a failed check, an offer of wood, or if the DM feels such a response is warranted to the PC's conduct - keep in mind, this should be warranted from the perspective of a being who thinks of himself as higher and above human morality, and who sees humans the way we see cattle), he will call off negotiations. Any woodsmen the PCs managed to free before this will be allowed to go, but any that remain will be condemned to death. For folkloric resonance and to give the PCs information to strategize with, Misleikkuri should make it explicitly clear, if the PCs enter negotiations, that he will only let himself be insulted three times. Each time he is insulted, he will remind the party how many attempts they have left.

If the PCs attempt to free the woodcutters by force, or if they continue to try and get Misleikkuri to release them even after he has ended negotiations, he will order the elves to attack. They have the stats of a scout; additionally, Misleikkuri himself has the stats of an archer (see Volo's Guide to Monsters). In addition to the six elves in the open, there are three additional scouts hidden in the trees; they are behind three-quarters cover, and any ranged attacks made at them from the clearing are made at Disadvantage.

Background: Fated Hero

 

If you've been following my blog, I don't think it should be any surprise to you that I love backgrounds. They're one of the best ideas 5e ever had, offering customization options for characters that add flavor, and most of the features are narrative-focused, opening up new avenues for characters to explore and interact with the world rather than just giving them mathematical bonuses. That being said, I do think that there's room for background features to introduce mechanics of their own. There's some fun things that can be done there. As a bonus, they provide an avenue to mechanically represent new character concepts without having to write a completely new class - let's face it, D&D has more classes than it has archetypes for those classes to fit as it is. Here's one such example.

This started out as a post for The Saga of the Ortegids as a background to represent a PC being a member of the Ortegid Dynasty - that is, the legendary family that includes (but is not limited to) the main characters of the first three Dragon Quest games. The idea of a legendary hero is a common feature in contemporary Japanese fantasy that tends to be a direct reference to the player characters of the Dragon Quest games in the same way that the "demon king" archetype is the result of porting the video game conceit of a final boss into narrative media. Usually, the two are linked, with the hero often being prophecized to defeat the demon king. In some stories, they're the only one physically capable of doing so, and in some, the hero and the demon king are both metaphysical roles passed down cyclically every generation, with their struggle serving to keep the balance of good and evil. These aren't mutually exclusive.

Notably, however, the heroes of the Erdrick Trilogy are not prophecized chosen ones - that trope comes mainly from later games. In the first three games, they're all people who volunteered or were volunteered to deal with a pressing threat, but from what little exposition we get, it appears that this is because they feel it's the right thing to do and/or because they're following the example of their ancestors, not because of a mandate from higher powers. With this in mind, in addition to the fact this project is deliberately eschewing any artifacts of the medium of video games, you might be wondering why I'd try to represent it.

Well, heroes being elevated in some way among common people is something we see in fantasy and mythology in pretty much every culture and era, so I think it can still work. Drawing more than a little inspiration from The Saga of the Volsungs, the lore for my version of the setting is this: when Baramos, the Sorcerer-King of the Southlands, was told by an oracle that he was doomed to be slain by the line of the Aliahanian warrior Ortega, he had a curse placed upon Ortega's kin, such that all would be blessed with incredible strength, wit, and bravery, but simultaneously doomed to misfortune and tragedy, attracting powerful enemies and more often than not dying by the sword. This is why they're so often capable of great heroic deeds and faced with a need to perform them, not because the world works like it's a video game.

However, while plotting out this background, I realized that it'd also work very well for a variety of names in fantasy and folklore - the Volsungs, but also the heroes of ancient Greece, subject as they are to the whims of the gods, Samson, and even more modern examples like Elric of Melnibone. To that end, I've submitted it as a setting-agnostic background. Feel free to tweak it for your own purposes.

Fated Hero

For whatever reason - be it a curse, a prophecy, or merely attracting the eye of the gods, you are capable of great deeds, but your fate is a plaything of higher beings. You have the potential to become a figure of renown through heroism, but the same fate that guides you toward greatness could just as easily bring about your end.

Skill Proficiencies: History, Religion

Languages: Celestial

Starting Equipment: A token of your divine favor, a set of common clothes, an explorer's pack or a dungeoneer's pack, and a pouch containing 15 GP.

Feature: Gigantic Melancholies and Gigantic Mirth. Once per long rest, you can beseech the gods to grant you their favor in performing a great task. If the DM agrees that the roll at hand is a suitably heroic deed, you make the roll with Advantage. However, your fate is bound in both directions. Each time you use this feature, the DM will make a note of it, and can inflict Disadvantage on any one roll they choose in the future. Additionally, if you roll a natural one on your reroll, even if the original roll was higher, you must take it, as the gods are punishing you for your hubris in calling upon them so wantonly.

Variant: Ortegid Scion. This variant can only be used in a Saga of the Ortegids campaign, or one where the setting also features a family of heroes cursed to tragic fates. You are a member of some branch of the Ortegid Dynasty - possibly a prince of one of the three Ortegid kingdoms, a distant cousin, or the product of a one-night stand in foreign lands. In addition to the Gigantic Melancholies and Gigantic Mirth feature, you also have the Inheritor feature from Van Richten's Guide to Ravenloft (if you bring up your heritage, you will get an idea of the local reception of your ancestors and how you can be expected to be treated in turn). You must be a human or a half-race of human parentage, and of at least partial Aliahanian ancestry, to use this background (though the Ortegids have traveled throughout Erdland and Torland and their descendants can be found in surprising places).

Friday Encounter: Star Metal

This encounter can be used anywhere outdoors, but probably has the most potential in a wilderness environment relatively close to civilization.

One way or another, the PCs should catch sight of a falling star, shortly before they hear the sound of a loud crash in the distance. If they investigate this site, they will find a large, smoking rock lying in the middle of a crater amidst flattened grass and toppled trees. A meteor has fallen here!

A DC 10 Nature check will determine that meteors often contain iron. A DC 10 Religion check will reveal that meteoric iron is considered a gift from the heavens in many cultures - and a DC 10 Arcana check will reveal that this iron, known as star metal or thunderbolt iron, is prized for having magical properties beyond that of earthly iron.

If the iron is mined from the meteor, there is about 60 pounds' worth of metal that can be obtained. Objects such as weapons and armor can be smithed from this metal, at a rate of one pound iron to one pound of the final product (for example, it could be used to make a single set of splint armor, 10 shields, 20 longswords, 60 daggers, etc.). Any weapons and armor made from the iron are treated as +1 items of that type; additionally, creatures wearing armor made of star metal have Advantage on all spell save DCs, as the iron is resistant to magical effects.

However, this equipment cannot be made without the use of a forge and a trained blacksmith. The party may need to transport the meteor to a forge if they wish to make use of its bounty. The meteor weighs 150 pounds in total and is cumbersome to carry; a bipedal creature carrying it may not use their hands for any other action while hauling the meteor. It can be carried on a cart or sled, but this may slow travel if it weighs the vehicle down. Getting the meteor to a blacksmith willing to work it may well be a quest in and of itself.

A character with proficiency in smith's tools can forge an item from the iron at a rate of one day of work per item, but they must have access to the proper tools as well as a forge and anvil in order to do so.

Keep in mind that things might not be easy even after taking the meteor to someone who knows how to work it. The blacksmith will likely demand compensation for such a task, and may even want to keep some of the iron for themselves, especially if they aren't familiar with the party and no reason to trust them. Furthermore, if word spreads about the star metal (such as if the PCs return to town to look for someone who can work it or help transport it, or if they show up in a settlement with the meteor in tow), they might attract the attention of thieves, or the feudal lord might lay claim to the iron if the meteor fell in his domain.

For that matter, the fair folk are repelled by iron, and they would have good reason to keep a source of it hidden so that it cannot be used against them. If the meteor is not collected in 1d4 days, a fey lord in the area will place a spell over it to make it invisible to mortal eyes, while fairies will try to waylay anyone who goes near the site - or accost them, if they must.

Saga of the Ortegids: Eras of Adventure

My default setting, as it were, for The Saga of the Ortegids would ground the action many generations after the events of Dragon Quest II - enough time for the setting to be a blank slate for the DM to run as they pleased, without needing to worry about canon characters or events impacting their plans, and for it to make sense that the Worldtree would have grown to the point where travel between Erdland and Torland would be possible in order to make full use of the material and its potential. However, there's a number of other eras in the setting's history that could make for good campaigns. Below, I've listed six - three focusing on Erdland, and three on Torland - presented in chronological order.

Art by Ted Nasmith

1. The Journeys of Ortega

Of all heroes of the Ortegid dynasty, their progenitor, Ortega, is the one we know the least about. What little overarching plot Dragon Quest III has is driven by him - he's a legendary warrior of Aliahan and the father of the protagonist, who in turn would become known as the legendary hero Erdrick. Ortega feared that the sorcerer-king Baramos would pose a threat to his family, and set out to kill him shortly after the birth of his child, but was never heard from again.

Your motivation in DQ3 mostly boils down to avenging your father and/or living up to his legacy, and he's mentioned at a few points throughout the game, even if his in-person screen time is minimal. We know a few places he went and a few characters he encountered, but much of his adventures are shrouded in mystery. The recent HD release added new cutscenes detailing more of Ortega's adventures, which I personally feel was a mistake - he had a lot more mystique when you only heard of him from NPCs' accounts and had to put the pieces together yourself. But the broad strokes we get could provide a good basis for a campaign.

In this campaign, the PCs would take the roles of companions of Ortega on his journey to the Southlands. Of all of these, this is the era that would probably have the most appeal to players already familiar with the Dragon Quest series, since it's grounded in events directly discussed in the games and would involve locations visited there. However, there's enough empty space in what we know to allow for DMs to add new quests and locations. The main drawback is that the presence of Ortega shackles things to canon events somewhat, which could lead to railroading and remove the sense of danger if players know he has to reach his canonical fate. Furthermore, you'd need to figure out how Ortega himself would be handled. While I personally don't have an issue with DMPCs, it's all too easy for them to turn into invincible plot devices that take all the glory from the actual PCs if run poorly. One way to get around this would be for Ortega to be run by a player, or for a PC to take his role in the story instead.

2. The Reign of Erdrick

Early on in DQ3, after returning his stolen crown, the King of Romaly offers to hand the throne over to you. You can accept the offer and play out a short scene of being the king and surveying your domain, but ultimately, you have to leave the position behind if you want to continue with the game. It's definitely a fun and memorable segment, though - and since a big part of Saga of the Ortegids is reframing the mechanics of the Dragon Quest games in a more realistic light, I think this could be made into a part of the setting's history.

Perhaps Erdrick did accept the crown of Romaly, but instead of abdicating right away, he sat on the throne for some years afterward before ultimately deciding to return to a life of adventure. If that's the case, we now have a few years' gap in our timeline that a campaign could take place in. Since there aren't any major changes to the world's status quo before and after this quest, we can assume that Erdrick's rule was a fairly peaceful one - but who knows what could have been happening behind the scenes?

This option would probably work best for a campaign taking place entirely or predominately in Romaly, with PCs being Romalian citizens during the reign of King Erdrick the Aliahanian. There are a number of directions it could be taken - it could simply be a backdrop for whatever adventures the PCs concern themselves with, but there are opportunities for storytelling if the DM does want to involve the royal court, too. After all, this would see a weak but familiar (and no doubt easily controlled) King cede the throne to a foreign barbarian, with no ties to the existing power players and no way of predicting his actions - and there would surely be factions with different opinions on the matter that PCs could get tied up in, if noble intrigue is on the menu.

Art by John Howe

3. After Baramos

After Erdrick's party departs for the Pit of Giaga and enters Torland, we don't hear from Erdland again. But it's a pretty expansive setting with many interesting areas and cultures, as I've blogged about extensively, and it would be a shame to let it go to waste. What was going on on the surface while Erdrick was saving Alefgard? This campaign would address that question.

This campaign would deal with the repercussions of a few major shakeups in the setting. Baramos has just been slain, and that leaves Gondo - a pretty major kingdom, and a strategically important one - without a ruler. This could lead to a power vacuum with multiple factions seeking to take control. Consider how it's implied that Baramos himself overthrew the previous rulership. There could be loyal subjects of the sorcerer-king hoping to continue his legacy going up against the downtrodden natives looking to finally liberate themselves from tyrannical rule, mixed in with other kingdoms hoping to swoop in and take some of the land for themselves, or install a ruler they can trust to serve their interests. At the center of all this is a pit known for spawning monsters, from which an ascendant dark god has just issued a threat to take over. Some factions would likely want to make sure this threat is controlled as soon as possible, and see themselves as the best ones to do it, while to others, it would be an obstacle to their ambitions that they would need dealt with before they enact their plans.

There are other potential plot hooks here, too. For one, Gondo wouldn't be the only nation in crisis - consider also that Zipangu has had its own draconic ruler killed, and that she was able to keep the populace controlled through fear and fanatic devotion. What happens when that centralizing force is taken away? Additionally, upon hearing Zoma's challenge, the King of Aliahan falls into a deep sense of malaise and hopelessness. This could itself provide issues to the kingdom if the ruler is no longer interested in ruling, and some factions both abroad and from within might well see their chance to strike when he is at his weakest.

4. The Rise of Lorasia

When we leave the protagonist of Dragon Quest I, he has set off to establish a new kingdom of his own in a distant land - and when we pick up in the sequel, the continent-spanning empire he founded has been split into three kingdoms ruled by his heirs. That gives us a lot of ground to cover, and it's one that would be a perfect fit for certain campaign models.

In this campaign, PCs would be Alefgarder settlers who followed Aleph Wyrmbeorn to Lorasia, then an unsettled and disjointed wilderness, in the early days of his kingdom, and would play a role in shaping its fate. This would be an exploration-focused campaign - PCs might be tasked with surveying the land, establishing new trade routes, and dealing with locals, who may or may not be friendly. In other words, it'd work very well for a sandbox campaign, perhaps something like West Marches.

There would also be room for domain-level play - an empire of the size of Aleph's would surely need regional power centers in order to project power effectively, and PCs could take the roles of dukes, counts, and barons carving out their own feudal demesne in the new kingdom. This in turn provides a good prospect for PCs to advance their place in society - they might start as peasants dreaming of a better life or landless second sons of nobles back home, but through service to the new King could be rewarded with domains of their own.

Art by Chris Achilleos

5. The First Kinslayer War

However, as great of an empire as Aleph's was, we know that it didn't last long after his death. The three Ortegid kingdoms of DQ2 are all descended from those that the empire was split into after the land was divided among Aleph's three sons. We have little in the way of details as to what happened between then and the present day of 2, but any student of history can tell you it probably wasn't a time of peace. The division of a great empire has often led to civil war, with disparate factions competing to reunify the bygone kingdom and take back territory from their neighbors. Alliances would constantly be made and broken, and the map could drastically change even from month to month.

A campaign set in the heat of such a period could have many opportunities. PCs might be in the service of one of the three kingdoms, taking part in battles against its rivals or conducting more clandestine operations in service of their goals. Alternatively, the chaos of the war could serve as a backdrop for their adventures - and there's plenty of ways a party could take advantage of the instability of the situation and the diverted attention of the authorities to their own benefit. Battles between the warring states could form obstacles the party would have to navigate around, so as to get from one point to the other without being caught up in the crossfire.

One way to really make this campaign fun would be to run it as a direct sequel to a campaign set in the previous era, with the same group. First, players would be involved in the establishment of the Ortegid Empire, carving out their own sphere of influence within it. Then, you jump forward a few decades to take a look at those domains ravaged by civil war! The PCs from the previous campaigns could become NPCs, while the strongholds they built could be revisited. This would be a great way to build more attachment to the setting if the players had a role in shaping it, as well as making for a living, dynamic game world where the choices players made in one setting impact the next.

6. The Second Kinslayer War

So here's a bit of trivia for you.

The ending for Dragon Quest II is a pretty conventional one. The evil is defeated, and everyone goes home and celebrates, roll credits. This was a time before storytelling was really a priority in video games. But in an interview, Yuji Horii described the ending we were going to get, had his original plan been implemented.

In it, there's a key difference to the final game - in order to defeat Malroth, the Prince of Samartoria (or Cannock - I'm aware that he's never actually been called that in English, and I'm stretching the rules I set for myself a bit in using the Japanese name for the country rather than the city, but I want to be consistent) must sacrifice his life. This has some interesting parallels with how Malroth was summoned through a willing human sacrifice, and it fits in pretty well if you are to interpret this as the Spell of Embodiment being dispelled through the same process. Anyway, in this version, the Prince's sister is told of his fate when the Prince of Lorasia travels to Cannock to celebrate their victory. Mad with grief, she blames the Prince of Lorasia for her brother's fate, and stabs him to death when he retires to his room.

This was scrapped because they didn't have enough disk space for such a cutscene, and they decided in retrospect it would make for a really unsatisfying ending. And I suppose, from the perspective of a video game, it would. Plenty of gamers would be frustrated to sink many hours into a game only for their character to be assassinated just before the credits. However, it's also something straight out of a Greek myth or a Norse saga. And, me being me, that alone is enough to make me prefer it over the ending we got - especially when this project draws heavily on myths and oral tradition for inspiration.

A potential campaign could be set immediately after the events of DQ2 - but using this ending instead. Such an act would have plenty of interesting consequences. Lorasia would surely want to take action if their crown prince was murdered at the neighboring kingdom's capital, and if we presume that Lorasia and Samartoria fought a war in the past, this could ignite old tensions between them. At the same time, both kingdoms just days ago were fighting a war against Rhone, and they might be in a precarious position, their forces exhausted and morale strained. Furthermore, you have Moonbrooke in the middle - surely they were hoping to rebuild their destroyed capital and get things back to normal following the defeat of Rhone, only for things to get even worse. And Rhone itself would be dealing with the immediate fallout of the death of Hargon, leaving them with a succession crisis of their own.

The PCs would be caught in the middle of all of this, as the celebrations that one war is over quickly turn to dread over the new war just beginning. They could ally themselves with any number of factions springing up in the aftermath, or try to get by in the middle of a rapidly combusting powder keg. In addition to the many potential leads to pursue, this is a campaign that would offer fanservice for players familiar with the series, taking place in the direct fallout of one of the games and with opportunities for recognizable characters, locations, and items to make an appearance, but there's still room for the PCs to be important. Any campaign set in an existing universe risks having the PCs be overshadowed by canon characters, but if two of the three heroes of DQ2 are dead and the Princess of Moonbrooke is busy trying to hold the remnants of her people together, they aren't going to get in the way.