PCGen :: An RPG Character Generator

[ http://jira.pcgen.org/browse/CODE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker resolved CODE-92.
----------------------------

    Resolution: Fixed

Fixed by other 5.17 work


> Automatic Spells not added when 'non-default' SPELLLIST is used
> ---------------------------------------------------------------
>
>                 Key: CODE-92
>                 URL: http://jira.pcgen.org/browse/CODE-92
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> 2nd issue spawned from     * TEST-13 - Class using SPELLLIST - test spell application
> When I used the SPELLLIST:2|Druid|Cleric
> The "Add Automatic Spells" did not add any of the 1st level spells, even after I leveled up to 2nd level. This was done using 
> CLASS:Cleric.MOD <tab> SPELLLIST:2|Cleric|Druid
> Thereby granting Cleric and Druid Spells to a Cleric. When you level you should be getting automatic spells with the check mark selected. This is not happening with a LG, Human Stats 10 across the board, Level Cleric 3 and no change. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker updated CODE-92:
---------------------------

      Status: In Progress  (was: Confirmed)
    Assignee: Tom Parker

> Automatic Spells not added when 'non-default' SPELLLIST is used
> ---------------------------------------------------------------
>
>                 Key: CODE-92
>                 URL: http://jira.pcgen.org/browse/CODE-92
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> 2nd issue spawned from     * TEST-13 - Class using SPELLLIST - test spell application
> When I used the SPELLLIST:2|Druid|Cleric
> The "Add Automatic Spells" did not add any of the 1st level spells, even after I leveled up to 2nd level. This was done using 
> CLASS:Cleric.MOD <tab> SPELLLIST:2|Cleric|Druid
> Thereby granting Cleric and Druid Spells to a Cleric. When you level you should be getting automatic spells with the check mark selected. This is not happening with a LG, Human Stats 10 across the board, Level Cleric 3 and no change. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker resolved CODE-90.
----------------------------

    Resolution: Fixed

Seems this has been resolved by intervening work.  
2	SPELLLEVEL:CLASS|Cleric=1|Lightning Bolt
with:
SPELLLIST:2|Cleric|Druid
in Druid now works
(Druid gets access to the spell)


> SPELLLEVEL will only add to a Class'es default list
> ---------------------------------------------------
>
>                 Key: CODE-90
>                 URL: http://jira.pcgen.org/browse/CODE-90
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> Summary says it all - from     * TEST-13 - Class using SPELLLIST - test spell application

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker updated CODE-90:
---------------------------

      Status: In Progress  (was: Confirmed)
    Assignee: Tom Parker

> SPELLLEVEL will only add to a Class'es default list
> ---------------------------------------------------
>
>                 Key: CODE-90
>                 URL: http://jira.pcgen.org/browse/CODE-90
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> Summary says it all - from     * TEST-13 - Class using SPELLLIST - test spell application

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker resolved CODE-87.
----------------------------

    Fix Version/s: 5.17.4 (Alpha) 
       Resolution: Fixed

Appears to work, used:
SPELLLEVEL:CLASS|Cleric=1|Fireball|PREVAREQ:CL,4 
on Cleric Level 1 line and it appeared when Cleric hit level 4


> SPELLLEVEL has Prereq Sensitivity
> ---------------------------------
>
>                 Key: CODE-87
>                 URL: http://jira.pcgen.org/browse/CODE-87
>             Project: Code
>          Issue Type: Bug
>          Components: Rules system (includes CDOM Referencing)
>            Reporter: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> Apply a SPELLLEVEL token with a trailing PRExxx
> This PRExxx must be context-specific, meaning something like:
> PREVARGT:CL,4
> (since CL is the class level, and thus is dependent on being in a specific Class in the Class LST file)
> MAKE SURE that the PRExxx will FAIL if the variable is miscalculated (assume the variable is returned as zero in a "broken" case)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker closed CODE-93.
--------------------------

    Resolution: Cancelled

SPELLS:Class|TIMES=1|CASTERLEVEL=max(TL,1)|Speak with Animals,11+WIS
When added to a level 1 (e.g. in Barbarian) displays properly on the Spells Tab.  
If this is still an issue, need further information to reproduce.


> SPELLS tag not working on CLASS LINE or CLASS LEVEL LINE
> --------------------------------------------------------
>
>                 Key: CODE-93
>                 URL: http://jira.pcgen.org/browse/CODE-93
>             Project: Code
>          Issue Type: Bug
>          Components: Rules (LST) persistence
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>             Fix For: 5.17.4 (Alpha) 
>
>
> Found during this test -     * TEST-4 - SPELLS may control fixed DC by spellbook
> SPELLS doesn't work in the Class File at all.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker closed CODE-89.
--------------------------

    Resolution: Cancelled

Both abilities appear if values are changed to integers - this is likely just due to significant changes in the core since this was reported.
Values in MOVECLONE must be integers, if not, it is reported as an error


> Ability with MOVECLONE is not visible
> -------------------------------------
>
>                 Key: CODE-89
>                 URL: http://jira.pcgen.org/browse/CODE-89
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>             Fix For: 5.17.4 (Alpha) 
>
>
> Summary says it all - this is from TEST-9 - Test Fractional Movement Multipliers

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker updated CODE-81:
---------------------------

      Status: In Progress  (was: Confirmed)
    Assignee: Tom Parker

> UMULT (Global) does not unparse .CLEAR
> --------------------------------------
>
>                 Key: CODE-81
>                 URL: http://jira.pcgen.org/browse/CODE-81
>             Project: Code
>          Issue Type: Bug
>          Components: LST Converter, Rules (LST) persistence
>    Affects Versions: 5.16.1, 5.16.2, 5.17.0 (Alpha), 5.17.1 (Alpha), 5.17.2 (Alpha), 5.17.3 (Alpha) 
>            Reporter: Tom Parker
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker resolved CODE-81.
----------------------------

    Fix Version/s: 5.17.4 (Alpha) 
       Resolution: Fixed

    Committed revision 13960.

> UMULT (Global) does not unparse .CLEAR
> --------------------------------------
>
>                 Key: CODE-81
>                 URL: http://jira.pcgen.org/browse/CODE-81
>             Project: Code
>          Issue Type: Bug
>          Components: LST Converter, Rules (LST) persistence
>    Affects Versions: 5.16.1, 5.16.2, 5.17.0 (Alpha), 5.17.1 (Alpha), 5.17.2 (Alpha), 5.17.3 (Alpha) 
>            Reporter: Tom Parker
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

add DOMAINLIST (and CLASSLIST) to KNOWNSPELLS
---------------------------------------------

                 Key: NEWTAG-230
                 URL: http://jira.pcgen.org/browse/NEWTAG-230
             Project: New Tag
          Issue Type: Modify Token
          Components: LST Tag
            Reporter: Andrew Maitland


In a FEAT/ABILITY, is there a way to use SYNTAX like the following?

KNOWNSPELLS:DOMAIN=DomainName
or
KNOWNSPELLS:TYPE=DOMAIN.DomainName

or do have I to code a differently named FEAT/ABILITY for every existing DOMAIN and add the list of Domain's Spells as a sequence of Spell's Names pipe-delimited?

===

Not possible today.

FREQ please to add DOMAINLIST (and CLASSLIST) to KNOWNSPELLS

TP.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

CONTAINS to 
------------

                 Key: NEWTAG-229
                 URL: http://jira.pcgen.org/browse/NEWTAG-229
             Project: New Tag
          Issue Type: Modify Token
            Reporter: Andrew Maitland


Is it possible to use the SIZE tag inside a CONTAINS tag? (I'm trying to use the CONTAINS tag to code what size (and how many of each) of creature can fit inside a certain size cage.)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

BONUS:ATTACKITERATION
---------------------

                 Key: NEWTAG-228
                 URL: http://jira.pcgen.org/browse/NEWTAG-228
             Project: New Tag
          Issue Type: New Token
          Components: LST Tag
            Reporter: Andrew Maitland


BONUS:ATTACKITERATION|x=y|z

x = PRIMARY, SECONDARY, ALL [indicates which hand this applies to]
x = NATURAL-PRIMARY
x = NATURAL-SECONDARY
y = Where the Iteration Bonus takes place (1, 2, 3, etc) [I'm debating whether a number or word 
would be easier to understand]
z = Bonus to HIT for the Named Iteration


This is used to apply variant bonuses to the different attacks without having to affect all the attacks.

Example:

BONUS:ATTACKITERATION|SECONDARY=2|5
Would add +5 to the Second Hand (Off-hand) for the Second iteration. If you had a Fighter with +10/+5 for the second attacks, they would be +10/+10 instead.

Ideally we want to cover as many possible solutions, giving us not just a pathfinder specific fix, 
but something useful for homebrews and other supplements. So think outside the box.




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

BONUS:INTERATION Proposal
-------------------------

                 Key: NEWTAG-227
                 URL: http://jira.pcgen.org/browse/NEWTAG-227
             Project: New Tag
          Issue Type: New Token
          Components: LST Tag
            Reporter: Andrew Maitland


BONUS:ITERATION|x=y|z

x = PRIMARY, SECONDARY, ALL [indicates which hand this applies to]

x = NATURAL-PRIMARY [only adds to an attack granted via the NATURALATTACKS tag (Primary is the First Attack listed, and shows up as NATURAL-PRIMARY equipped)]
x = NATURAL-SECONDARY [only add to an attack granted via the NATURALATTACKS tag]
y = Where the Iteration Bonus takes place (1, 2, 3, etc) [I'm debating whether a number or word 
would be easier to understand; I think the number is best as the system doesn't need to translate a word and numbers are universal]
z = Number of Extra Attacks added


BONUS:ITERATION|PRIMARY=FIRST|1
vs
BONUS:ITERATION|PRIMARY=1|1

This would add one additional Attack at the first (primary) attack
+1 would become +1 / +1

BONUS:ITERATION|PRIMARY=3|1

Would add a Third Attack Iteration to the Primary Hand


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Dempsey updated CODE-27:
------------------------------

    Component/s: UI

> when using any OpenJDK, the advanced source selection menu is blank due to a missing java feature
> -------------------------------------------------------------------------------------------------
>
>                 Key: CODE-27
>                 URL: http://jira.pcgen.org/browse/CODE-27
>             Project: Code
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 5.16.2
>         Environment: OS= FreeBSD
>            Reporter: Joseph S. Atkinson
>            Assignee: James Dempsey
>             Fix For: Unscheduled
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Submitter: jsa (on IRC channel)
> when using any OpenJDK, the advanced source selection menu is blank due to a missing java feature

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.pcgen.org/browse/CODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker resolved CODE-389.
-----------------------------

    Fix Version/s: 5.17.4 (Alpha) 
       Resolution: Fixed

    Committed revision 13953.

> CHOOSE:FEATSELECTION does not use primitives or qualifiers
> ----------------------------------------------------------
>
>                 Key: CODE-389
>                 URL: http://jira.pcgen.org/browse/CODE-389
>             Project: Code
>          Issue Type: Bug
>          Components: CHOOSE system
>    Affects Versions: Not Released
>            Reporter: Andrew Maitland
>            Assignee: Tom Parker
>             Fix For: 5.17.4 (Alpha) 
>
>
> CHOOSE:FEATSELECTION does not use primitives or qualifiers

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira