PDA

View Full Version : WG & Disadvantages



RPMiller
Sep 28th, '03, 04:10 PM
Sorting - When sorting Disads they are sorted first by name and then by cost currently there doesn't seem to be a way to do this.
Dependence - Very difficult to get it to look like the WG examples.
DNPC - Useful Noncombat Position every word should be capitalized.
Distinctive Features - The abbreviation DF is not per the WG.
Distinctive Features - When something is Detectable By Commonly-Used Senses it shouldn't display the detectable text portion
Enraged - For Berserk, put the word "Berserk" at the beginning of the description of the condition. I.e. berserk at the sight/smell of blood.
Hunted - Descriptors inside parentheses should be separated with commas not semi-colons
Hunted - Extensive Non-Combat Influence should be abbreviated "NCI"
Hunted - What the Hunter will do should come last in the parentheses
Physical Limitation - Phys. Lim. is not a WG abbreviation
Physical Limitation - Descriptors in parentheses should be separated with commas not semi-colons
Psychological Limitation - Psych. Lim. is not a WG abbreviation
Psychological Limitation - Descriptors in parentheses should be separated with commas not semi-colons
Reputation - after the description of the reputation there should be a comma followed by the roll
Rivalry - The descriptors for power and authority, fierceness, and knowledge should be separated with commas not semi-colons
Rivalry - The descriptor for fierceness shouldn't be displayed unless it is Harm/Kill. I get the impression when a descriptor isn't worth points it should display. You may want to ask Steve. It seems this way in the printed material and in the examples in the WG.
Social Limitation - Soc. Lim. is not a WG abbreviation
Social Limitation - Descriptors should be separated with commas not semi-colons
Susceptibility - A comma follows the to description, and there is no comma after the damage

Simon
Sep 29th, '03, 05:15 AM
1. Sort by cost and then sort by name.

2. I don't see any need to change this one.

3. Done.

4. Fixed.

5. I disagree. Per the WG: After the description, list in parentheses, and separated by semi-colons, the descriptors for Concealability, Reaction, and Sensing; the key words in these descriptors are capitalized.

(more to come)

RPMiller
Sep 29th, '03, 11:58 AM
Originally posted by Simon
5. I disagree. Per the WG: After the description, list in parentheses, and separated by semi-colons, the descriptors for Concealability, Reaction, and Sensing; the key words in these descriptors are capitalized.

(more to come) Well, here I go breaking my decision... I wasn't going to reply to anything, but I have to on this one because it was per Steve. You may want to run it past him. I'll let you get back to pushing your Beans ;)

Simon
Oct 3rd, '03, 08:41 AM
5 (again): I <b>have</b> talked with Steve on it. It remains the way it is. The examples in the WG do not follow the description given...they are space-saving devices only. Entirely optional. If you want to take advantage of that option, then delete the text for the appropriate entry.

6. Done.

7. Done.

8. Done (unless the user explicitly changes it to something else)

9. Done.

10. Fixed.

11. Done.

12. Fixed.

13. Done.

14. Done.

15. No, they shouldn't. The only statement about "separators" in the WG's description of Rivalry says to use a semicolon. The examples show both a semicolon used to separate those items and a comma. HD will continue to use semicolon.

16. No. See (5) above.

17. Fixed.

18. Done.

19. Done.