• 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

Code:
<!-- Modifications portal -->
<portal
  id="grModify"
  style="tblNormal">
  <table_dynamic
    component="Mods"
    showtemplate="SimpleItem"
    choosetemplate="SimpleItem"
    alwaysupdate="yes"
    scrollable="yes"
    addpick="ModCat"
    headerpick="default">
    <titlebar><![CDATA[
      @text = "Add Modifications"
      ]]></titlebar>
    <headertitle><![CDATA[
      @text = "Modifications"
      ]]></headertitle>
    <additem><![CDATA[
      @text = "Add New Modifications"
      ]]></additem>
    </table_dynamic>
  </portal>
 
RavenX, please read what I said about the helper pick in post #7 in the stickied thread. That question has already been answered there.
 
RavenX, please read what I said about the helper pick in post #7 in the stickied thread. That question has already been answered there.

I've read it, multiple times and its still confusing me.
Everytime I try to bootstrap the simple thing from the miscellaneous.str it says "bootstrap thing 'Simple' does not exist" when I try to bootstrap it to the entity.

I guess what I am saying is I'd like for you to elaborate more on that post because I am having a frustrating time figuring this out.
 
You need to create a helper pick and bootstrap it to your entity.

I'm suggesting that this pick use Simple as its compset.
 
ok, so what you're suggesting is a pick, like in the thing_modifications.dat file that uses Simple for its compset? That is how to create the helper?
 
Here's an example of an entity from Shadowrun:

Code:
<!-- An entity for the Possession adjustment -->
<entity
  id="adjPossess"
  form="poCustPoss">
  <bootstrap thing="PossHelper"/>
  </entity>

Here's the code for PossHelper:
Code:
<thing
  id="PossHelper"
  name="Possession Helper"
  compset="Simple">
  </thing>

Then, in the tables on that form, I set

headerpick="PossHelper"
addpick="PossHelper"
 
Question for you Mathias, I am thinking of doing this as a chooser, but some of the armor choices will have the option for power armour history. Will I have to set up a separate gizmo or form for this?
 
I wouldn't make armor a chooser - I'd just use a table.

That way, you can have your favorite suit of terminator armor and your favorite suit of power armor both there at the same time, and you can add history and modifications to each one, and not have to throw away all the customizations and records on one every time you add the other.
 
I was thinking of doing the History on the modifications menu, like you've done for shadowrun with mods & accessories. That way the armour history is part of each suit of armour.
 
Mathias, I think you mentioned this before but I wanted to ask your opinion on it, for the weapons, should I set up a separate entity similar to this one?

I think I will need something similar to the way you set up Shadowrun because of the ammunition on ranged weapons and clips. I was wondering what your thoughts are on it.
 
Without knowing the exact details, I don't know whether you'll end up needing separate entities for gear, armor, and weapons. Shadowrun does use different entities in each of those cases, but I'd recommend starting with a single entity that covers all of the gear categories you have, and then splitting it into compset specific entities if you find you need to.
 
Mathias,

If I am using just one entity, can I restrict which mods show up? I have a series of ModCat tags already created. I am wondering if there is a way to only have armour show the mods that have the ModCat.Armor tag on them.
 
Back
Top