Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="KarinsDad" data-source="post: 2940106" data-attributes="member: 2011">You waste your time writing them down? <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f631.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":eek:" title="Eek!    :eek:"  data-smilie="9"data-shortname=":eek:" /> Then you are not reading everything here.The very fact that WotC changed the Haste spell should tell you something. Back to back actions for a single character can lead to TPK faster than anything else in the game. If it does not tell you this, then I suggest that you do not use this variant rule because it will side swipe you quick.Round one: The PCs win init, so they move closer to the enemy. The NPC Wizard fireballs the PCs.Round two: The NPC Wizard wins init, so he fireballs the PCs. Not a single PC could react to the first fireball to either heal, take cover, counterattack, or anything.Most of the PCs are dead and the few other NPCs quickly mop up the heavily wounded Barbarian.DM: "Ok people, who wants to play what race and class for our new campaign?"This is not whining (for those who hold that position). This is fact. It will happen and it will happen a lot. With feats and PrCs and monster templates, 3E has a lot more ways to take advantage of back to back actions than 2E did. Even without delays or readied actions.This is also not DM adjudication. If you have to have the NPC Wizard not fireball the PCs in round two in the example above and instead cast a Shield spell, then I just feel sorry for you and your spoon fed must protect the PCs because of the stupid initiatve system you are using game. And, the players will obviously feel coddled in such a game when the NPC Wizard casts Shield on round two and waits until round four to cast Fireball again. That's just plain sad.</blockquote>

Verification