Reply to thread

Message: <blockquote data-quote="Dunamin" data-source="post: 4394178" data-attributes="member: 57529">I wholeheartedly agree.I had initially put contracts under the same recharge power due to the DMG’s advice that monsters generally should have only one encounter or recharge power per tier. However, I noted that the Troglodyte Curse Chanter has 3 (same level and role) and there’s generally an abundance of deviations from the design guide in the MM, so why not do the same for the falxugon (Contract of Submission and Cowardice are not too severe for encounter powers anyway).I like your modifications to the contracts and the new one, though I’m unsure about damage ranges. Making them bursts seems prudent for the reasons you mentioned, though why set range to 6 specifically?For the Contract of Submission I just noticed that dropping prone and standing up doesn’t seem to provoke OAs in 4E which makes the power less trouble than I intended – the target just spends a move to get up and a minor action to grab its weapon/implement, making the effect essentially on par with being dazed for a round. The idea is to convey a clear message of submission and humility, so my current take is this:<img src="http://www.enworld.org/forum/images/smilies/c.gif"  class="smilie" loading="lazy" alt=":close:" title="Close    :close:" data-shortname=":close:" /> Contract of Submission (standard, encounter) * Charm, PsychicClose burst 5, one creature within burst; +12 vs Will; target chooses - target immediately drops prone and cannot stand up until end of the devil’s next turn, or target takes 3d8+5 psychic damage.The Contract of Cowardice has a nice theme going but the fixed push distance seems a bit awkward. Rather than have the subject flee, cowardice could also just be abstinence from attacking:<img src="http://www.enworld.org/forum/images/smilies/c.gif"  class="smilie" loading="lazy" alt=":close:" title="Close    :close:" data-shortname=":close:" /> Contract of Cowardice (standard, encounter) * Charm, PsychicClose burst 5, one creature within burst; +12 vs Will; target chooses - target cannot make an attack that includes the devil until end of the devil’s next turn, or target takes 3d8+5 psychic damage.There’s no vital reason why the pen should daze, though the idea of a pen dealing more than marginal damage sort of irks me. I think I’ll just make the basic melee attack a Tail Sting 1d8+2 (same damage as the trog chanter’s basic), since falxugon tails are described as having a wicked prong.Now that I look at the current stat block, however, I’m thinking it may be a bit much with 7 separate powers, so I’m considering if I should cut Corrupt Soul and/or Contract of Cowardice (though I think both are nice and appropriate features for this devil).My current take is in the top post, though after having looked at the Satyr Piper I’m wondering if it isn’t simpler (if unconventional) to use the following expression:<img src="http://www.enworld.org/forum/images/smilies/c.gif"  class="smilie" loading="lazy" alt=":close:" title="Close    :close:" data-shortname=":close:" /> Infernal Contract (standard; each contract once per encounter) * Charm, PsychicClose burst 5, one creature within burst; +12 vs. Will; the target is fooled into believing it has signed a contract with the devil. The target may choose not to follow the terms of the contract, in which case it believes its soul is damned and takes 3d8+5 psychic damage. The devil selects one of the following contracts, each useable once per encounter:Contract of Treachery: The terms require the target to immediately shift 1 and make a basic attack against an ally, if possible, with a +1d8 bonus to damage. Contract of Submission: The terms require the target to drop and remain prone until end of the devil’s next turn. Contract of Cowardice: The terms require the target to not make an attack that includes the devil until end of the devil’s next turn.I’ll get busy with the barbed devil / hamatula soon, although it’s fun fine-tuning the falxugon as you get feedback. Thanks again for all the help!</blockquote>

Verification