This guide has been updated! The original DME rules allowed more latitude. You can still find the old post here.
1. Experience.
The best tool in your arsenal is experience. If you are new to judging 4E and/or LFR, you probably should not be using DME to adjust difficulty. This is because 4E and LFR can be ‘swingy’, in that one encounter can be really easy for a party and the next really hard. This is a factor of the way adventures and encounters are built, as well as the way parties are built and how the die rolls can distribute over time. An encounter can seem really hard when the monsters have high damage and the party lacks a healer, or when they have high defenses and the striker rolls poorly for several attacks in a row. An adventure might deliberately start with a really hard encounter, then tone it down for an easy encounter, then finish with a moderate encounter. The more experience you have as a DM, the more you can recognize these factors.
2. Know the Adventure
The more you understand how the adventure’s encounters tend to play, the better you will be able to know when DME is appropriate. Maybe the skill challenge is designed to be a strong social encounter because the next skill challenge is all about non-social skills. Adding in non-social skills in the first challenge changes that balance. Maybe the first fight uses minions and is really easy so that the players will feel good… and not be frustrated when they face a more denial-based encounter in the next room. One of the first cores, for example, has two pretty easy fights up front, using several minions. A DM might think the adventure needs tweaking. However, the last encounter can be very difficult depending on how PCs handle the bundled skill challenge and one of the foes. That final fight can be challenging enough to threaten a TPK for some tables. If a DM increases the difficulty based solely on how the first two fights play, they could be making a big mistake, using up vital resources too early!
3. Know the Party
DME is especially useful if you have a good understanding of the party’s capability. Understanding the roles they have, the skills they have, and their level of proficiency with the game is important. Understanding the style of play they prefer is important as well. Some players would appreciate DME that provides more RP. Some players are happy optimizing their PC and having a cakewalk and don’t want the DME to up the challenge level. Maybe the party just finished having a TPK in their previous adventure and now they sit down looking for a cakewalk, and you decide to up the challenge level…
4. Use DME Cautiously, With an Eye Toward Options
DME is best used carefully. Tweaking monsters by a level may seem by very little, but a missed daily power or two can have big effects over the course of an adventure. Plan ahead for how you can back out of DME changes. For example, if you increased several foes by a level and the party is having trouble, and the party likely knows the foes’ attack bonus or defenses, you could just reduce their HPs back to normal or even a bit below normal or change monster powers to refresh less often. Don’t forget tactics. Bad or great tactics are easily worth more than a level adjustment if done well. After all, just the simple choice to flank or attack a foe with/without cover is a difference of 2 on an attack roll. Combine with a marking penalty and you can be increasing/decreasing your monster’s chance to hit by 4!
What should you not do with DME?
1. Don’t automatically use DME to make up for a party being effective
An optimized party may or may not be a fun party. Your job is to ensure fun. If you see the PCs having an easy time, check with the players before increasing the challenge level. If they seem bored, you can likely adjust the challenge level. Be mindful of new players, however, as they may be riding on the coattails of experienced players and you don’t want to overwhelm them, if possible.
2. Don’t use DME to punish an optimized player
While severely optimized players can be un-fun (both for the table and for the DM), keep in mind that everyone is entitled to their own play style. If one PC’s optimization seems to be causing a problem for the whole table, talk to the player to try to reach a compromise. Or, ask the table as a whole if they want a higher challenge level. Trying to ‘punish’ the optimized player by increasing difficulty can be a big mistake if it ends up making the game too difficult for the other PCs.
3. Don’t use DME to issue a rules edict.
DME does not allow you to ignore core 4E or LFR rules. You are bound by the 4E and campaign rules at all times, including using the latest rules clarifications in the FAQ, errata documents, and CS (Customer Service) replies.
DME should also be viewed as being there for the benefit of players and the table. It isn’t for the benefit of the DM, other than the increased satisfaction of knowing the players had a great time.
4. Don’t overstep your bounds.
Know the limits of DME and obey them. Just as you expect players not to cheat, they expect you to understand and follow the limits imposed by DME.
Creating Adventures with MYRE
My attempt at a guide.
Teos, may I and other "reskinners" use this guide in our "reskin / re-imagined" documents, so as to explain and rate how much change our reskins our modifying the original scenario?
Teos, may I and other "reskinners" use this guide in our "reskin / re-imagined" documents, so as to explain and rate how much change our reskins our modifying the original scenario?
Absolutely. I would appreciate help with properly setting the levels of "Minor". "Moderate", and "Extreme", if those are even proper terms!
I've been thinking that we could also use a index thread that points out the various reskins for mods. Basically, a list of mods with any available changes as links to the posts/threads capturing those changes. The idea being, if you go to run a mod, you can see what others have done, cherry pick changes, run the mod at a really high level of fun. This is what I felt happened with the WiR mod, and it was great for me to have the benefits of what others had thought through.
Oh, and I'm fine with this ending up in either board. I put it here because the other one seemed specific to individual modules, while this thread is more general. No issues either way.
Teos
how big of a change would it be to change say a boss mob. just one of his capabilities...?? to provide flavor for those that have repeated the mod say 3 or 4 times...I like the capability that say a solo mob cannot be marked in any form (fighter, pally, swordmage, ranger, cleric, warlock, etc). true it may prolong the game a bit but ive had bosses that died in 1 round cause the players knew exactly what was needed to be done ( CORM1-1 ). So would in this instance be allowed that kind of change?
Is there a power that prohibits marks as well as curses and quarries which aren't marks? I hadn't come across it yet and it seems like an awfully powerful ability.
how big of a change would it be to change say a boss mob. just one of his capabilities...?? to provide flavor for those that have repeated the mod say 3 or 4 times...I like the capability that say a solo mob cannot be marked in any form (fighter, pally, swordmage, ranger, cleric, warlock, etc). true it may prolong the game a bit but ive had bosses that died in 1 round cause the players knew exactly what was needed to be done ( CORM1-1 ). So would in this instance be allowed that kind of change?
Off the top of my head, it would be a minor or moderate change, depending on the type of power. For a good example of a change, compare the creature in the first combat in the adaptable Menace of the Icy Spire to the creature it is obviously based upon - the power changes are very reasonable and do not affect the power level. That's a minor change, IMHO, even though several powers were changed.
If I were to take a boss and make a very different power, say, something that heals or your example that cancels a class feature, that is likely a moderate change. A lot of these are judgment calls. We can try to categorize changes roughly, but the nature of the game and of players is why the guide exists - it is really easy for something not to work as you intend it to work.
Not allowing a class feature to work may really rub players the wrong way. Think of the many LG mods that do things like prevent animal companions from coming along... a player is right to say "Why was I unfairly prevented from using part of my class capabilities?"
Aside from that, looking over the MM can show you examples of what powers are reasonable and unreasonable at different levels. Generally, an "always up" defensive power is pretty darn strong. More likely you will see a once per round immediate interrupt power, though these are also viewed as really strong. For your example, I could see an immediate interrupt that either redirects the mark to an adjacent foe (similar to the power of a goblin hexer) or a minor or move action to cancel a mark as an encounter power. Both seem to me ok, assuming you are removing a power of equal value. Remember, you aren't getting the benefit of WotC development teams, their playtesting, the module's author, the mod's reviewers, and the mod's playtests... thus, be ready to scale back on the fly or try this only after you have a really good sense of your options as a DM if this ends up annoying the players. For example, if it ends up being too strong, you could retroactively knock of 10 hp per use and have the player that is annoyed make a spot check with a low DC. You announce "you spot a trickle of blood coming out of your foe's mouth. You think they are paying for that capability with their own blood!"
The more you DM 4E and LFR, the more you gain a sense of balance and can feel out whether this is a minor change or may be something to which players could react negatively.
For example, the Arkanul changes I suggested include some fairly strong enhancements to combats. Giving a set of critters ropes for swinging allows them a terrific movement advantage, with little downside. It isn't even a power and requires no skill! That might be a moderate change or even extreme, except that the encounter is a really easy encounter. The final effect, in the context of that encounter, is just a minor change that greatly improves the fun without really changing the difficulty at all.
-====-
I really like the guide. I would add the following (unsure where to
do so, perhaps under extreme changes):
X. Guidelines for Extreme Changes
Outside of home play, extreme changes should follow these guidelines:
a) The treasure bundles, total experience, and gold awards must be
identical to those in the original module.
b) The number of encounters and the relative size of the encounters
should be as close to the original module as possible, as these are
carefully tested to ensure that the module falls within the suggested
play time of the module. This is less important in events and locales
where time is not an issue (single module events); in convention and
multiple-slot events this is a necessity as it interferes with the
players' ability to join in other slots.
c) The story awards MUST make sense within the scope of any extreme
changes--favors from NPCs must remain logical and flow within the
storyline and roleplaying of the changed module.
d) It is *highly* recommended that if you do decide to make extreme
changes outside of use for a home game, you do so only with groups of
players that have already played the original module as written with
another character. In this way, the players are aware of how the
original module is played, in the event that in your changes you have
altered something which will be important in a future module. There
are several modules which contain NPCs and encounters that appear to
be benign and seem insignificant in the course of the individual
module but which may well be key to future modules. In this manner,
players know what their characters SHOULD have encountered and can
therefore make adjustments in sequel modules their character plays in
the future to reflect what they WOULD have experienced with that
character had they played through the original module.
(For D... I'd include some examples, but I'm uncertain how spoilers
work on this list. Needless to say I believe that *most* modules with
this sort of element have some obvious hints and thematic elements
which are particularly obvious setups for something in the future that
aren't associated with story awards or even potentially the encounter.
Off the top of my head, I can think of two mods with RP encounters
with characters who have little bearing on the individual module's
story awards but whose nature is ominous, curious, or otherwise odd
and foreshadows possible future involvement. This indicates to me
that there may very well be other elements essential to future modules
that aren't as obvious.)
--
Scott Roberts
General Manager
The Gamer's Gambit
Teos
Thank you, Teos, for writing this up.
I'd think that the (or at least a) primary reason for using DME to change a mod would be to mix it up for replayers...
Regarding the second post.
I'd think that the (or at least a) primary reason for using DME to change a mod would be to mix it up for replayers...
I'll mention that. My own bias is against replaying. No matter what a good DM does with a mod to make it different, a replay generally is, to me, sub-par. I look for really good engaging experiences, a story that immerses me and my PC, compelling heroic goals, and continuity of plot across mods. With reasonable DME, there will always be some repetitive feel... getting a few "oh, nice change" moments is seldom going to make the mod as fun as a new mod. (Any mod, replay or not, can be fun if you play with a great table, of course, but then the fun would just be better for having a new experience).
I do realize that many people like to replay. I'll make a mention.
Teos
Resistances are supposed to be relatively rare in heroic tier. Adding multiple resistances to most of the monsters for the entire mod should be a no-no. Find some other way to communicate your fire goblins or at least toss in a few non-fire goblins.
How about this one?
Sounds very non-fun! I've added the following to the end of the new post:
D) The changes should not unreasonably increase the difficulty of the encounter. It can be appropriate to make an encounter harder or easier, but this can be very hard to estimate and change correctly. DMs that use DME to adjust monster abilities or encounter difficulty should be ready to pull punches if the adjustment does not play out as intended. Few things will irritate a player more than a perception of a change being unfair, especially if it results in character death.
And now one to mine.
I do look forward to guidance from above. I'm lawful that way!
Additional comments about the intent of DME and coming guidelines.
Take part in the Regional Flavor DME Challenge and help increase the flavor of LFR!
The CCG 1.9 should come out, widely expected to clarify DME.
When that comes out this guide will either shift its focus (getting a major rewrite) or add on additional ideas on DME within the revised context and that of the MYRE concept.
Even some of the examples under the "Minor Changes" category might have to be removed.
Now that CCG 1.9 is out, greatly limiting DME, it looks like we will need to change the focus of the Quick Guide.
Even some of the examples under the "Minor Changes" category might have to be removed.
My take on this would be that the side that originally pushed for DME lost, and the advocates of "consistency of play" won. By and large, it's tough to say that DME exists any more in anything but name.
The changes can be summed up in one quote from the new section: "The adventure should be essentially the same no matter who runs it."
(Contrast with what one campaign admin said when the concept was released: "[DM Empowerment] is stressed to specifically defuse the notion that the RPGA is striving for some mythical 'consistency of play' within an adventure from one table to the next in its Living campaigns.")
Several cardinal examples that campaign staff have used in the past for how DME should work (replacing a creature with four minions of the same level or a creature of another type; replacing a combat with a skill challenge when appropriate) are explicitly disallowed. Indeed, it wouldn't surprise me if the specific example of what is not allowed (changing the color of a dragon) was directly recommended by campaign staff in the past.
This isn't a clarification of DM empowerment; this is a flat-out disavowal of it.
I'm not sure how much I'm bothered by them throwing the baby out with the bathwater, because, after all, it was a particularly ugly baby. Still, this was a 180º turnaround.
I hope that this section finds its way to the standard adventure template, as these are the sort of guidelines that need to be clearly expressed and accessible to all DMs.
I might also add in the concept of MYRE and how you can write those, but that might be best as a separate thread.
With regards to the changes that took place, I fully support them. My (probably obvious) intent with this thread was to bring the issues to the forefront and provide guidance given that there was a lot of confusion. It didn't seem as if the admins wanted to draw a hard line, so I wanted there to be some idea on how to avoid huge failures.
I am happy to see really major and even moderate changes removed. Ideally, the adventures don't need them. In truth, some do, but I think RPGA plays better when players can count on getting a play experience that is genuine to what the authors and admins crafted.
With MYRE, you can ignore a bad mod and instead write your own. If you don't like REGION1-X, you can skip it and write your own to still take place in that region. You can borrow elements (ideas on terrain, for example, or the concept of a search and rescue plot) that you liked and ditch the rest. MYRE provide a creative outlet and help DMs become authors, which is good for the craft and the RPGA. And, if you create something that turns out poorly, only 4-6 people suffer and you likely learn from the experience.
I have some major work to get off my plate and will then set to revise this guide. I'll probably end up making a new guide and asking WolfStar to unsticky this one. I'm not sure the older comments in this thread are helpful given the enormity of the changes.
This isn't a clarification of DM empowerment; this is a flat-out disavowal of it.
I'm not sure how much I'm bothered by them throwing the baby out with the bathwater, because, after all, it was a particularly ugly baby. Still, this was a 180º turnaround.
I thnk they tried it as an experient, tried to gently mention that it was only meant for small changes and not wholesale reskinning, etc. but saw that people were taking that inch and turning it into a mile. Experiment failed. So I'm not surprised.
I think they tried it as an experiment, tried to gently mention that it was only meant for small changes and not wholesale reskinning, etc. but saw that people were taking that inch and turning it into a mile. Experiment failed. So I'm not surprised.
I think one of the problems was that there appeared to be a wide divergence (even among staff) as to what DME was supposed to be about.
Here are a few quotes from regional POCs (who shall remain nameless) that seemed to think that the whole thing was about encouraging creativity, not just allowing small changes when necessary:
Show
LFR is less restrictive than previous Living Campaigns! We have DM empowerment, now. We WANT to tap the best and most creative DMs in the community to DM for LFR because DMs don't have to try and shoot for a uniform experience anymore. Share your creativity and DMing skills with our huge and incredibly diverse community!
An update is coming. I'm serious. I hope for this to come soon and for lots of feedback!
original guide:
My attempt at a guide.
1. The golden rules: Fun and reasonable Any DME changes should make the game more fun. Changes should be seen as the players as reasonable. It is easy to overstep the bounds of what players see as reasonable. Therefore, the greater the changes, the more important it is to check with players to ensure they are ok with the types of changes you are making. Consider whether you know the players, whether this is a con or a home game, how the author might feel, and impacts on the players/PCs when they play future mods in the series that may be based on this mod.
2. Respect copyright/ownership Any DME changes you make can be shared as adjustments, but you should avoid the use of trademarked/ copyrighted information and any document or post should still require another DM to have the original module. Reposting a completely remade module is not allowed.
3. Minor changes are encouraged by all. A minor change typically includes an adjustment to something that impacts an encounter but that is not fundamental to it.
For a skill challenge, this could include adding a skill that can be used, modifying the effect of a success or failure, creating impacts for RP and/or tactics, and adjusting the effects of a high or low roll.
Example: A player rolls really well on Diplomacy and does some great role-playing; you reward two successes instead of one.
Example: Intimidate is not allowed, but the party found some solid ground on which to threaten the NPC. You decide to allow the use of Intimidate.
For combat encounters, this could include adjustments to terrain, addition of minions, swapping of minions for other included monsters, changes to the map, changes to lower the hit points of monsters if combat drags on or is too challenging.
Example: You change the nature of difficult terrain to provide more opportunities for combatants without greatly affecting the overall difficulty.
Example: You have minions appear in waves, so as to improve their utility. (You might remove a minion or two to compensate for the advantage if it is a potentially difficult combat)
Example: You swap a power of a monster for another power from the MM of a similarly-leveled monster. The first combat encounter of ADAP1-5, Menace of the Icy Spire, contains a monster that has been changed in several minor ways to best fit the cold/ice theme and is a good example of minor changes.
Changes to the story can be minor if they do not impact the overall story or change NPCs, locations, rewards, or other important factors. An example would be to have a foe that was left unconscious by the party give information to help clear up any confusion the players have about the plot. Another example would be to include a new NPC that helps guide the players when they are having trouble with the story or with a skill challenge. In the retired adventure, Weekend in the Realms, any of the caravan NPCs could shed light on the Cormyr-Elven-Eladrin politics, clearing up the events of the attack and helping players better understand the module. Minor changes are an excellent way to adjust for replayers, to increase the regional flavor of modules, and to improve potential weak points of modules.
4. Moderate changes are possible under DME Moderate changes include changes to the story, the premise, the NPCs, the order of encounters, or major portions of encounters.
Example: Removing a trap and placing a monster of your choosing. Changing a monster for another. (Using the DMG rules to ensure proper balance).
Example: Changing the premise of the story to contain regional aspects, such as the Dwarves of the East Rift asking the party (composed entirely of PCs from the East Rift) to go to that region and secure a trade agreement, then having the mod run basically as it is written but including bits and pieces that carry the theme of securing a trade agreement.
Example: Adding RP encounters with NPCs to further the story, lengthening an intro to contain better story and RP.
Example: Changing the terrain in a drastic way, changing the placement and tactics of all monsters (with potential impacts on difficulty), etc.
Example: Changing a combat encounter that does not add XP to be a skill challenge instead. In Weekend in the Realms 2008, you could make the encounter with the iron dog and the clay homonculi into a skill challenge, having the parties search for clues as to how to appease them.
The number of encounters and the relative size of the encounters should be as close to the original module as possible, as these are carefully tested to ensure that the module falls within the suggested play time of the module. This is less important in events and locales where time is not an issue (single module events); in convention and multiple-slot events this is a necessity as it interferes with the players' ability to join in other slots. Too great a deviation can be an extreme change. With Moderate changes it is best to check with the players. While the rules seem to pretty clearly support this type of DME, some players may object to not getting the module as it is intended or to having changes that impact their chances of survival, RP, or continuity with future mods in the series. The rough nature of the changes should be shared prior to running the mod.
While moderate changes can improve on a module or make it a new experience for replayers, moderate changes run the risk of being too drastic - unlike the original module, your changes did not go through several sets of eyes and two playtests before reaching your table! Moderate changes are best employed by DMs who are very experienced and comfortable with the core DMG rules and who know the players and/or the module very well.
5. Extreme changes are not encouraged and may not be part of DME A complete rewrite of DME is discouraged by the campaign staff.
The language of DME suggests adjustments and not complete changes. Taking DME beyond moderate changes likely changes the module in fundamental ways the author, admins, playtesters, and WotC did not intend and would not recommend. The module may be unrecognizable and may harm continuity based on future releases for the series. Many players will find extreme changes to be the opposite of fun. In general, extreme changes should be attempted only with the approval beforehand of players you know and DM for frequently. It should be a home setting with plenty of time to handle any disagreement over the balance and scope of the changes.
Example: Completely change the nature of the encounter. For example, a combat with a solo monster of your choosing (say, oh, a Dragon...) instead of a mixed set of monsters provided in the mod.
Example: Changing a combat encounter that awards XP to be a skill challenge instead. In general, this is an extreme change that vastly changes the nature of the module. While an adventure without skill challenges may seem to call for one, it really provides a different play experience and can vastly affect the resources available to players for the remaining encounters. The reverse, changing a skill challenge to a combat encounter, is even more trouble-prone.
Example: Rewrite the plot to one of your choosing, such that the new story is not similar to the original plot. Example: Change the setting/theme to include some overriding theme of your choosing (insert TV show, movie, or other non FR idea of your choosing).
It is very easy for players to become upset over drastic DME. They may like it initially, then have a huge problem if it results in an impact to their XP, gold, awards, PC death, etc. Extreme changes should only be attempted by DMs and players with many years of experience who are comfortable both with the scope with changes and with working through any arguments that may come as a result of the changes. It is very poor form to run extreme DME changes without player consent! Admins and authors may be offended by your changes, particularly if they come with the idea that you thought the original work they produced was something that you could easily fix... (whether that is true or not).
Keep in mind that it is very likely that DME of this type will be strictly prohibited in the future. Consider these types of changes very carefully. Extreme changes are probably best for two situations: a set of friends agree to massively change a published module to fit some desired theme or provide some very different opportunity, or the rewriting of a published module to serve as a convention special event (preferably with admin approval, such as the event manager).
6. Prohibited under DME DME certainly does not allow you ownership of the module, republishing the whole module, changing rewards, or otherwise changing core 4E or LFR rules. Some guidelines on prohibited changes:
A) The treasure bundles, total experience, and gold awards must be identical to those in the original module.
B) The story awards MUST make sense within the scope of any changes (especially extreme changes) - favors from NPCs must remain logical and flow within the storyline and role-playing of the changed module in order for future modules to make sense. Story rewards are often an indication of a hook that will be used again in a future module.
C) It is highly recommended that if you do decide to make extreme changes outside of use for a home game, you do so only with groups of players that have already played the original module as written with another character. In this way, the players are aware of how the original module is played, in the event that in your changes you have altered something which will be important in a future module.
There are several modules which contain NPCs and encounters that appear to be benign and seem insignificant in the course of the individual module but which may well be key to future modules. In this manner, players know what their characters SHOULD have encountered and can therefore make adjustments in sequel modules their character plays in the future to reflect what they WOULD have experienced with that character had they played through the original module.
Example: The story awards for DALE1-1, The Prospect, are obvious tie-ins for authors to use in future adventures. Any changes to that module should keep the NPCs/organizations and have a valid story reason leading to the favor.
D) The changes should not unreasonably increase the difficulty of the encounter. It can be appropriate to make an encounter harder or easier, but this can be very hard to estimate and change correctly. DMs that use DME to adjust monster abilities or encounter difficulty should be ready to pull punches if the adjustment does not play out as intended. Few things will irritate a player more than a perception of a change being unfair, especially if it results in character death.
Template for 'Reskinned' Scenarios, by Corwynn.
An example of a moderately reskinned scenario, using my ideas for AKAN1-1.
Extreme reskin of CORM1-1 by Corwynn Reskin ideas for CORM1-1, may need some work
Reskin ideas for CORE1-1
Regional DME challenge, where you are invited to contribute minor changes to establish better regional setting and tone to the 1-1 mods.
This guide is yours! Please feel free to comment, refine, etc.
Teos
My attempt at a guide.
1. The golden rules: Fun and reasonable Any DME changes should make the game more fun. Changes should be seen as the players as reasonable. It is easy to overstep the bounds of what players see as reasonable. Therefore, the greater the changes, the more important it is to check with players to ensure they are ok with the types of changes you are making. Consider whether you know the players, whether this is a con or a home game, how the author might feel, and impacts on the players/PCs when they play future mods in the series that may be based on this mod.
2. Respect copyright/ownership Any DME changes you make can be shared as adjustments, but you should avoid the use of trademarked/ copyrighted information and any document or post should still require another DM to have the original module. Reposting a completely remade module is not allowed.
3. Minor changes are encouraged by all. A minor change typically includes an adjustment to something that impacts an encounter but that is not fundamental to it.
For a skill challenge, this could include adding a skill that can be used, modifying the effect of a success or failure, creating impacts for RP and/or tactics, and adjusting the effects of a high or low roll.
Example: A player rolls really well on Diplomacy and does some great role-playing; you reward two successes instead of one.
Example: Intimidate is not allowed, but the party found some solid ground on which to threaten the NPC. You decide to allow the use of Intimidate.
For combat encounters, this could include adjustments to terrain, addition of minions, swapping of minions for other included monsters, changes to the map, changes to lower the hit points of monsters if combat drags on or is too challenging.
Example: You change the nature of difficult terrain to provide more opportunities for combatants without greatly affecting the overall difficulty.
Example: You have minions appear in waves, so as to improve their utility. (You might remove a minion or two to compensate for the advantage if it is a potentially difficult combat)
Example: You swap a power of a monster for another power from the MM of a similarly-leveled monster. The first combat encounter of ADAP1-5, Menace of the Icy Spire, contains a monster that has been changed in several minor ways to best fit the cold/ice theme and is a good example of minor changes.
Changes to the story can be minor if they do not impact the overall story or change NPCs, locations, rewards, or other important factors. An example would be to have a foe that was left unconscious by the party give information to help clear up any confusion the players have about the plot. Another example would be to include a new NPC that helps guide the players when they are having trouble with the story or with a skill challenge. In the retired adventure, Weekend in the Realms, any of the caravan NPCs could shed light on the Cormyr-Elven-Eladrin politics, clearing up the events of the attack and helping players better understand the module. Minor changes are an excellent way to adjust for replayers, to increase the regional flavor of modules, and to improve potential weak points of modules.
4. Moderate changes are possible under DME Moderate changes include changes to the story, the premise, the NPCs, the order of encounters, or major portions of encounters.
Example: Removing a trap and placing a monster of your choosing. Changing a monster for another. (Using the DMG rules to ensure proper balance).
Example: Changing the premise of the story to contain regional aspects, such as the Dwarves of the East Rift asking the party (composed entirely of PCs from the East Rift) to go to that region and secure a trade agreement, then having the mod run basically as it is written but including bits and pieces that carry the theme of securing a trade agreement.
Example: Adding RP encounters with NPCs to further the story, lengthening an intro to contain better story and RP.
Example: Changing the terrain in a drastic way, changing the placement and tactics of all monsters (with potential impacts on difficulty), etc.
Example: Changing a combat encounter that does not add XP to be a skill challenge instead. In Weekend in the Realms 2008, you could make the encounter with the iron dog and the clay homonculi into a skill challenge, having the parties search for clues as to how to appease them.
The number of encounters and the relative size of the encounters should be as close to the original module as possible, as these are carefully tested to ensure that the module falls within the suggested play time of the module. This is less important in events and locales where time is not an issue (single module events); in convention and multiple-slot events this is a necessity as it interferes with the players' ability to join in other slots. Too great a deviation can be an extreme change. With Moderate changes it is best to check with the players. While the rules seem to pretty clearly support this type of DME, some players may object to not getting the module as it is intended or to having changes that impact their chances of survival, RP, or continuity with future mods in the series. The rough nature of the changes should be shared prior to running the mod.
While moderate changes can improve on a module or make it a new experience for replayers, moderate changes run the risk of being too drastic - unlike the original module, your changes did not go through several sets of eyes and two playtests before reaching your table! Moderate changes are best employed by DMs who are very experienced and comfortable with the core DMG rules and who know the players and/or the module very well.
5. Extreme changes are not encouraged and may not be part of DME A complete rewrite of DME is discouraged by the campaign staff.
The language of DME suggests adjustments and not complete changes. Taking DME beyond moderate changes likely changes the module in fundamental ways the author, admins, playtesters, and WotC did not intend and would not recommend. The module may be unrecognizable and may harm continuity based on future releases for the series. Many players will find extreme changes to be the opposite of fun. In general, extreme changes should be attempted only with the approval beforehand of players you know and DM for frequently. It should be a home setting with plenty of time to handle any disagreement over the balance and scope of the changes.
Example: Completely change the nature of the encounter. For example, a combat with a solo monster of your choosing (say, oh, a Dragon...) instead of a mixed set of monsters provided in the mod.
Example: Changing a combat encounter that awards XP to be a skill challenge instead. In general, this is an extreme change that vastly changes the nature of the module. While an adventure without skill challenges may seem to call for one, it really provides a different play experience and can vastly affect the resources available to players for the remaining encounters. The reverse, changing a skill challenge to a combat encounter, is even more trouble-prone.
Example: Rewrite the plot to one of your choosing, such that the new story is not similar to the original plot. Example: Change the setting/theme to include some overriding theme of your choosing (insert TV show, movie, or other non FR idea of your choosing).
It is very easy for players to become upset over drastic DME. They may like it initially, then have a huge problem if it results in an impact to their XP, gold, awards, PC death, etc. Extreme changes should only be attempted by DMs and players with many years of experience who are comfortable both with the scope with changes and with working through any arguments that may come as a result of the changes. It is very poor form to run extreme DME changes without player consent! Admins and authors may be offended by your changes, particularly if they come with the idea that you thought the original work they produced was something that you could easily fix... (whether that is true or not).
Keep in mind that it is very likely that DME of this type will be strictly prohibited in the future. Consider these types of changes very carefully. Extreme changes are probably best for two situations: a set of friends agree to massively change a published module to fit some desired theme or provide some very different opportunity, or the rewriting of a published module to serve as a convention special event (preferably with admin approval, such as the event manager).
6. Prohibited under DME DME certainly does not allow you ownership of the module, republishing the whole module, changing rewards, or otherwise changing core 4E or LFR rules. Some guidelines on prohibited changes:
A) The treasure bundles, total experience, and gold awards must be identical to those in the original module.
B) The story awards MUST make sense within the scope of any changes (especially extreme changes) - favors from NPCs must remain logical and flow within the storyline and role-playing of the changed module in order for future modules to make sense. Story rewards are often an indication of a hook that will be used again in a future module.
C) It is highly recommended that if you do decide to make extreme changes outside of use for a home game, you do so only with groups of players that have already played the original module as written with another character. In this way, the players are aware of how the original module is played, in the event that in your changes you have altered something which will be important in a future module.
There are several modules which contain NPCs and encounters that appear to be benign and seem insignificant in the course of the individual module but which may well be key to future modules. In this manner, players know what their characters SHOULD have encountered and can therefore make adjustments in sequel modules their character plays in the future to reflect what they WOULD have experienced with that character had they played through the original module.
Example: The story awards for DALE1-1, The Prospect, are obvious tie-ins for authors to use in future adventures. Any changes to that module should keep the NPCs/organizations and have a valid story reason leading to the favor.
D) The changes should not unreasonably increase the difficulty of the encounter. It can be appropriate to make an encounter harder or easier, but this can be very hard to estimate and change correctly. DMs that use DME to adjust monster abilities or encounter difficulty should be ready to pull punches if the adjustment does not play out as intended. Few things will irritate a player more than a perception of a change being unfair, especially if it results in character death.
Template for 'Reskinned' Scenarios, by Corwynn.
An example of a moderately reskinned scenario, using my ideas for AKAN1-1.
Extreme reskin of CORM1-1 by Corwynn Reskin ideas for CORM1-1, may need some work
Reskin ideas for CORE1-1
Regional DME challenge, where you are invited to contribute minor changes to establish better regional setting and tone to the 1-1 mods.
This guide is yours! Please feel free to comment, refine, etc.
Teos
original post, part 2:
Reasons and Methodology for the Use of DME to Modify a Mod
In general, DME is used to improve upon the module. This can be due to perceived shortcomings, or due to desired aspects that are not present. DME can also be used to give a table of replayers new experiences (though, generally, a new module will always provide a better overall experience).
A) The module is unclear
A lack of clarity can kill a module. If the players can't follow the story, don't understand the importance of taking heroic action, don't understand what to do next, or otherwise are lost, they typically will lose faith and interest in the module. Minor changes can be used to smooth the transitions between encounters or clarify encounters. Examples include providing a handout that captures the information they might learn via a skill challenge, providing a handout with a check-list of tasks, or including a clue that one of the creatures in a combat encounter may actually be an ally they are seeking.
B) The module lacks diversity
A convention may have two modules in a row that feature the same monsters. Or, a single module may rely too heavily on the same monster type (goblins, orcs, kobolds). Making a few minor to moderate changes can keep the battles interesting. Many times, simply changing terrain and conditions can make the battles different while continuing the logic of a dungeon of a single species of monster. For example, the preview adventure in the back of the DMG is really about the skull game and the giant stone sphere, not about the wacky kobolds. Making the environment interesting, giving the monsters names and uniforms, using different tactics, and enhancing terrain and traps/hazards can make a monotonous module fun.
C) The module runs long
When a module runs long, you can always shave a few HPs off of a monster or two on the fly as a minor change. (This is best done when you do it a bit before the end, such as to two of the last three monsters, as this can hasten the heroic feel of the combat or preserve PC resources).
Modules often run long because there are too many brutes or soldiers with lots of HPs, because the skill challenges are complex, or because the PCs spend a lot of time wondering what to do. A module may run on time, but lack opportunities for proper RP. And, a table may end up enjoying one aspect of the module more than another.
With time to plan, you can reduce HPs, trade monsters for minions (best done in a fight that is not the mod's primary challenge), trade a brute or soldier for another type of monster, increase the skills that can be used in a challenge, prepare NPC responses to typical PC questions, provide maps and handouts, provide NPCs that review what has happened, and so on. Many of these can be done on-the-fly as well.
D) The module lacks a regional feel
Many LFR modules could use improvements to their regional aspects, so as to make the region iconic and provide a setting that has meaning and gives players an emotional investment in the outcome (and that of future modules). Ideally, each module teaches PCs something about the region, creates regional ties, and provides memorable locations, foes, or allies.
Minor changes with DME can add regional flavor. A very simple addition to any module is to use the FRPG and allow PCs to roll the skill checks listed for each region, providing them with the noted information if the succeed. This can be done right at the beginning, or with a bit of planning, the information that would be learned can be woven into the introduction (perhaps the NPC responds to a question from the PC and provides the information).
With a little more work, the mod's setting and story can be linked to the locations and themes in the FRPG and FRCG. For example, show players the Faerun map and show them where they are, then show them distances to other surrounding towns and features (forests, mountains). Add references to regional character (For example, in the East Rift: "You notice that the Gold Dwarves have well groomed beards and display finely crafted jewelry with pride. One particularly well-groomed dwarf now approaches you..."). Throw in gossip and rumor ("Leaving the fabulous city of Airspur and it's floating spires behind, you can't help but recall what you overheard in a tavern... Arkanul and the Genasi face several threats along its borders, especially the Abolethi... could it be that they needed you for this mission because Airspur cannot spare the men to look into common goblins, or are these goblins a bigger threat than expected?"). Little tricks, such as detailing treasure ("you find some Cormyrian coins and a statue depicting their famous ruler...") can go a long way towards reminding players that they are in a particular region.
E) An Encounter is Poorly Designed
An encounter might be too deadly, easy, boring, or otherwise need work to meet the desired standard of quality. Be careful to measure this objectively and not personally or based solely on a single previous game. One table may hate an encounter two other tables will love. If an encounter can use improvement, try to isolate the root problem (too deadly because there are two monsters with AoE rechargable powers... a few lucky dice and the table will take massive damage), then consider several solutions (change one of the monsters, fudge the dice if you come up with too many recharges, change the recharge value so it comes up less often, change one of the monsters to have a different rechargable power). Generally, a choice you can tweak on the fly or which has a strong basis in core rules and the encounter (such as using a different monster of the same level already found in the module) is best. Be careful not to change encounter difficulty (such as by raising Skill DCs significantly) without really knowing the PCs well.
F) DME for Replaying
The replay rules allow a player to play any particular mod multiple times (once per character). A DM that knows ahead of time that they will have replayers at the table can use DME to keep the module from becoming stale. The DM must balance the desires of replayers against the desires of first-time players. Minor DME can often be used without changing anything notable for the first-time players. Moderate and extreme DME may be contrary to the wishes of first-time players, as they may wish to experience the module as it was intended by the LFR staff and the author. In general, it is best to honor the desires of first-time players.
When using DME for replay with some first-timers present, consider ways to keep the central story intact but change aspects that add color. In RP and skill challenges, you can change any NPCs that are not critically important or shift the emphasis of NPCs. For example, shift more of the conversation to the barmaid and introduce a local bard who can answer questions. Consider a voice or mannerisms that will make an impression and solicit RP. You can shift skill challenge locations (instead of a blacksmith who can make keys, they need to talk the former owner into giving up the old set of keys they still have).
For combats, analyze the critical pieces that affect tactical decisions, as those are often the most repetitive/boring and subject to abuse. Swap minions in or out (though you may not to deprive a first-time player who has minion-slaying powers), change the starting locations of monsters, move the traps around and change their description (wall panels instead of the statues) change the terrain description, start the combat with some RP that deteriorates into combat, and add some RP to the monsters (such as smack-talking or comical disagreement between leader and subordinates) that liven the combat. Keep the basic challenge and nature of the encounters intact so that first-time players get an experience that is true to the module.
==
Feedback appreciated!
Reasons and Methodology for the Use of DME to Modify a Mod
In general, DME is used to improve upon the module. This can be due to perceived shortcomings, or due to desired aspects that are not present. DME can also be used to give a table of replayers new experiences (though, generally, a new module will always provide a better overall experience).
A) The module is unclear
A lack of clarity can kill a module. If the players can't follow the story, don't understand the importance of taking heroic action, don't understand what to do next, or otherwise are lost, they typically will lose faith and interest in the module. Minor changes can be used to smooth the transitions between encounters or clarify encounters. Examples include providing a handout that captures the information they might learn via a skill challenge, providing a handout with a check-list of tasks, or including a clue that one of the creatures in a combat encounter may actually be an ally they are seeking.
B) The module lacks diversity
A convention may have two modules in a row that feature the same monsters. Or, a single module may rely too heavily on the same monster type (goblins, orcs, kobolds). Making a few minor to moderate changes can keep the battles interesting. Many times, simply changing terrain and conditions can make the battles different while continuing the logic of a dungeon of a single species of monster. For example, the preview adventure in the back of the DMG is really about the skull game and the giant stone sphere, not about the wacky kobolds. Making the environment interesting, giving the monsters names and uniforms, using different tactics, and enhancing terrain and traps/hazards can make a monotonous module fun.
C) The module runs long
When a module runs long, you can always shave a few HPs off of a monster or two on the fly as a minor change. (This is best done when you do it a bit before the end, such as to two of the last three monsters, as this can hasten the heroic feel of the combat or preserve PC resources).
Modules often run long because there are too many brutes or soldiers with lots of HPs, because the skill challenges are complex, or because the PCs spend a lot of time wondering what to do. A module may run on time, but lack opportunities for proper RP. And, a table may end up enjoying one aspect of the module more than another.
With time to plan, you can reduce HPs, trade monsters for minions (best done in a fight that is not the mod's primary challenge), trade a brute or soldier for another type of monster, increase the skills that can be used in a challenge, prepare NPC responses to typical PC questions, provide maps and handouts, provide NPCs that review what has happened, and so on. Many of these can be done on-the-fly as well.
D) The module lacks a regional feel
Many LFR modules could use improvements to their regional aspects, so as to make the region iconic and provide a setting that has meaning and gives players an emotional investment in the outcome (and that of future modules). Ideally, each module teaches PCs something about the region, creates regional ties, and provides memorable locations, foes, or allies.
Minor changes with DME can add regional flavor. A very simple addition to any module is to use the FRPG and allow PCs to roll the skill checks listed for each region, providing them with the noted information if the succeed. This can be done right at the beginning, or with a bit of planning, the information that would be learned can be woven into the introduction (perhaps the NPC responds to a question from the PC and provides the information).
With a little more work, the mod's setting and story can be linked to the locations and themes in the FRPG and FRCG. For example, show players the Faerun map and show them where they are, then show them distances to other surrounding towns and features (forests, mountains). Add references to regional character (For example, in the East Rift: "You notice that the Gold Dwarves have well groomed beards and display finely crafted jewelry with pride. One particularly well-groomed dwarf now approaches you..."). Throw in gossip and rumor ("Leaving the fabulous city of Airspur and it's floating spires behind, you can't help but recall what you overheard in a tavern... Arkanul and the Genasi face several threats along its borders, especially the Abolethi... could it be that they needed you for this mission because Airspur cannot spare the men to look into common goblins, or are these goblins a bigger threat than expected?"). Little tricks, such as detailing treasure ("you find some Cormyrian coins and a statue depicting their famous ruler...") can go a long way towards reminding players that they are in a particular region.
E) An Encounter is Poorly Designed
An encounter might be too deadly, easy, boring, or otherwise need work to meet the desired standard of quality. Be careful to measure this objectively and not personally or based solely on a single previous game. One table may hate an encounter two other tables will love. If an encounter can use improvement, try to isolate the root problem (too deadly because there are two monsters with AoE rechargable powers... a few lucky dice and the table will take massive damage), then consider several solutions (change one of the monsters, fudge the dice if you come up with too many recharges, change the recharge value so it comes up less often, change one of the monsters to have a different rechargable power). Generally, a choice you can tweak on the fly or which has a strong basis in core rules and the encounter (such as using a different monster of the same level already found in the module) is best. Be careful not to change encounter difficulty (such as by raising Skill DCs significantly) without really knowing the PCs well.
F) DME for Replaying
The replay rules allow a player to play any particular mod multiple times (once per character). A DM that knows ahead of time that they will have replayers at the table can use DME to keep the module from becoming stale. The DM must balance the desires of replayers against the desires of first-time players. Minor DME can often be used without changing anything notable for the first-time players. Moderate and extreme DME may be contrary to the wishes of first-time players, as they may wish to experience the module as it was intended by the LFR staff and the author. In general, it is best to honor the desires of first-time players.
When using DME for replay with some first-timers present, consider ways to keep the central story intact but change aspects that add color. In RP and skill challenges, you can change any NPCs that are not critically important or shift the emphasis of NPCs. For example, shift more of the conversation to the barmaid and introduce a local bard who can answer questions. Consider a voice or mannerisms that will make an impression and solicit RP. You can shift skill challenge locations (instead of a blacksmith who can make keys, they need to talk the former owner into giving up the old set of keys they still have).
For combats, analyze the critical pieces that affect tactical decisions, as those are often the most repetitive/boring and subject to abuse. Swap minions in or out (though you may not to deprive a first-time player who has minion-slaying powers), change the starting locations of monsters, move the traps around and change their description (wall panels instead of the statues) change the terrain description, start the combat with some RP that deteriorates into combat, and add some RP to the monsters (such as smack-talking or comical disagreement between leader and subordinates) that liven the combat. Keep the basic challenge and nature of the encounters intact so that first-time players get an experience that is true to the module.
==
Feedback appreciated!
Feel free to post with ideas!
Is changing a weapon, a relatively aesthetic change ok? I find a monster with a battleaxe, and see no shield and think hmm Executioners axe. This is an interesting change, because overall it adds more damage potential, brutal, high crit, bigger damage dice etc.
Is giving a monster an action point, or another action point ok? This has happened in several adventures I have played in. I don't mind unless it pushes the combat over the edge. A tough combat should not be tweaked, but an easy combat could easily get a step up with an action point or few to the bad guys.
Two questions about the limits of DME.
Is changing a weapon, a relatively aesthetic change ok? I find a monster with a battleaxe, and see no shield and think hmm Executioners axe. This is an interesting change, because overall it adds more damage potential, brutal, high crit, bigger damage dice etc.
Is giving a monster an action point, or another action point ok? This has happened in several adventures I have played in. I don't mind unless it pushes the combat over the edge. A tough combat should not be tweaked, but an easy combat could easily get a step up with an action point or few to the bad guys.
Neither change is supported by DME. You cannot actually change a monster in any way beyond increasing or decreasing its level.
It is all a fine line. If everyone at the table wanted the DM to play around and try some things to challenge them because they are so OP as to walk over every LFR mod, I don't see the problem. But, if some people at the table don't want it, or if it is done without players knowing... that's exactly why these rules exist.
As I said on another thread, you never know what players want without asking. I had an otherwise fantastic DM stealth-run my friends and I through a table at High when we asked for Low. I knew and had read the mod, so I recognized the changes. He worked hard to challenge us, killed one PC... and he probably had no idea that in the preceding con slot we had a near TPK and wanted a nice easy going.
I could use some ideas for MYRE, should anyone want to share some wisdom. I see Elder Basilisk's nice thread and have linked to it.