Thanee said:Rules As Written? (I can only guess)
BTW, in 2e you could get high percentages as a Thief, because you could decide where to put the %-points each level, in 1e you had that fixed slow progression!
Bye
Thanee
reapersaurus said:Apparently, even when there is no surprise round, a character is considered flatfooted until it reaches their initiative order in combat.
Main impact to game: No DEX boni, suffer sneak attacks, and no AoO.
Example: 4 1st level combatants, 2 on a side. NO SURPRISE.
1st side has Rogue Archer and Spiked Chain Ftr, 2nd side has Bbn and Mage.
Initiative: Bbn (20), then Rogue (18), then Chain Ftr (17), then Mage (16).
Bbn WAY in the back rank goes. Rages, pulls out greatsword, runs 80' right past the mage, past the Chain Ftr's entire threatened quadrant (incurring NO AoO's) and charges into Rogue, almost killing him cause no DEX bonus.
All because he started his Charge a couple blinks of an eye faster than the Rogue & Ftr started?
Then, the Rogue goes. He steps 5' back, ignores the Bbn that almost killed him, and fires at the Mage who he easily hits cause no DEX bonus and kills him with sneak attack damage.
Does this make sense to you?
Who plays this way?
I'm guessing that since I've never heard this rule discussed, and it's in the books, that MOST people would play this way, and I've just had uncommon groups.
But I think I'd remember if any group had done special AC calculations that only applied in the first round, and only until their PC moved, and used different tactics in the first round to take advantage of the PC or NPC that looked like they hadn't reacted yet.
How would that go, anyway?
Player1 to DM: I want to BullRush someone off the cliff. Which Kobold looks like they haven't moved yet?The DM's answer would be "weren't you paying attention? now just pick one, already!"
The player should observe which kobolds have or haven't taken their action.
Additionally, most games I've played in, or GMed ... the NPCs tend to have initiative rolled in groups. IF there are twenty kobolds, I'd split them into groups of 5. Other GMs would just roll once for the whole mess of kobolds.
That just sounds so awkward.
And more: Wouldn't this rule change the entire weight of initiative being rolled in the open?
There are so many reasons to now roll initiative secretly, so as not to unduly influence the strategies used in combat.
Players shouldn't be making ANY rolls "secretly". As a DM, I don't announce the NPCs initiative until I have all the PC initiatives to hand; if that counts as rolling initiative "in secret" ... then I guess that's what I do. Occasionally, for a critical combat, I'll fudge the initiative roll, so that the main villain has the initiative to make his dramatic speech-and-exit, leaving his/her/it's minions to deal with the PCs, and so on. That rather requires not rolling openly ...
Shard O'Glase said:Yes if you chose to specialize in two fields those %s could get high fairly quick. Climb walls always started decent, add in dex, and race and you could get some skills to the 95% range decently fast. Problem was thier was no above 95%, while thier were plenty of penalties.(I beleive the high level handbook addressed this to some degree) I think an outstanding lock had a 40% penalty so the ebst lockpikcer in the world owuld have at best a 55% chance of success, and if he failed the attempt he just couldn't make another attempt.
reapersaurus said:It seems like that vote is off even from the responses here (unless you play the rule as written every single time, you're not playing it by the rules)
But for example - Thanee - I know we aren't playing it that way in the Non-Iconic Adventure.
I'm fairly sure most online games aren't using it.
I've seen/played in probably 8 different ones, and with my 6 or 7 different RL groups, that encompasses almost a hundred people, and they never mentioned it, or to my knowledge used it.
I guess asking the Rules Forum of the most knowledgeable 3E Message Board is not the place to get a feel for the common game, so maybe it's just that you guys are the uncommon ones in relation to this rule.
![]()