A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get A Free Psychic Reading!
Your Online Answer To Life's Important Questions.
http://us.click.yahoo.com/aM1XQD/od7FAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@yahoogroups.com
------------------------------------------------------------------------
There are 6 messages in this issue.
Topics in this digest:
1. Augments & Inheritance
From: "ChrisSuch" <csuch@adelaide.on.net>
2. "Item" question.
From: "pr0fane69" <pr0fane@sympatico.ca>
3. Re: Augments & Inheritance
From: Colen McAlister <colen@wolflair.com>
4. Re: "Item" question.
From: Colen McAlister <colen@wolflair.com>
5. Re: Item points
From: Colen McAlister <colen@wolflair.com>
6. Re: Item points
From: "Mr. Green" <mach_5@rocketmail.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 30 May 2003 03:50:28 -0000
From: "ChrisSuch" <csuch@adelaide.on.net>
Subject: Augments & Inheritance
Hiya,
I am trying to inherit the properties of an item that I have
augmented with a seperate file. The problem is that it seems to not
include the augment (in this case, I was trying to extend the notes
field).
Could someone help me out with this?
Cheers, Chris.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Fri, 30 May 2003 02:44:36 -0000
From: "pr0fane69" <pr0fane@sympatico.ca>
Subject: "Item" question.
Hmm...I don't know what happened...I sent this Q as an email but it
seems to have gone nowhere...sorry if it gets doubled.
G'day everybody.
I have what seems to me to be a simple problem, but I cannot find a
means to implement.
What I need is this - I need an Item to count as 2 Items if selected.
Sounds so simple that I don't think I need to elaborate...maybe I'm
just blind and cannot see how this can be done.
Thank you in advance for any help.
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Fri, 30 May 2003 00:10:47 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: Augments & Inheritance
At 03:50 AM 5/30/2003 +0000, you wrote:
>Hiya,
>
>I am trying to inherit the properties of an item that I have
>augmented with a seperate file. The problem is that it seems to not
>include the augment (in this case, I was trying to extend the notes
>field).
>
>Could someone help me out with this?
From the construction kit manual, page 74:
"The set of attributes inherited is solely those attributes defined
explicitly for the referenced record. If the referenced record contains
either augmentations or inheritance attributes of its own, those attributes
are ignored."
If you inherit from a record and then augment it, any augmentations are NOT
inherited by the child records. Although I believe that if you inherit
records in a record that is then inherited from, everything works fine, so
it looks like the manual is a bit innaccurate there (unless I'm misreading
it). We'll have to make sure that's fixed in the next release...
So I'm afraid this is by design. Sorry!
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Fri, 30 May 2003 00:16:21 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: "Item" question.
At 02:44 AM 5/30/2003 +0000, you wrote:
>Hmm...I don't know what happened...I sent this Q as an email but it
>seems to have gone nowhere...sorry if it gets doubled.
>
>G'day everybody.
>
>I have what seems to me to be a simple problem, but I cannot find a
>means to implement.
>
>What I need is this - I need an Item to count as 2 Items if selected.
>
>Sounds so simple that I don't think I need to elaborate...maybe I'm
>just blind and cannot see how this can be done.
You can do this one of two ways; either change the item category in the
definition file so that each item in that category takes up 2 slots or, if
this is only true for a single item, you can have the item assign a type
"x1Slot" or similar. Give all units that can take that item an option
which, if the unit has tyle "x1Slot", reduces the number of special items
allowed by 1 ("item:-1".
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Fri, 30 May 2003 00:26:08 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: Item points
At 08:23 PM 5/28/2003 -0700, you wrote:
> > Each clmt attribute will be evaluated independently - since each has its
> > own validation message, this needs to be the case, so the appropriate
> > validation messages will be displayed at all times.
>
>Fair enough, but I think it would be more useful if you were able to
>combine both statements in one attribute and OR them together.
Quite possibly, but since the problem can be solved in several other ways,
it's unlikely to take precedence over other features that may be added.
Also, if clmt were changed to act as you request (ORing multiple attributes
by default), it would break many current datafiles which rely on its
current mode of operation.
I see your point, however, and we'll do our best to improve this
functionality in future releases of Army Builder.
> > While removing the item category using tweaks will work, an alternative
> > solution would be using types. If every magic standard assigns the type
> > 'HasStd", then the weapons, armour, wards etc could all be restricted so
> > that if the type "HasStd" was present, they would be unselectable. It
> > would
> > then be impossible to select a standard and weapons (etc) at the same
> > time,
> > so the problem of the clmt attributes would not arise.
>
>This would require me to put "utyp:!HasStd" on every magic item in the
>game that is not a magic standard... I'm far too lazy for that! This way,
>I simply add the tweak to each of the magic standards and everything
>works.
Instead of using tweaks, you could also use the item attribute 'spec' to
remove the categories from the unit. If multiple item categories need to be
removed, create a new, hidden, item with an attribute for each, and then
have each standard inherit from that item.
That should do exactly the same thing as is happening now, without the
tweaks. So it's another method to consider.
> > This is exactly the
> > sort of thing types were designed to do, so I don't think that
> > implementing
> > the expanded clmt attribute is really required. Thoughts?
>
>If I were able to use augmentation to globally assign the utyp:!HasStd
>attribute to all items of specified categories and the type:HasStd to all
>magic standards I would definitely go for it. Is that possible?
I'm afraid not. Sorry
Either going with your tweaks solution or using
spec as I suggest above would seem to be the simplest solution at this point.
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Fri, 30 May 2003 00:52:39 -0700 (PDT)
From: "Mr. Green" <mach_5@rocketmail.com>
Subject: Re: Item points
> Quite possibly, but since the problem can be solved in several other
> ways,
> it's unlikely to take precedence over other features that may be added.
> Also, if clmt were changed to act as you request (ORing multiple
> attributes
> by default), it would break many current datafiles which rely on its
> current mode of operation.
>
> I see your point, however, and we'll do our best to improve this
> functionality in future releases of Army Builder.
I'm really not suggesting changing the default, I certainly don't want to
invalidate old data files. Adding functionality to include multiple clmt
statements in a single attribute is really what I'm after.
For example, instead of these (which by default get and-ed together):
clmt:stnd<=1-count
clmt:weap+armr+ench+ward<=50-points-msg=crbsb1
I'd like to do something like this (the '|' is 'OR'):
clmt
stnd<=1-count)|(weap+armr+ench+ward<=50-points)-msg=crbsb1
This allows for current datafiles to remain the same and perfectly valid,
but also added functionality to combine the statements in was other than
'AND' if need be.
> >This would require me to put "utyp:!HasStd" on every magic item in the
> >game that is not a magic standard... I'm far too lazy for that! This
> way,
> >I simply add the tweak to each of the magic standards and everything
> >works.
>
> Instead of using tweaks, you could also use the item attribute 'spec' to
> remove the categories from the unit. If multiple item categories need to
> be
> removed, create a new, hidden, item with an attribute for each, and then
> have each standard inherit from that item.
> That should do exactly the same thing as is happening now, without the
> tweaks. So it's another method to consider.
Yep, they're very similar. I'll probably just leave it as-is for now
(it's not really broken, after all...)
Thanks for your help!
Mark
=====
WF6 Army Builder File Manager
-
Warhammer Club - Vancouver, BC
http://www.WCP-Vancouver.com
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Get A Free Psychic Reading!
Your Online Answer To Life's Important Questions.
http://us.click.yahoo.com/aM1XQD/od7FAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@yahoogroups.com
------------------------------------------------------------------------
There are 6 messages in this issue.
Topics in this digest:
1. Augments & Inheritance
From: "ChrisSuch" <csuch@adelaide.on.net>
2. "Item" question.
From: "pr0fane69" <pr0fane@sympatico.ca>
3. Re: Augments & Inheritance
From: Colen McAlister <colen@wolflair.com>
4. Re: "Item" question.
From: Colen McAlister <colen@wolflair.com>
5. Re: Item points
From: Colen McAlister <colen@wolflair.com>
6. Re: Item points
From: "Mr. Green" <mach_5@rocketmail.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 30 May 2003 03:50:28 -0000
From: "ChrisSuch" <csuch@adelaide.on.net>
Subject: Augments & Inheritance
Hiya,
I am trying to inherit the properties of an item that I have
augmented with a seperate file. The problem is that it seems to not
include the augment (in this case, I was trying to extend the notes
field).
Could someone help me out with this?
Cheers, Chris.
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Fri, 30 May 2003 02:44:36 -0000
From: "pr0fane69" <pr0fane@sympatico.ca>
Subject: "Item" question.
Hmm...I don't know what happened...I sent this Q as an email but it
seems to have gone nowhere...sorry if it gets doubled.
G'day everybody.
I have what seems to me to be a simple problem, but I cannot find a
means to implement.
What I need is this - I need an Item to count as 2 Items if selected.
Sounds so simple that I don't think I need to elaborate...maybe I'm
just blind and cannot see how this can be done.
Thank you in advance for any help.
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Fri, 30 May 2003 00:10:47 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: Augments & Inheritance
At 03:50 AM 5/30/2003 +0000, you wrote:
>Hiya,
>
>I am trying to inherit the properties of an item that I have
>augmented with a seperate file. The problem is that it seems to not
>include the augment (in this case, I was trying to extend the notes
>field).
>
>Could someone help me out with this?
From the construction kit manual, page 74:
"The set of attributes inherited is solely those attributes defined
explicitly for the referenced record. If the referenced record contains
either augmentations or inheritance attributes of its own, those attributes
are ignored."
If you inherit from a record and then augment it, any augmentations are NOT
inherited by the child records. Although I believe that if you inherit
records in a record that is then inherited from, everything works fine, so
it looks like the manual is a bit innaccurate there (unless I'm misreading
it). We'll have to make sure that's fixed in the next release...
So I'm afraid this is by design. Sorry!
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Fri, 30 May 2003 00:16:21 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: "Item" question.
At 02:44 AM 5/30/2003 +0000, you wrote:
>Hmm...I don't know what happened...I sent this Q as an email but it
>seems to have gone nowhere...sorry if it gets doubled.
>
>G'day everybody.
>
>I have what seems to me to be a simple problem, but I cannot find a
>means to implement.
>
>What I need is this - I need an Item to count as 2 Items if selected.
>
>Sounds so simple that I don't think I need to elaborate...maybe I'm
>just blind and cannot see how this can be done.
You can do this one of two ways; either change the item category in the
definition file so that each item in that category takes up 2 slots or, if
this is only true for a single item, you can have the item assign a type
"x1Slot" or similar. Give all units that can take that item an option
which, if the unit has tyle "x1Slot", reduces the number of special items
allowed by 1 ("item:-1".
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Fri, 30 May 2003 00:26:08 -0700
From: Colen McAlister <colen@wolflair.com>
Subject: Re: Item points
At 08:23 PM 5/28/2003 -0700, you wrote:
> > Each clmt attribute will be evaluated independently - since each has its
> > own validation message, this needs to be the case, so the appropriate
> > validation messages will be displayed at all times.
>
>Fair enough, but I think it would be more useful if you were able to
>combine both statements in one attribute and OR them together.
Quite possibly, but since the problem can be solved in several other ways,
it's unlikely to take precedence over other features that may be added.
Also, if clmt were changed to act as you request (ORing multiple attributes
by default), it would break many current datafiles which rely on its
current mode of operation.
I see your point, however, and we'll do our best to improve this
functionality in future releases of Army Builder.
> > While removing the item category using tweaks will work, an alternative
> > solution would be using types. If every magic standard assigns the type
> > 'HasStd", then the weapons, armour, wards etc could all be restricted so
> > that if the type "HasStd" was present, they would be unselectable. It
> > would
> > then be impossible to select a standard and weapons (etc) at the same
> > time,
> > so the problem of the clmt attributes would not arise.
>
>This would require me to put "utyp:!HasStd" on every magic item in the
>game that is not a magic standard... I'm far too lazy for that! This way,
>I simply add the tweak to each of the magic standards and everything
>works.
Instead of using tweaks, you could also use the item attribute 'spec' to
remove the categories from the unit. If multiple item categories need to be
removed, create a new, hidden, item with an attribute for each, and then
have each standard inherit from that item.
That should do exactly the same thing as is happening now, without the
tweaks. So it's another method to consider.
> > This is exactly the
> > sort of thing types were designed to do, so I don't think that
> > implementing
> > the expanded clmt attribute is really required. Thoughts?
>
>If I were able to use augmentation to globally assign the utyp:!HasStd
>attribute to all items of specified categories and the type:HasStd to all
>magic standards I would definitely go for it. Is that possible?
I'm afraid not. Sorry

spec as I suggest above would seem to be the simplest solution at this point.
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Fri, 30 May 2003 00:52:39 -0700 (PDT)
From: "Mr. Green" <mach_5@rocketmail.com>
Subject: Re: Item points
> Quite possibly, but since the problem can be solved in several other
> ways,
> it's unlikely to take precedence over other features that may be added.
> Also, if clmt were changed to act as you request (ORing multiple
> attributes
> by default), it would break many current datafiles which rely on its
> current mode of operation.
>
> I see your point, however, and we'll do our best to improve this
> functionality in future releases of Army Builder.
I'm really not suggesting changing the default, I certainly don't want to
invalidate old data files. Adding functionality to include multiple clmt
statements in a single attribute is really what I'm after.
For example, instead of these (which by default get and-ed together):
clmt:stnd<=1-count
clmt:weap+armr+ench+ward<=50-points-msg=crbsb1
I'd like to do something like this (the '|' is 'OR'):
clmt

This allows for current datafiles to remain the same and perfectly valid,
but also added functionality to combine the statements in was other than
'AND' if need be.
> >This would require me to put "utyp:!HasStd" on every magic item in the
> >game that is not a magic standard... I'm far too lazy for that! This
> way,
> >I simply add the tweak to each of the magic standards and everything
> >works.
>
> Instead of using tweaks, you could also use the item attribute 'spec' to
> remove the categories from the unit. If multiple item categories need to
> be
> removed, create a new, hidden, item with an attribute for each, and then
> have each standard inherit from that item.
> That should do exactly the same thing as is happening now, without the
> tweaks. So it's another method to consider.
Yep, they're very similar. I'll probably just leave it as-is for now
(it's not really broken, after all...)
Thanks for your help!
Mark
=====
WF6 Army Builder File Manager
-
Warhammer Club - Vancouver, BC
http://www.WCP-Vancouver.com
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/