A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@yahoogroups.com
------------------------------------------------------------------------
There are 3 messages in this issue.
Topics in this digest:
1. Using the threshold feature (Problems)
From: "mystarian1" <wraith1@ptd.net>
2. RE: Using the threshold feature (Problems)
From: Randel Clawson <Randel.Clawson@CTBT
rg>
3. Strange things going on with appended option sorting
From: Randel Clawson <Randel.Clawson@CTBTrg>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Wed, 20 Aug 2003 06:18:27 -0000
From: "mystarian1" <wraith1@ptd.net>
Subject: Using the threshold feature (Problems)
I have tried using the threshold option but it doesn't seem to be
working.
It is for battlefleet Gothic
ulmt:type=Commander-min@points=100-thresh=750
this is from the dark elder list and it also doesn't work.
ulmt:type=Prince-min@points=100-thresh=750-mode=default
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Wed, 20 Aug 2003 12:31:23 +0200
From: Randel Clawson <Randel.Clawson@CTBTrg>
Subject: RE: Using the threshold feature (Problems)
mystarian1 wrote:
> I have tried using the threshold option but it doesn't seem to be
> working.
>
> It is for battlefleet Gothic
>
> ulmt:type=Commander-min@points=100-thresh=750
>
> this is from the dark elder list and it also doesn't work.
>
> ulmt:type=Prince-min@points=100-thresh=750-mode=default
The '-thresh' modifier for the 'umlt' attribute is ~only~ checked
against the selected points size of the roster by the 'Restricted
To: ab@support.wolflair.com
checked against the points that have been spent in a roster. Also,
the -thresh modifier set above won't show a validation message if
a roster of 'Unlimited Size' is selected under 'Create New Roster'.
An example. If I selected a Dark Eldar fleet restricted to 500
points with the 'umlt' set above, I shouldn't see a validation
message. If I select a 1000-point fleet, though, I should see a
validation message until I purchase a Prince, even if I currently
have 800 points of ships in the roster.
On a related note, it will be much nicer if you replace the default
validation message, "Not enough Pts spent on units of type 'Prince'
in roster (min 100).", with something else using the '-msg'
attribute modifier with the 'ulmt' attribute above. Something like
"A Pirate Prince is required for a roster of this size." would
sound more eloquent IMO.
Finally, a little clarifcation on Dark Eldar fleets--they are lead
by Dread Archons and ~not~ by Pirate Princes like the Eldar fleet.
That's one of the more minor errors in Hugo's BFG data files, but
it ~is~ an error so be sure to change yours to read Dread Archon
instead.
HTH,
Randel
------------------
Randel's BFG Stuff
http://www.madtexan.com/BFG/index.html
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Wed, 20 Aug 2003 15:08:33 +0200
From: Randel Clawson <Randel.Clawson@CTBTrg>
Subject: Strange things going on with appended option sorting
I still haven't been able to find a solution to my problem with option sorting when the options are part of a unit added as a child via an option. Further, I'm really confused on how the option sort order is working since the following is happening:
Unit Name ## Hts Spd Trn Shd Arm Trt Ldr Cost
Corsair Squ. 1 - - - - - - 175
Corsair 1 1 1 40cm 90° Shadowfield 4+ - [50]
Corsair 2 1 1 40cm 90° Shadowfield 5+ 1 [60]
Corsair 3 1 1 35cm 90° Shadowfield 5+ 2 [65]
Cor3 Wpns 1 Cor3 Weapons 1 -
Cor3 Wpns 2 Cor3 Weapons 2 -
Cor1 Wpns 1 Cor1 Weapons 1 -
Cor1 Wpns 2 Cor1 Weapons 2 -
Cor2 Wpns 1 Cor2 Weapons 1 -
Cor2 Wpns 2 Cor2 Weapons 2 -
'Corsair Squ.' is a unit purchased from the list of 'Available Units' and 'Corsair 1' through 'Corsair 3' are added as child units via options for each 'Add Corsair 1', 'Add Corsair 2', etc. The weapons for each child unit are options with the 'apnd' and 'invs:nodisplay' attributes.
In the test data file illustrated above, the 'Add Corsair X' options are assigned in progressively 'lower' categories, with the 'weapon options' mixed in between according to which Corsair they are attached, like so:
C1 ~1st Corsair
C11 ~1st Corsair's 1st weapon
C12 ~1st Corsair's 2nd weapon
C2 ~2nd Corsair
C21 ~...
C22
C3
C31
C32
With this sorting, ~how~ are the weapon options for Corsair 3 being appended ~before~ those for Corsair 1 and 2? I'm 100% ~certain~ that 'Cor1 Wpns 1', 'Cor1 Wpns 2', 'Cor2 Wpns 1' and 'Cor2 Wpns 2' are set to higher categories like I describe above. How exactly does the sorting for appended options work?
Cheers,
Randel
------------------
Randel's BFG Stuff
http://www.madtexan.com/BFG/index.html
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@yahoogroups.com
------------------------------------------------------------------------
There are 3 messages in this issue.
Topics in this digest:
1. Using the threshold feature (Problems)
From: "mystarian1" <wraith1@ptd.net>
2. RE: Using the threshold feature (Problems)
From: Randel Clawson <Randel.Clawson@CTBT
rg>3. Strange things going on with appended option sorting
From: Randel Clawson <Randel.Clawson@CTBT
rg>________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Wed, 20 Aug 2003 06:18:27 -0000
From: "mystarian1" <wraith1@ptd.net>
Subject: Using the threshold feature (Problems)
I have tried using the threshold option but it doesn't seem to be
working.
It is for battlefleet Gothic
ulmt:type=Commander-min@points=100-thresh=750
this is from the dark elder list and it also doesn't work.
ulmt:type=Prince-min@points=100-thresh=750-mode=default
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Wed, 20 Aug 2003 12:31:23 +0200
From: Randel Clawson <Randel.Clawson@CTBT
rg>Subject: RE: Using the threshold feature (Problems)
mystarian1 wrote:
> I have tried using the threshold option but it doesn't seem to be
> working.
>
> It is for battlefleet Gothic
>
> ulmt:type=Commander-min@points=100-thresh=750
>
> this is from the dark elder list and it also doesn't work.
>
> ulmt:type=Prince-min@points=100-thresh=750-mode=default
The '-thresh' modifier for the 'umlt' attribute is ~only~ checked
against the selected points size of the roster by the 'Restricted
To: ab@support.wolflair.com
checked against the points that have been spent in a roster. Also,
the -thresh modifier set above won't show a validation message if
a roster of 'Unlimited Size' is selected under 'Create New Roster'.
An example. If I selected a Dark Eldar fleet restricted to 500
points with the 'umlt' set above, I shouldn't see a validation
message. If I select a 1000-point fleet, though, I should see a
validation message until I purchase a Prince, even if I currently
have 800 points of ships in the roster.
On a related note, it will be much nicer if you replace the default
validation message, "Not enough Pts spent on units of type 'Prince'
in roster (min 100).", with something else using the '-msg'
attribute modifier with the 'ulmt' attribute above. Something like
"A Pirate Prince is required for a roster of this size." would
sound more eloquent IMO.
Finally, a little clarifcation on Dark Eldar fleets--they are lead
by Dread Archons and ~not~ by Pirate Princes like the Eldar fleet.
That's one of the more minor errors in Hugo's BFG data files, but
it ~is~ an error so be sure to change yours to read Dread Archon
instead.
HTH,
Randel
------------------
Randel's BFG Stuff
http://www.madtexan.com/BFG/index.html
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Wed, 20 Aug 2003 15:08:33 +0200
From: Randel Clawson <Randel.Clawson@CTBT
rg>Subject: Strange things going on with appended option sorting
I still haven't been able to find a solution to my problem with option sorting when the options are part of a unit added as a child via an option. Further, I'm really confused on how the option sort order is working since the following is happening:
Unit Name ## Hts Spd Trn Shd Arm Trt Ldr Cost
Corsair Squ. 1 - - - - - - 175
Corsair 1 1 1 40cm 90° Shadowfield 4+ - [50]
Corsair 2 1 1 40cm 90° Shadowfield 5+ 1 [60]
Corsair 3 1 1 35cm 90° Shadowfield 5+ 2 [65]
Cor3 Wpns 1 Cor3 Weapons 1 -
Cor3 Wpns 2 Cor3 Weapons 2 -
Cor1 Wpns 1 Cor1 Weapons 1 -
Cor1 Wpns 2 Cor1 Weapons 2 -
Cor2 Wpns 1 Cor2 Weapons 1 -
Cor2 Wpns 2 Cor2 Weapons 2 -
'Corsair Squ.' is a unit purchased from the list of 'Available Units' and 'Corsair 1' through 'Corsair 3' are added as child units via options for each 'Add Corsair 1', 'Add Corsair 2', etc. The weapons for each child unit are options with the 'apnd' and 'invs:nodisplay' attributes.
In the test data file illustrated above, the 'Add Corsair X' options are assigned in progressively 'lower' categories, with the 'weapon options' mixed in between according to which Corsair they are attached, like so:
C1 ~1st Corsair
C11 ~1st Corsair's 1st weapon
C12 ~1st Corsair's 2nd weapon
C2 ~2nd Corsair
C21 ~...
C22
C3
C31
C32
With this sorting, ~how~ are the weapon options for Corsair 3 being appended ~before~ those for Corsair 1 and 2? I'm 100% ~certain~ that 'Cor1 Wpns 1', 'Cor1 Wpns 2', 'Cor2 Wpns 1' and 'Cor2 Wpns 2' are set to higher categories like I describe above. How exactly does the sorting for appended options work?
Cheers,
Randel
------------------
Randel's BFG Stuff
http://www.madtexan.com/BFG/index.html
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/