SIZENUM: for sequencing of sizes

Activity

Show:
Tom Parker
February 9, 2015, 11:00 PM
Edited

Currently, the Size objects are indexed by sequence in the file. This makes it rather hard to expand, and basically impossible to load from multiple files. The eventual goal is to move things out of the game mode and into other places, and this is one of the things that keeps Size stuck.

It also has a unique set of code associated with it that I would like to retire

This is a proposal for a new token: SIZENUM

SIZENAME:Small <> SIZENUM:4

Rules for SIZENUM:

  • Required token. If a SIZE does not have a SIZENUM, load will fail.

    • Implied: This will cause loads to fail, so it is incompatible with existing data.

  • Must be an integer

  • When data load is complete:

    • No value may be used by more than one SizeAdjustment

Tom Parker
July 27, 2015, 7:44 AM

PR #397

Andrew Maitland
August 1, 2015, 8:04 PM

jdempsey-au merged commit b3ce771 into PCGen:master 5 days ago

Andrew Maitland
August 1, 2015, 8:05 PM

- Assigned to you for the documentation side.

Li-aung Yip
August 2, 2015, 4:13 PM
Edited

Documented; see https://github.com/PCGen/pcgen/pull/413 .

Actually, the entire page about `sizeadjustment.lst` needed some love and attention, so I re-wrote it from scratch.

Finally getting the hang of JIRA workflows. Don't need to create separate `DOCS` issues at all.

Assignee

Unassigned

Reporter

Tom Parker

Labels

None

Theme

None

Dependent Data

None

Subtype

Token

Epic/Theme

None

Pending User Input

No

Components

Fix versions

Affects versions

Priority

Minor
Configure