Questions regarding new system

TCArknight · Jul 30, 2009

Howdy!

I am attempting to implement the CODA game rules from Decipher's Star Trek and Lord of the Rings games. I've made a little progress, but have a couple of questions on how to proceed..

I'm starting with the Star Trek rules, and these questions have come up:

1) How do I make an attribute (Psionics) hidden unless the character has an ability that allows it (Psionic Talent which allows the Attribute and starts at a score of 4 )?

2) How do I add fields to skills? I need to add a field that indicates whether a skill is useable untrained or Trained only, as well as one for making a skill fit one of four categories (Academic, Physical, Social or Psionic)

3) How do I hide Psionic skills unless the Psionic Attribute is visible?

4) In the CODA system, a skill can be:
a) The skill itself where the ranks are applied only for that skill. i.e. Empathy 3
b) A Specialty of a base skill and a character can have several specialties for a skill. i.e. System Operation (Helm)(Sensors) 4
c) One of a Group of skills, each individual and separate (But subskills of the same base). i.e. Science (Chemistry 4, Physics 2)

5) How do I calculate and display a modifier score for an attribute? i.e. Score of 1 is a -3 modfier, 4 is a 0 modifier or 10 is a +2 modifier
a) I'm thinking a script that pulls the final value of the attribute and assigns the modifier based on that score..?

I'm trying to get the basic information down for now... more in-depth creation questions wll be coming I'm sure.

Thanks!
Thomas

Mathias · Jul 30, 2009

TCArknight said:
1) How do I make an attribute (Psionics) hidden unless the character has an ability that allows it (Psionic Talent which allows the Attribute and starts at a score of 4 )?

Your psionics attribute will be auto-added with all the other attributes. On the tables that display attributes (on the basics tab, the summary, the dashboard, and the character sheet), you'll put in a live expression of:

Code:

<live>!Hide.Attribute</live>

Because of that, any attribute that has the Hide.Attribute tag will not be displayed in the attributes list.

Your talent will assign a hero tag (Hero.Psionic for example) once it's added, and a script on the Psionic attribute will assign itself Hide.Attribute unless the hero is psionic. Looking for a hero tag instead of the talent allows supplement X to add a different version of the psionic talent that works differently, but still uses the same psionics attribute.

Read through the Savage Worlds walkthrough sections on arcane backgrounds. It sounds like psionics act much like them.

TCArknight said:
2) How do I add fields to skills? I need to add a field that indicates whether a skill is useable untrained or Trained only, as well as one for making a skill fit one of four categories (Academic, Physical, Social or Psionic)

In traits.str is where fields are defined, but what you're describing are best done with tags. You'll create a tag (like SkillUse.Trained) to mark if a skill can only be used once trained (no tag means it can be used untrained).

This page of the Savage Worlds walkthrough includes creating categories for the various edges (defining categories for your skills will work the same way):
http://hlkitwiki.wolflair.com/index.php5/Edge_Support_(Savage)

TCArknight said:
3) How do I hide Psionic skills unless the Psionic Attribute is visible?

This page of the Savage Worlds walkthrough covers that:
http://hlkitwiki.wolflair.com/index.php5/More_on_Arcane_Backgrounds_(Savage)

TCArknight said:
4) In the CODA system, a skill can be:
a) The skill itself where the ranks are applied only for that skill. i.e. Empathy 3
b) A Specialty of a base skill and a character can have several specialties for a skill. i.e. System Operation (Helm)(Sensors) 4
c) One of a Group of skills, each individual and separate (But subskills of the same base). i.e. Science (Chemistry 4, Physics 2)

I'm afraid I'll need more detail on how skills work before I can work out how they should be defined in HL.

Does an individual skill only belong in one of those three categories? Ex: the empathy skill has no specialties/grouping?

If you have specialties for a skill, are they all at the same level? Or is the grouping of skills you describe essentially two different specialties of Science, each at different levels?

It may help to think in terms of existing examples. In the Cortex files, skills and specialties are separate, with the specialties always sorting themselves under the skill (and then some scripts to make a gun figure out whether it should be using the pistols specialty or the guns skill, or whether the character is unskilled). In WoD, specialties tend to be more along the lines of modifications of existing skills, that don't change their parent as much, so they're displayed in their own table. In d20, there are many perform skills, but since the maximum matters to a bard, a separate component searches through all the perform skills to find the maximum value among them.

TCArknight said:
5) How do I calculate and display a modifier score for an attribute? i.e. Score of 1 is a -3 modfier, 4 is a 0 modifier or 10 is a +2 modifier
a) I'm thinking a script that pulls the final value of the attribute and assigns the modifier based on that score..?

Bingo. The thing to watch out for here is timing. You'll put this script slightly after the script that calculates trtFinal, then derive the modifier from trtFinal.

TCArknight · Jul 30, 2009

mgehl said:
Your psionics attribute will be auto-added with all the other attributes. On the tables that display attributes (on the basics tab, the summary, the dashboard, and the character sheet), you'll put in a live expression of:

Code:

<live>!Hide.Attribute</live>

Because of that, any attribute that has the Hide.Attribute tag will not be displayed in the attributes list.

Your talent will assign a hero tag (Hero.Psionic for example) once it's added, and a script on the Psionic attribute will assign itself Hide.Attribute unless the hero is psionic. Looking for a hero tag instead of the talent allows supplement X to add a different version of the psionic talent that works differently, but still uses the same psionics attribute.

Read through the Savage Worlds walkthrough sections on arcane backgrounds. It sounds like psionics act much like them.

This is what I've got on the Attribute portal and the assign on the Attribute:

Code:

  <portal
    id="baAttrib"
    style="tblInvis">
    <table_fixed
      component="Attribute"
      showtemplate="baAttrPick"
      showsortset="explicit"
      scrollable="no">
      <headertitle><![CDATA[
        @text = "Attributes"
        ]]></headertitle>
     </table_fixed>
    <live>!Hide.Attribute</live>
    </portal>

  <thing
    id="attrPsi"
    name="Psionics"
    compset="Attribute"
    isunique="yes"
    description="Description goes here">
    <fieldval field="trtAbbrev" value="Psi"/>
    <tag group="explicit" tag="7"/>
    <eval index="1" phase="Setup" priority="100"><![CDATA[
        perform assign[Hide.Attribute]
        ]]></eval>
    </thing>

except the Psionics attribute still shows up.

mgehl said:
In traits.str is where fields are defined, but what you're describing are best done with tags. You'll create a tag (like SkillUse.Trained) to mark if a skill can only be used once trained (no tag means it can be used untrained).

This page of the Savage Worlds walkthrough includes creating categories for the various edges (defining categories for your skills will work the same way):
http://hlkitwiki.wolflair.com/index.php5/Edge_Support_(Savage)

Ok, I added this to tags.1st:

Code:

<!-- Skill Type group -->
  <group
    id="SkillType">
    <value id="Academic"/>
    <value id="Physical"/>
    <value id="Social"/>
    <value id="Psionic"/>
    </group>

and I add this to the Skill:

Code:

<tag group="SkillType" tag="Academic" />

and get a message about 'Encountered unknown element tag 'tag' ' And that happens even if I add the <tag group="DashTacCon" tag="NonCombat"/> mentioned in the skeleton files. Am I missing something in the Skills trait?

mgehl said:
I'm afraid I'll need more detail on how skills work before I can work out how they should be defined in HL.

Does an individual skill only belong in one of those three categories? Ex: the empathy skill has no specialties/grouping?

If you have specialties for a skill, are they all at the same level? Or is the grouping of skills you describe essentially two different specialties of Science, each at different levels?

It may help to think in terms of existing examples. In the Cortex files, skills and specialties are separate, with the specialties always sorting themselves under the skill (and then some scripts to make a gun figure out whether it should be using the pistols specialty or the guns skill, or whether the character is unskilled). In WoD, specialties tend to be more along the lines of modifications of existing skills, that don't change their parent as much, so they're displayed in their own table. In d20, there are many perform skills, but since the maximum matters to a bard, a separate component searches through all the perform skills to find the maximum value among them.

a) Yes, a skill can only belong in one of the three groupings.
b) A specialty of a skill is narrower use of the overall skill, so adds a +2 to the total roll for use of that specialty. It doesn't affect ranks themselves except for costing less to purchase and advance.
c) It would be as if you had the two skills: Science - Chemistry 4 and Science - Physics 2. Each subskill is treated as a seperate skill for costs, etc. However, when creating a character, one of the added skills might be something like Science (Any) 2 which means "choose a skill from the science skill group at rank 2".

mgehl said:
Bingo. The thing to watch out for here is timing. You'll put this script slightly after the script that calculates trtFinal, then derive the modifier from trtFinal.

Mathias · Jul 30, 2009

TCArknight said:
and get a message about 'Encountered unknown element tag 'tag'

That error means you have the elements of the thing out of order.

http://hlkitwiki.wolflair.com/index.php5/Thing_Element_(Data)

Scroll down that page until you get to the list of elements (they're all links, so it's easy to see whn you've gotten to that section of the list). The order they're listed in there has to be followed. I'm guessing you put your new <tag/> line as the first or last line in the skill.

TCArknight said:
a) Yes, a skill can only belong in one of the three groupings.
b) A specialty of a skill is narrower use of the overall skill, so adds a +2 to the total roll for use of that specialty. It doesn't affect ranks themselves except for costing less to purchase and advance.
c) It would be as if you had the two skills: Science - Chemistry 4 and Science - Physics 2. Each subskill is treated as a seperate skill for costs, etc. However, when creating a character, one of the added skills might be something like Science (Any) 2 which means "choose a skill from the science skill group at rank 2".

Could you have both System Operation 4 and System Operation (Helm) 5 (total roll 7, because of the +2 for a specialty)?

Or, once you take the system operation skill, do you have the option to restrict it to one or more specialties, trading the general effectiveness of the skill for better rolls in those specialties? If so, is there a limit to the number of specialties per skill (if it's a max of 2 or 3, you can put menus on the skills to select the specialties - if it's more, you're going to need a table that allows the user to select them all).

Would it work to handle the third option with requirements? - The character class (or whatever) grants you the skill points you'd need to buy Science (XXX) 2, and has an eval rule that requires that you have at least one science skill at a rating of 2 or more. It's then up to the user to buy the science skill they want, with the program complaining until they do?

If the character's maximum science skill isn't something that's used, I'd suggest you add Science (chemistry) and Science (physics) as separate skills, with the same skill grouping tag. On the other hand, if the skills are listed as Science (Chemistry 4, Physics 2) on a character sheet, you're going to need a parent skill. Parent skills would display themselves on the character sheet, and then find and display all their child skills. Normal skills (like empathy) would just display themselves.

TCArknight · Aug 1, 2009

Ok, I'm not worrying about the skills at the moment, so thought I'd tackle something a bit simpler... or so I thought.

Each character has 4 stats based on the modifiers of one of two attributes (I take the max of the two in a script) These are called Reactions in the game.

What I did, was duplicate everything for Traits and change it to Reaction. The Reactions should show up in the lower right panel on the Basics tab. However, they don't. Seems like no matter what I change in the Pick template, I can't get the Reactions to show up.

I've got a Reaction compset, and a Reaction Component set up, but no luck.

What am I missing?

I've attached the zip of the data files.
View attachment StarTrek.zip

Thanks!
Thomas

Mathias · Aug 2, 2009

In the bootstraps.1st file, there is an enmasse entry that adds all derived traits to every character. Do you have a way to add your reactions to the characters that need them?

TCArknight · Aug 2, 2009

Not that I've come up with. Reactions are normal Characteristics, as much as the Attributes.

I'm playing around with a couple of other ideas and going back through the walkthrough to see what I missed...

TCArknight · Aug 2, 2009

Well, I added the enmasse entry for Reactions and they showed up. I guess I missed that in the walkthrough... :

:

Couple of things:
1) any ideas why this script isn't working?

Code:

  <scriptmacro
    name="traitmod"
    param1="trait"
    result="hero.child[#trait].field[trtMod].value"/>

    <!-- Attribute modifier -->
    <field
      id="trtMod"
      name="Modifier"
      type="derived">
      </field>

    <!-- Calculate the modifier for the Attribute -->
      <eval index="3" phase="Traits" priority="5000"><![CDATA[
        ~base our test on the adjusted trait value, sans any in-play adjustments
        var trait as number
        trait = field[trtFinal].value
        if (trait <= 1) then
          field[trtMod].value = -3
        elseif (trait = 2) then
          field[trtMod].value = -2
        elseif (trait = 3) then
          field[trtMod].value = -1
        elseif (trait = 4) then
          field[trtMod].value = 0
        elseif (trait = 5) then
          field[trtMod].value = 0
        elseif (trait = 6) then
          field[trtMod].value = 0
        elseif (trait = 7) then
          field[trtMod].value = 0
        elseif (trait = 8) then
          field[trtMod].value = 1
        elseif (trait = 9) then
          field[trtMod].value = 1
        elseif (trait = 10) then
          field[trtMod].value = 2
        elseif (trait = 11) then
          field[trtMod].value = 2
        elseif (trait = 12) then
          field[trtMod].value = 3
        elseif (trait = 13) then
          field[trtMod].value = 3
        elseif (trait = 14) then
          field[trtMod].value = 4
        elseif (trait = 15) then
          field[trtMod].value = 4
        elseif (trait = 16) then
          field[trtMod].value = 5
        elseif (trait = 17) then
          field[trtMod].value = 5
        elseif (trait = 18) then
          field[trtMod].value = 6
        elseif (trait = 19) then
          field[trtMod].value = 6
        elseif (trait = 20) then
          field[trtMod].value = 7
        elseif (trait = 21) then
          field[trtMod].value = 7
        elseif (trait = 22) then
          field[trtMod].value = 8
        elseif (trait = 23) then
          field[trtMod].value = 8
        endif
        ]]></eval>

<thing
      id="reQuick"
      name="Quickness"
      compset="Reaction"
      isunique="yes"
      description="Description goes here">
      <fieldval field="reaAbbrev" value="Qui"/>
      <tag group="explicit" tag="1"/>
      <tag group="DashTacCon" tag="Combat"/>
      <eval index="1" phase="Traits" priority="4000">
        <before name="Derived trtFinal"/>
        <after name="Calc trtFinal"/><![CDATA[
        ~Quickness uses the better of the character's Perception or Agility modifier

        field[reaBonus].value = maximum(#traitmod[attrPer],#traitmod[attrAgi])
        ]]></eval>
      </thing>

The eval script seems to update the trtMod field properly, but the #traitmod always seems to be returning a value of 0.

2) What am I missing to make the Psionics attribute not appear unless have the Psionics talent.

Code:

  <thing
    id="attrPsi"
    name="Psionics"
    compset="Attribute"
    isunique="yes"
    description="Description goes here">
    <fieldval field="trtAbbrev" value="Psi"/>
    <tag group="explicit" tag="7"/>
    <eval index="1" phase="Setup" priority="1000"><![CDATA[
        perform assign[Hide.Attribute]
        ]]></eval>
    </thing>

  <template
    id="baAttrPick"
    name="Attribute Pick"
    compset="Attribute"
    marginhorz="18"
    marginvert="9">

    <live>!Hide.Attribute</live>
    
    <portal
      id="name"
      style="lblXLarge"
      showinvalid="yes">
      <label
        field="name">
        </label>
      </portal>
...
</template>

rob · Aug 5, 2009

TCArknight said:
1) any ideas why this script isn't working?

Code:

 <eval index="3" phase="Traits" priority="5000"> ]]></eval> <eval index="1" phase="Traits" priority="4000"> <before name="Derived trtFinal"/> <after name="Calc trtFinal"/> </eval>

The eval script seems to update the trtMod field properly, but the #traitmod always seems to be returning a value of 0.

Look at your timing. The script that sets the value of the trtMod field occurs at Traits/5000. The script that checks the value occurs at Traits/4000. So you are checking the value before its been set. That's why it's returning zero.

rob · Aug 5, 2009

TCArknight said:

2) What am I missing to make the Psionics attribute not appear unless have the Psionics talent.

Code:

  <thing
    id="attrPsi"
    name="Psionics"
    compset="Attribute"
    isunique="yes"
    description="Description goes here">
    <fieldval field="trtAbbrev" value="Psi"/>
    <tag group="explicit" tag="7"/>
    <eval index="1" phase="Setup" priority="1000"><![CDATA[
        perform assign[Hide.Attribute]
        ]]></eval>
    </thing>

  <template
    id="baAttrPick"
    name="Attribute Pick"
    compset="Attribute"
    marginhorz="18"
    marginvert="9">

    <live>!Hide.Attribute</live>
</template>

You are always assigning the Hide.Attribute tag to the thing, which is why it is never showing up. I think what you should be doing is two-fold. First, assign the Hide.Attribute tag via a "tag" element instead of the Eval script. This will have it never appear under normal circumstances. You can do that by adding:

Code:

        <tag group="Hide" tag="Attribute"/>

Second, use the Eval script to determine whether to make the attribute appear. If it is supposed to appear, then you can delete the tag from the pick. You'd probably base this on the presence of a tag somewhere on the hero. The script would look like:

Code:

    <eval index="1" phase="Setup" priority="1000"><![CDATA[
      if (hero.tagis[Hero.Psionics] <> 0) then
        perform delete[Hide.Attribute]
        endif
        ]]></eval>

Note that I just used a tag I concocted here, so you should use whatever you decide instead. Also, you'll probably need the timing to be much different from Setup/1000, since this is very early and you'll likely want to schedule it after the Psionics tag has been added somewhere.

TCArknight · Aug 5, 2009

rob said:
You are always assigning the Hide.Attribute tag to the thing, which is why it is never showing up. I think what you should be doing is two-fold. First, assign the Hide.Attribute tag via a "tag" element instead of the Eval script. This will have it never appear under normal circumstances. You can do that by adding:

Code:

<tag group="Hide" tag="Attribute"/>

Second, use the Eval script to determine whether to make the attribute appear. If it is supposed to appear, then you can delete the tag from the pick. You'd probably base this on the presence of a tag somewhere on the hero. The script would look like:

Code:

<eval index="1" phase="Setup" priority="1000"><![CDATA[ if (hero.tagis[Hero.Psionics] <> 0) then perform delete[Hide.Attribute] endif ]]></eval>

Note that I just used a tag I concocted here, so you should use whatever you decide instead. Also, you'll probably need the timing to be much different from Setup/1000, since this is very early and you'll likely want to schedule it after the Psionics tag has been added somewhere.

Rob,

Thanks for the help!

The problem I was having is that even though it had the !Hide.Attribute <live> tag on the pick template, that wasn't having any effect. It wasn't never showing up, it was always visible no matter what.... I'll try changing some timings around and see what happens.

HL rocks and even though it's a tough learning curve, the flexibility it offers is bar-none.

rob · Aug 7, 2009

TCArknight said:
The problem I was having is that even though it had the !Hide.Attribute <live> tag on the pick template, that wasn't having any effect. It wasn't never showing up, it was always visible no matter what.... I'll try changing some timings around and see what happens.

Oops. I'm too rushed right now with all the prep for GenCon. So I missed that detail.

By putting the Live tagexpr on the *template*, you are not going to get the behavior you want at all. The Live tagexpr on the template performs the test against the tags on the *hero*. It also only applies to templates that are *not* used within tables. If a template is used for table, the live state of the table *portal* dictates whether the table appears or not.

If I understand correctly, you want all attributes to appear in the table, except for the Psionics attribute. That one attribute should be controlled via the presence of a tag. To accomplish this, you need to control what appears *within* the table - not the visibility of the table itself. You control the contents of a table via the Live tagexpr within the table *portal* - not the template.

Using the standard table portal used within the Skeleton files as a starting point, the revised table portal would look like below with the added restriction of only showing attributes that are lacking the tag.

Code:

  <portal
    id="baAttrib"
    style="tblInvis">
    <table_fixed
      component="Attribute"
      showtemplate="baAttrPick"
      showsortset="explicit"
      scrollable="no">
      <live>!Hide.Attribute</live>
      <headertitle><![CDATA[
        @text = "Attributes"
        ]]></headertitle>
      </table_fixed>
    </portal>

TCArknight · Aug 7, 2009

Rob,

Thanks, but no luck.

When I have it the exact way you do, I get "Encountered Unknown element tag 'live' "

Code:

<portal
    id="baAttrib"
    style="tblInvis">
    <table_fixed
      component="Attribute"
      showtemplate="baAttrPick"
      showsortset="explicit"
      scrollable="no">
     <live>!Hide.Attribute</live>
      <headertitle><![CDATA[
        @text = "Attributes"
        ]]></headertitle>
     </table_fixed>
    </portal>

rob · Aug 7, 2009

Doh! That should be "list" instead of "live". Sorry, I'm just too frazzled and sleep-deprived with the big crunch leading into GenCon in a few days. My brain knew it was "list", but my fingers just typed "live" because that's what I had been looking at in your post. Sorry!

TCArknight · Aug 7, 2009

LOL 's ok.

I just wish I was able to get to GenCOn, meet you all and attend some seminars.

I completely understand how rough it must be. Just enjoy the Con and keep cranking out the good stuff! LOL

Edit: Oh, one other related thing.

I'm trying to use: perform assign[Edge.IsPsionic] when the Psionic edge is added. I get an error that Edge.IsPsionic not defined.

I've got this in tags.1st:
<group
id="Edge"
dynamic="yes">
<value id="Edge"/>
</group>

What am I missing?

Mathias · Aug 7, 2009

Even if your tag group is dynamic, you should add any tags you intend to use before using them in a script.

Currently, your only Edge tag is Edge.Edge

Also, for testing purposes, don't you want to use:
perform hero.assign[Edge.IsPsionic], so that the tag is on the hero, and not wherever your script is?

TCArknight · Aug 7, 2009

Thanks!

That did it!

Making much greater progress now!

TCArknight · Aug 8, 2009

Another Snag...

Howdy!

Ran into another snag...

I'm trying to allow the choice of one of the 4 reactionsto gain a bonus. From looking at the walkthrough, I should probably use the following portal:

Code:

    <portal
      id="menu1"
      style="menuSmall">
      <menu_things
        field="usrChosen1"
        component="none"
        maxvisible="10"
        usepicksfield="usrSource1"
        candidatefield="usrCandid1">
        </menu_things>
      </portal>

I've added this tag to all selectable reactions: <tag group="RAbil" tag="Adaptable"/>

However, although I get Adaptable: -choose- in red for the racial ability the menu to choose never shows up.

My template and the Racial ability:

Code:

<thing
  id="abAdapt"
  name="Adaptable"
  compset="RaceAbil"
  isunique="yes"
  description="Description goes here">
  <fieldval field="usrCandid1" value="thingid.Adaptable"/>
  <tag group="Hide" tag="Ability"/>
  <tag group="Hide" tag="RaceAbil"/>
  <tag group="ChooseSrc1" tag="Hero"/>

    <!-- Bootstrap Choose either Sta, Qui, Wil for a +2 bonus -->
  </thing>

  <template
    id="raPick"
    name="Racial Ability Pick"
    compset="RaceAbil"
    marginhorz="3"
    marginvert="2">

    <portal
      id="name"
      style="lblNormal"
      showinvalid="yes">
      <label
        field="name">
        </label>
      </portal>

    <portal
      id="menu1"
      style="menuSmall">
      <menu_things
        field="usrChosen1"
        component="none"
        maxvisible="10"
        usepicksfield="usrSource1"
        candidatefield="usrCandid1">
        </menu_things>
      </portal>

    <portal
      id="info"
      style="actInfo">
      <action
        action="info">
        </action>
      <mouseinfo/>
      </portal>

    <portal
      id="delete"
      style="actDelete"
      tiptext="Click to delete this item">
      <action
        action="delete">
        </action>
      </portal>

    <position><![CDATA[
      ~set up our height based on our tallest portal
      height = portal[info].height

      ~if this is a "sizing" calculation, we're done
      doneif (issizing <> 0)

      ~determine whether our menus are visible
      ~Note: Remember that a non-empty tagexpr field indicates menu selection is used.
      ~if (field[usrCandid1].isempty <> 0) then
        portal[menu1].visible = 0
      ~  endif

      ~position our tallest portal at the top
      portal[info].top = 0

      ~center the other portals vertically
      perform portal[name].centervert
      perform portal[delete].centervert
      perform portal[menu1].centervert

      ~position the delete portal on the far right
      perform portal[delete].alignedge[right,0]

      ~position the info portal to the left of the delete button
      perform portal[info].alignrel[rtol,delete,10]

      ~position the menus to the left of the info in the available space
      perform portal[menu1].alignrel[rtol,info,10]
      portal[menu1].width = (portal[info].left - portal[menu1].left - 20) / 2

      ~position the name on the left and use availble space, with a gap for menus
      portal[name].left = 0
      ~portal[name].width = minimum(portal[name].width,portal[menu1].left - portal[name].left)
      portal[name].width = 50

      ~if the ability is auto-added, change its font to indicate that fact
      if (candelete = 0) then
        perform portal[name].setstyle[lblAuto]
        endif
      ]]></position>

    </template>

What am I missing? Is my sizing and positioning off? I set the visibility always to 0, so I thought it would always show up even if there wasn't anything in the usrCandid1 field.

Suggestion?

Thanks!
Thomas

TCArknight · Aug 8, 2009

Also:

Code:

  <component
    id="DeReac"
    name="Derived Reaction"
    autocompset="no">

    <!-- Derived traits are based on other traits. The "calculate" script on the
        "trtFinal" field value will work great for most traits, but NOT for derived
        traits. Consequently, derived traits need to re-calculate the field value AFTER
        the traits derived from are properly calculated. So the individual calculation
        scripts for each derived trait must occur AFTER the initial "trtFinal"
        calculation and BEFORE this derived calculation. We can also omit any "user"
        value from the calculation since derived traits have no user-defined facet.
        -->
    <eval index="1" phase="Traits" priority="6000" name="Derived reaFinal"><![CDATA[
      field[reaFinal].value = field[reaBonus].value + field[reaInPlay].value
      ]]></eval>

    </component>

<thing
  id="abBraklul"
  name="Brak'lul"
  compset="RaceAbil"
  isunique="yes"
  description="Description goes here">
  <tag group="Hide" tag="Ability"/>
  <tag group="Hide" tag="RaceAbil"/> 
    
    <eval value="1" phase="Traits" priority="10000">
      <![CDATA[
      var total as number 
      total = hero.child[reStamina].field[reaBonus].value

      total += 2

      hero.child[reStamina].field[reaBonus].value = total

      ]]></eval>
    </thing>

Doesn't seem to be working. It's the last Eval in the Traits phase and after the Stamina is calculated initially. What am I missing?

rob · Aug 8, 2009

TCArknight said:
I've added this tag to all selectable reactions: <tag group="RAbil" tag="Adaptable"/>

Code:

<fieldval field="usrCandid1" value="thingid.Adaptable"/>

The first issue is that you'll never have anything show up in the menu to select from with this tagexpr. You have assigned the tag "RAbil.Adaptable", but you will only be showing picks that possess the "thingid.Adaptable" tag. You need to change the tagexpr to match the tag you've assigned.

Questions regarding new system

Well-known member

Moderator

Well-known member

Moderator

Well-known member

Moderator

Well-known member

Well-known member

Administrator

Administrator

Well-known member

Administrator

Well-known member

Attachments

Administrator

Well-known member

Moderator

Well-known member

Well-known member

Well-known member

Administrator