Reply to thread

Message

<blockquote data-quote="Charlaquin" data-source="post: 8736251" data-attributes="member: 6779196">Ok, so… I LOVE this UA. I have a few nitpicks here and there, but overall, I’m thrilled with the direction this seems to be going in. Couple of subtle things I noticed:• The wording on Long Rest in the rules glossary clears up the ambiguity about how much combat it takes to interrupt a long rest. Turns out, it’s any combat at all. Not sure this is any indication of what the intent of the original wording was, since “everyone plays it this way anyway” is explicitly the reason for nat 1s and 20s being automatic failures and successes on any d20 Test (not a fan of that term, but it does its job). But in that light it’s an unsurprising decision to change the wording the way they did in either case.• One of the effects of being incapacitated is that you’re “surprised” which gives you disadvantage on your initiative roll. In light of the way False Appearance works post-MMotM and the changes to Bugbears’ ambusher trait, I’m calling it now: the pseudo-surprise-round is going away, surprise will now just impose disadvantage on initiative.• A lot of stuff in the packet is capitalized that hasn’t typically been capitalized in 5e. Looks like they’re going to continue using natural-sounding terms in a technical way, but they’re at least going to use capitalization to indicate when a word is being used as rules jargon instead of its literal English meaning. Which is I think the best us technical language enjoyers could reasonably have hoped for in light of the goal of backwards compatibility.</blockquote>

[QUOTE="Charlaquin, post: 8736251, member: 6779196"] Ok, so… I LOVE this UA. I have a few nitpicks here and there, but overall, I’m thrilled with the direction this seems to be going in. Couple of subtle things I noticed: • The wording on Long Rest in the rules glossary clears up the ambiguity about how much combat it takes to interrupt a long rest. Turns out, it’s any combat at all. Not sure this is any indication of what the intent of the original wording was, since “everyone plays it this way anyway” is explicitly the reason for nat 1s and 20s being automatic failures and successes on any d20 Test (not a fan of that term, but it does its job). But in that light it’s an unsurprising decision to change the wording the way they did in either case. • One of the effects of being incapacitated is that you’re “surprised” which gives you disadvantage on your initiative roll. In light of the way False Appearance works post-MMotM and the changes to Bugbears’ ambusher trait, I’m calling it now: the pseudo-surprise-round is going away, surprise will now just impose disadvantage on initiative. • A lot of stuff in the packet is capitalized that hasn’t typically been capitalized in 5e. Looks like they’re going to continue using natural-sounding terms in a technical way, but they’re at least going to use capitalization to indicate when a word is being used as rules jargon instead of its literal English meaning. Which is I think the best us technical language enjoyers could reasonably have hoped for in light of the goal of backwards compatibility. [/QUOTE]

Verification