• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Deathwatch

What makes me think it's a foreach is that it's reporting exactly the same error, in exactly the same location, on a dozen different things. In order to get that, you have to have something that's being repetetive - that's performing the same operation on many different things.

I ended up fixing it. It was trying to find something on the conditions tab that didn't exist. I ended up creating a cIsOn field for the conditions and combat circumstances and removing the ability compref component from the component set. Seems to be working fine now.
 
Mathias,

What is the difference between needtag and denytag? Couldn't they both do the same things?

If I have a piece of equipment that is not available for purchase, could I just use this:

Code:
  denytag="Equipment.NoPurchase"

Wouldn't this keep the not available for purchase items off the list of available items?
 
Needtag and Denytag are opposites

Needtag: The thing you're adding MUST have at least one tag that matches the source tags.

Denytag: The thing you're adding MUST NOT have any tags that match the source tags.

Both needtag and denytag function on entire tag groups, and can't be targetted to specific tags.

For what you're trying to accomplish, use the existing Helper.Helper tag instead of creating a new tag, and you'll add it to the end of the candidate expression:

& !Helper.Helper
 
I thought it was, but it might be that we just add it to tags.1st so early in the process of creating a new game system that I forget it isn't already there.
 
Well you've been doing this a lot longer than me. I'll go ahead and add it in there.
I'll be back out mowing the lawn again soon if it doesn't start raining. Its hot today and humid. Bad combo for lawn work.
 
Mathias,

I tried adding the tag like you said, but HL gives me an error message on recompiling:
Unrecognized special token following '&'

Code:
      <candidate inheritlist="yes">!Equipment.Natural & !Helper.Helper</candidate>
 
Code:
<candidate inheritlist="yes"><![CDATA[!Equipment.Natural & !Helper.Helper]]></candidate>

or

Code:
<candidate inheritlist="yes">!Equipment.Natural & !Helper.Helper</candidate>

I prefer the first.
 
Mathias,

When you did the vehicles for Shadowrun, did they get their own basics tab? or did you just reconfigure the existing one to handle the vehicle statistics?
 
Mathias,

I figured out the image portal as you recommended, I've attached a screenshot of what the skills look like now.
 

Attachments

  • Skills tab Progress.JPG
    Skills tab Progress.JPG
    88.8 KB · Views: 10
Mathias,

I'm trying to make a couple pull down menus for chapters that get to choose which attributes they gain a +5 bonus to (Ultramarines get to pick two attributes instead of having fixed bonuses). I have set up the usrCandid fields on the chapter already, but for some reason the choosers are not appearing.

This is the template I created in visual.dat:
Code:
  <template
    id="MenuSlPick"
    name="Configurable Pick"
    compset="UserSelect"
    marginhorz="5"
    marginvert="3">
    
    <portal
      id="name"
      style="lblLeft"
      showinvalid="yes">
      <label
        ismultiline="yes"
        field="usrConfNm">
        </label>
      </portal>

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

    <portal
      id="thinglist2"
      style="menuSmall">
      <menu_things
        field="usrChosen2"
        component="none"
        candidatefield="usrCandid2"
        usepicksfield="usrSource2"
        maxvisible="10"
        sortset="explicit">
        </menu_things>
      </portal>

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

    <position><![CDATA[
      ~set up our height; our width is pre-initialized for us
      height = portal[info].height

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

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

      ~center the other portals on the tallest one
      perform portal[name].centeron[vert,info]
      perform portal[thinglist].centervert
      perform portal[thinglist2].centervert

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

      ~show our thing list menu if we have a tag expression - otherwise, show
      ~text only.
      if (tagexpr[(component.Attribute & !Helper.ChosenOpt)] <> 0) then
        portal[thinglist].visible = 0
        portal[thinglist2].visible = 0
      else
        portal[thinglist].visible = !field[usrCandid1].isempty
        portal[thinglist2].visible = !field[usrCandid2].isempty
        endif

      ~if both thing lists are showing, space them appropriately
      var total as number
      if (portal[thinglist].visible + portal[thinglist2].visible = 2) then
        total = width - portal[thinglist].left - 5
        portal[thinglist].width = total / 2
        portal[thinglist2].width = portal[thinglist].width
        portal[thinglist2].left = portal[thinglist].right + 5
        endif

      ]]></position>
    </template>

Any idea why its not showing on the chapter tab when I pick the Ultramarines chapter?
 
Ok so I've been fiddling around with this for hours now, and here's what I have:

Attribute Pick portal
Code:
  <portal
    id="chAttrPick"
    style="tblInvis"
    width="110">
    <table_dynamic
      component="Chapter"
      showtemplate="chAttrPick"
      showsortset="explicit"
      choosetemplate="chAttrPick"
      addtemplate="chAttrPick"
      descwidth="400">
      <candidate><![CDATA[
        component.Attribute & component.Trait & !component.Actor
        ]]></candidate>
      <headertitle>
        @text = "+5 to Two Attributes"
        </headertitle>
      </table_dynamic>
    </portal>

Attribute Pick template
Code:
<template
  id="chAttrPick"
  name="Attribute Picks"
  compset="UserSelect"
  marginhorz="5"
  marginvert="3">

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

  <portal
    id="AttrPick2"
    style="menuNormal">
    <menu_things
      field="usrChosen2"
      component="none"
      maxvisible="10"
      usepicksfield="usrSource2"
      candidatefield="usrCandid2">
      </menu_things>
    </portal>

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

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

    ~position our portals at the top
    portal[AttrPick1].top = 0
    portal[AttrPick2].top = 0

    ~center our portals vertically
    perform portal[AttrPick1].centervert
    perform portal[AttrPick2].centervert

    ~show our portals only if we have a tag expression
    portal[AttrPick1].visible = !field[usrCandid1].isempty
    portal[AttrPick2].visible = !field[usrCandid2].isempty

    ~if we're both showing, space us accordingly
    if (portal[AttrPick1].visible + portal[AttrPick2].visible = 2) then
      var wide as number
      wide = width - portal[AttrPick1].left - 5
      portal[AttrPick1].width = wide / 2
      portal[AttrPick2].width = portal[AttrPick1].width
      portal[AttrPick2].left = portal[AttrPick2].right + 5
      endif

    ]]></position>
  </template>

Not sure why I am getting the errors in the screenshot or how to fix it. Help please?
 

Attachments

  • Problem with Code.JPG
    Problem with Code.JPG
    225 KB · Views: 5
Could it be a component/compset mismatch? The table displays things with the Chapter component, and the Pick template has the UserSelect component. Do chapters also have the UserSelect component in their CompSet?

Also, might be unrelated to this problem, but you're using the same template for the table's showtemplate, choosetemplate, and addtemplate.

Showtemplate shows the picks that have been added to the table, and I think that is what you're going for with chAttrPick.
Addtemplate is the section at the bottom of the table which usually says "Add New Feats" or whatever. I don't think you need a template here, you can handle it with the <additem> element to just set some text
Choosetemplate is the popup which displays the choices of things you're going to add to the table, after you click whatever <additem> text
 
Aaron,

You were right, it was the choosetemplate, addtemplate. I switched it over to table fixed, eliminated the candidate expression and now its working without error messages. Now I have to figure out how to hide the portal for chapters that don't use it and I'm good. Thanks for the help.
 
New and Improved Chapter Tab, thanks to Aaron's assistance
 

Attachments

  • Deathwatch Progress May 30.JPG
    Deathwatch Progress May 30.JPG
    233 KB · Views: 9
In addition to what I worked on with Aaron's assistance, I managed to crank out the journal tab as well. Here's a progress shot on the Journal tab.
 

Attachments

  • Journal Tab progress.JPG
    Journal Tab progress.JPG
    131.6 KB · Views: 4
Mathias,

I took your advice and decided to experiment with the sheet layout.
The attached image shows what I have come up with so far.

I am not sure why, but whenever I go to print the sheet off, the Attack number doesn't print at all. It just leaves it as a blank space on the print out.

I am also trying to figure out how to get the full name to show on Weapon Skill and Ballistic Skill characteristics.
 

Attachments

  • Deathwatch Sheet Progress June 2 2013.JPG
    Deathwatch Sheet Progress June 2 2013.JPG
    49.6 KB · Views: 9
Back
Top