Of all the relevant conditions: -Restrained lets you make attacks, ie, you still have the use of your hands.
-Other relevant conditions allow you to move but not take actions at all. (Basically anything that makes you incapacitated).
So if someone binds your hands behind your back, why is Restrained not the right condition? That seems silly. (Also, restrained sets speed to 0, but someone with their hands bound can still walk...)
There doesn't seem to be any condition where casting a spell while not using S or M components is relevant, because no condition allows spell casting but prevents spells with S or M.
Probably because making a rules condition for "in handcuffs" isn't important in a game where the rules mainly exist to ensure fairness. Everyone knows that you won't attack if your hands are tied behind your back, but most people wouldn't know how to run "stuck in cobwebs" without the Restrained condition.
They only create named conditions for common situations, and I guess that didn't see a sufficiently common condition. You can have an unnamed effect that does that.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Of all the relevant conditions:
-Restrained lets you make attacks, ie, you still have the use of your hands.
-Other relevant conditions allow you to move but not take actions at all. (Basically anything that makes you incapacitated).
So if someone binds your hands behind your back, why is Restrained not the right condition? That seems silly. (Also, restrained sets speed to 0, but someone with their hands bound can still walk...)
There doesn't seem to be any condition where casting a spell while not using S or M components is relevant, because no condition allows spell casting but prevents spells with S or M.
Probably because making a rules condition for "in handcuffs" isn't important in a game where the rules mainly exist to ensure fairness. Everyone knows that you won't attack if your hands are tied behind your back, but most people wouldn't know how to run "stuck in cobwebs" without the Restrained condition.
They only create named conditions for common situations, and I guess that didn't see a sufficiently common condition. You can have an unnamed effect that does that.