• 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

WH40K: Duplicate entries in Option Notes of the HTML page

  • Thread starter Thread starter matti.makarainen at ztang
  • Start date Start date
M

matti.makarainen at ztang

Guest
I'm not sure if this also occurs in text version output, but some
items are shown duplicate (maybe the difference is one space or
similar).
Example can be seen at:
http://www.geocities.com/kezerk3/BloodAngels.htm

Bolt Pistol appears twice, with no visible difference (maybe an extra
space at the end?)
Power fist with two different descriptions (says pretty much the same)
Power weapon, also no visible difference.

As this is just a cosmetic issue, it's prolly not high on your
priority list =:)

Thanks for the effort put in this, I really appreciate it,

Kez.

---------------------------
Matti "Kezerk" Mäkäräinen
 
This happens to be due to the way the 40K data files are implemented and is
not a bug in Army Builder. Within the footnotes, Army Builder distinguishes
between options (e.g. Power Weapon) based on their unique id. If more than
one unit utilizes the EXACT same option, then Army Builder throws out the
duplicates. However, it is possible to have multiple DIFFERENT options that
happen to have the same displayed name. This is necessary when the same
basic option can be selected under substantially different conditions. Such
is the case within the 40K files. Since these options are distinct within
AB, there is no reliable way for AB to simply assume that they should be
treated as the same. For example, you'll note that the two Power Fist
options have different description text. Which one should AB throw out? It
can't know, so it plays it safe and includes both.

Correcting this would require a fair amount of work within the data files.
Colen would have to be the one who makes the call on this one. As you
pointed out, it's a cosmetic issue and of no substantial impact, so I would
get it's going to get low priority from Colen. Maybe he'll address it this
Summer when school is out and he has nothing better to do. :-O

<slap>

Ow! OK, I deserved that one from Colen. Just joking! :-)

Hope this explanation helps,
Rob


At 10:44 AM 4/20/01 +0000, you wrote:
>I'm not sure if this also occurs in text version output, but some
>items are shown duplicate (maybe the difference is one space or
>similar).
>Example can be seen at:
>http://www.geocities.com/kezerk3/BloodAngels.htm
>
>Bolt Pistol appears twice, with no visible difference (maybe an extra
>space at the end?)
>Power fist with two different descriptions (says pretty much the same)
>Power weapon, also no visible difference.
>
>As this is just a cosmetic issue, it's prolly not high on your
>priority list =:)
>
>Thanks for the effort put in this, I really appreciate it,
>
> Kez.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
 
> Correcting this would require a fair amount of work within the data files.

Doesnt each weapon have a unique abbreviation for it?? Why not use that
abbreviation (in an array) as a check to avoid duplication on the roster??
ie :-

Squad #1 has a missile launcher in it, so does squad #2. AB notices the
missile launcher in squad #1 and includes the info for it at the end of the
roster and the abbrviation in the array. It then checks squad #2 and notices
that the missile launcher is already present in the array and thus misses
out repeating the item description again.


Jimi

FREE 40k card scenery - http://www.crosswinds.net/~astronomican/

40k3 - http://groups.yahoo.com/group/40k3/
40k Fluff - http://groups.yahoo.com/group/40k_fluff/
Astartes - http://groups.yahoo.com/group/adeptus_astartes/
Grey Knights - http://groups.yahoo.com/group/greyknightchapter/
Imperial Guard - http://groups.yahoo.com/group/imperial-guard/
Sons Of Russ - http://groups.yahoo.com/group/sons-of-russ/
Unforgiven - http://groups.yahoo.com/group/unforgiven/
VDR - http://groups.yahoo.com/group/gw-vdr/
 
At 07:54 AM 4/21/01 +0100, you wrote:
> > Correcting this would require a fair amount of work within the data files.
>
>Doesnt each weapon have a unique abbreviation for it?? Why not use that
>abbreviation (in an array) as a check to avoid duplication on the roster??
>ie :-
>
>Squad #1 has a missile launcher in it, so does squad #2. AB notices the
>missile launcher in squad #1 and includes the info for it at the end of the
>roster and the abbrviation in the array. It then checks squad #2 and notices
>that the missile launcher is already present in the array and thus misses
>out repeating the item description again.

AB already DOES this. I think you missed my point. In the case of a Power
Fist, it can be taken by numerous different units. The conditions under
which it can/can't be taken, and the implications upon OTHER optoins by
taking it, will vary between different units. Therefore, the only way to
model this properly is to have DIFFERENT options for Power Fist that have
differing behaviors that correspond to the correct conditions. Each of
these options has the same DISPLAY name, so it appears to the user that
they are the same, while they are very different under the covers. It is
these DIFFERENT options that AB can't distinguish between.

After this explanation, please RE-READ my last post. Hopefully, it will all
be clear this time. You might also want to take a look at the marines.40k
data file. You'll find numerous options with the exact same display name,
yet each has VERY different behaviors. Each is used under different
circumstances within the data files and has a different unique id. They
just look the same to the user.

Hope this helps,
Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
 
One fine day in the middle of the night, Rob Bowes <rob@wolflair.com>
got up to write:

>This happens to be due to the way the 40K data files are implemented and is
>not a bug in Army Builder.

--8<----

> Which one should AB throw out? It
>can't know, so it plays it safe and includes both.
>
>Correcting this would require a fair amount of work within the data files.
>Colen would have to be the one who makes the call on this one. As you
>pointed out, it's a cosmetic issue and of no substantial impact, so I would
>get it's going to get low priority from Colen.

The problem is that while there's a large database of the option
footnotes in base.40k (where I keep everything to do with multiple
armies), before I started that I also put one in the Space Marine file,
in the Ork file, and in the Dark Eldar file IIRC. I haven't bothered to
ever consolidate them, because it sounds too much like hard work and
it's working fine right now :)

Except in the few bits you mention. I'll see which bits are causing the
problem and fix them if possible.

>Maybe he'll address it this
>Summer when school is out and he has nothing better to do. :-O

Nothing better to do than go back to working full-time on writing test
suites for DSP chips, you mean? :)

><slap>
>
>Ow! OK, I deserved that one from Colen. Just joking! :-)

The Evil Flying Drones have been dispatched to administer appropriate
punishment. Do not leave the house. :)

--
'Not Colin' McAlister | License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
 
You must log in or register to reply here.
Back
Top