Report 1147

Report #1147
Skillset: Skill: Parrying
 Org: Sentinels Status: Completed Apr 2013
Furies' Decision:
Solution 1 (incl. Xenthos syntax).
Problem: Parrying is one of those things that generates both quite a lot of
command spam and information sent back to the user. To change your current
parry, you must first unparry and then assign a weight to the bodypart you wish
to parry. If for whatever reason, you are splitting your parry over two (or
more) bodyparts, this gets even spammier with each shifted parry requiring its
own command. This report looks for a solution to reduce some of the spam, like
the relatively recent CLOT <#> change with bleeding spam.
[A: 0 R: 0] Solution #1: Allow for the single command type syntax: PARRY
 <where> <amount> [<where> <amount>...]. The current
 'unparry' step will be understood to be implicit, and
 rather than the 'You cease parrying.' and each 'You
 adjust your attention spent parrying your
 <bodypart>.' lines sent back, a single summary line
 is returned.
Player Comments:
---[Ushaara on 4/14 @ 12:12 writes]:
Like how clot <#> only sends a single clot if under aeon/sap, having it only
work for the first specified bodypart works for me.
---[Rivius on 4/14 @ 17:07 writes]:
I don't see this as hugely necessary and actually weakens the value of stupidity
in screwing up re-parrying attempts. If people find it too spammy, there's
client-side methods to deal with that.
---[Celina on 4/15 @ 00:29 writes]:
Supported. Anything to reduce spam is good. "Weakens stupidity," is a pretty
vague and flimsy argument. I don't know why anyone would oppose this.
---[Shuyin on 4/16 @ 02:59 writes]:
This is fine
---[Steingrim on 4/16 @ 03:15 writes]:
Supported, though a bit wary of Ushaara's suggestion. Instead might suggest the
return also be one line.
---[Ushaara on 4/16 @ 19:00 writes]:
@Steingrim ah, I already had that suggestion included in the solution part.
---[Xenthos on 4/18 @ 01:30 writes]:
I don't mind, but I'd prefer a separate command versus changing how regular
parry works. IE PARRY RESET WHERE AMOUNT WHERE AMOUNT WHERE AMOUNT. If the
reset is the second work in the command, it does an unparry and redoes
everything based on the list.
---[Janalon on 4/18 @ 10:14 writes]:
Sure.
---[Ushaara on 4/19 @ 15:32 writes]:
PARRY RESET <blah> works for me. Avoids any backward compatability issues with
systems too which is good point to consider.
---[Llandros on 4/30 @ 14:10 writes]:
This is fine