• 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

alright I'll look at the need tag element. I thought about doing the candidate expression for the table, but I'd have to set up multiple tables for that to work wouldn't I?
 
No, a candidate field wouldn't require multiple components - a script on your gear component would look up all the ModCatAllw tags on it, and generate an expression from that list of tags.
 
That's right, I can generate the candidate expression for the Mods via a script.
I need to add a set of ModCatAllw tags, but I should be able to get this working with a script.
 
Mathias, I am having difficulty getting the "Customize" button to appear...

I added the addbehavior="customize" line to the armor component, but its not showing up in testing. Did I misread the gizmo info?
 
In your table, the component="" must be the same as the component with addbehavior="customize".

However, in order to get all the purchase mechanics, it also has to be the same as the component with isgear="yes".

So basically, add addbehavior="customize" to the gear component, and set every table that adds any type of gear (weapons, armor, etc.) to use that component.
 
Mathias said:
No, a candidate field wouldn't require multiple components - a script on your gear component would look up all the ModCatAllw tags on it, and generate an expression from that list of tags.
Click to expand...

Just so I know for sure, I am building the script on the Gear component instead of the modification component? And that script will build the candidate expression I need for showing the correct mods?
 
In order to use it as the candidatefield="" of a table on the gizmo's form, it needs to be a field on the helper pick you've added to the gizmo. You also need to set candidatepick="" to the pick where the candidatefield="" can be found.

That may require you to create a new component for the gizmo helper - no longer using Simple for those.
 
So I need to add a field to hold the candidate field to the helper pick? And I may have to create a new compset to handle this?

This is the helper I created for the mods.
Code: 
  <thing
    id="ModHelper"
    name="Modification Helper"
    compset="Simple">
    </thing>
 
RavenX said:
So I need to add a field to hold the candidate field to the helper pick? And I may have to create a new compset to handle this?

This is the helper I created for the mods.
Code: 
  <thing
    id="ModHelper"
    name="Modification Helper"
    compset="Simple">
    </thing>
Click to expand...

Correct.
 
I see, A new compset that incorporates the Custom component will allow me to access the candidate expression fields. So what I need to do is create a similar compset to Simple but add in the Custom component.
 
That depends on what you need this compset to do. If you don't need any other components in your compset, then leaving out autocompset="no" will save you the typing of formally defining the compset as well as the component. If you do find that you need other components in this compset, then you can't use autocompset="no".
 
So now that I have the field created created in the component, I need to set candidatefield="" to that field?
 
Now its giving me an error message:

Portal 'grModify' - Candidate field 'AllowMods' must be a text field

I set the field's type to user

Code: 
  <!-- ModHelp component
        This component helps with the derivation of ModCatAllw expressions
  -->
  <component
    id="ModHelp"
    name="ModHelp">

    <field
      id="AllowMods"
      name="Modification Category Allowed"
      type="user">
      </field>
    </component>

so why is it giving me this error?
 
You must log in or register to reply here.
Back
Top