Difference between revisions of "OS Sheet Improvement Discussion"

From PCGen Wiki
Jump to: navigation, search
(Update Issues - ask clarification)
(Update details)
 
Line 29: Line 29:
 
* Age, Gender, Race - Not sure of benefit in moving these over leaving as is.
 
* Age, Gender, Race - Not sure of benefit in moving these over leaving as is.
 
* Points - Character generation points? Do they need outputting at all?
 
* Points - Character generation points? Do they need outputting at all?
* Reduce header line to just 2 rows.
+
* Reduce header line to just 2 rows. - We need to keep it three rows or else the thumbnail doesn't fit. [[User:LegacyKing|LegacyKing]] 17:06, 16 March 2012 (EST)
  
  
Line 91: Line 91:
 
Include files /templating
 
Include files /templating
 
* not a quick fix - simplify building new OS by providing building blocks for each individual section on the OS, to be arranged on the page by end users.
 
* not a quick fix - simplify building new OS by providing building blocks for each individual section on the OS, to be arranged on the page by end users.
 
  
 
=== [[Spell List Suggested Improvements]] ===
 
=== [[Spell List Suggested Improvements]] ===

Latest revision as of 06:06, 16 March 2012

Intro

Discussion from thread http://games.groups.yahoo.com/group/pcgen/message/107383 migrated here for ease of use

Screen Shots of Experimental Changes

A list of suggested updates to the character output sheet.

General Aims:

Improve the format through reorganisation and alternative display styles to reduce the overall page count of an OS (primarily by improving spell lists).

Ensure that the majority of the regularly used information (specifically combat related) appears on the first page (or first 2 pages at least), this involves moving some less used information to subsequent pages.

Allow 'equipment' changes to be made, and only require a re-print of the first few (ideally 1 or 2) pages - this may already be satisfied.


Suggestions

Move fields off P1 onto Bio page.

(most of the 'descriptive' fields are not referenced very often, so aren't need on the first page)

  • Alignment (to help keep such information secret for those in disguise) JIRA
  • Region - can also be a giveaway for disguised characters.
  • Deity - move to keep secret, do clerics really need a reminder on P1? JIRA
  • Height, Weight - though can be useful as they come into play for traps. JIRA (covers descriptive fields in general, as an option)
  • Eyes, Hair - Any reason to duplicate these on P1 and Bio?
  • Age, Gender, Race - Not sure of benefit in moving these over leaving as is.
  • Points - Character generation points? Do they need outputting at all?
  • Reduce header line to just 2 rows. - We need to keep it three rows or else the thumbnail doesn't fit. LegacyKing 17:06, 16 March 2012 (EST)


Remove duplicated fields

  • BAB - listed by itself, and then for each variation of Melee, Ranged, Grapple and CMD - Done on Exp Sheet LegacyKing 10:30, 15 March 2012 (EST)

Add fields to P1

  • Effective Level & Challenge Rating - Done LegacyKing 10:30, 15 March 2012 (EST)
  • Templates applied (Rage is the biggie - Barbarians want two copies of P1 and need to differentiate) JIRA
  • Spell effects applied (potential for very large list, perhaps limited display)
  • Companions box - who's who in the party is often referred to (in my group) JIRA
    • This is on the notes page, not sure we have any room on P1, this can easily be left on the Bio / Notes Page LegacyKing 10:30, 15 March 2012 (EST)
  • Party Companions box - is there any benefit to having just of list of PC's separately to Companions?
    • Duplicate of above LegacyKing 10:30, 15 March 2012 (EST)


Update fields

  • AC split out for all the possible types of enhancements
    • Added Morale, Insight, Sacred and Profane - Done LegacyKing 10:30, 15 March 2012 (EST)
  • More weapons being displayed on P1
    • This is tricky as the room available changes based upon class abilities LegacyKing 10:30, 15 March 2012 (EST)
  • Skills broken out to show class, feat, equipment modifiers
    • The available room leaves this as a "Would be nice" otherwise, either the columns become extremely tiny, and we get complaints of text being to small, or skills get moved to another page for a full display. LegacyKing 10:30, 15 March 2012 (EST)
  • Shift Miss Chance, ASF, ACP, Spell Resistance down a row (freeing up space for AC details) - Complete [Condensed Sheet]
  • Shift Speed, DR, Subdual down a row
  • Move HP 'box' to far right, reduce size of box and use Margin for continued damage notes JIRA
    • This presents some additional work as the HP Row has two displays based upon Game Mode [Vitality & Wounds vs. HP] LegacyKing 10:30, 15 March 2012 (EST)
  • Move Subdual damage box to far right, as per HP
    • Please Clarify this request, I can't have two fields in the same "Far Right" so which one is where? LegacyKing 10:30, 15 March 2012 (EST)
  • Encumbrance to persist (even 'light' should still show, and show limit before reaching next bracket)
  • Turning table - using that space for non-clerics, adding special attacks into that space (but what to do with multi-class that need both?)
    • uhg - Turning Table isn't the only table that occupies that space, that also houses Bombs, Raging, and plenty of other special abilities. If someone wishes to add something there, they can already do so with a Checklist Box (Otherwise, you'll be taking up valuable space again). LegacyKing 10:30, 15 March 2012 (EST)
    • Second issue, those Checkbox Abilities don't port nicely to a second page so need to fix that as well.
  • Equipment - ensure that changes to carried equipment only affects first two pages (avoid reprinting entire sheet) JIRA
    • CLARIFY this request please. Are you asking that Equipment only be on the second page? LegacyKing 10:30, 15 March 2012 (EST)
  • Prevent a large portrait from pushing the 'stats' section down. - Completed [Thumbnail now used for front page]
  • Force portrait on P1 to be a small picture (limited to header size)? - Completed
  • Conditional Modifiers - move to one side, or bottom of page(?) to allow extended notes in margin?
    • It fits in that section next to Saves, moving it to a side is going to either take up Skills Section, Attack Section - Please explain in greater detail on where it should go. LegacyKing 10:30, 15 March 2012 (EST)
  • Feats ('disadvantages' on Drews sample sheet) - limit source name to prevent long feats/disadvantages from wrapping rather than forcing 70%/30% split.
    • This cannot be done with the existing set up. Source Names should be limited to Short by default, but I can't enforce that, it's a preference thing. Either Source ends up trailing the Name of the ability (Ugly), takes up another line by itself on a line, or we can throw it at the end of the description. In most cases, the existing set up saves space. I can try and alter the space, but that is a lot of work. LegacyKing 10:30, 15 March 2012 (EST)
  • Footer - unbold the 'character:' and 'Player:' prefixes, leaving just the actual tokens bold.
  • Simple weapon display - put 'total attack bonus' and 'damage' as prefixes to the actual value rather than a separate row


Display style

  • Bio/header information has a line between the data and the title, alter this to make it more intuitive
    • (box the info together or put the title as a prefix to the token?)
  • Use initial caps rather than all caps on headers


Page order

  • With double sided printing, pages 2 & 3 become more valuable open side by side in a binder, thus page 1 becomes essentially just a cover sheet. However, single sided printing seems more favourable currently.

Filing Assistance

  • To aid in finding a specific character, NPC or monster from a ring binder:
  • Level/ECL/CR prominent on P1 -done LegacyKing 10:30, 15 March 2012 (EST)
  • Character Name, Player Name & Level on footer of every page JIRA-done LegacyKing 10:30, 15 March 2012 (EST)
  • Type & Subtype prominent on P1

Include files /templating

  • not a quick fix - simplify building new OS by providing building blocks for each individual section on the OS, to be arranged on the page by end users.

Spell List Suggested Improvements