Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Army Builder Forums > Army Builder
Register FAQ Community Today's Posts Search

Notices

Reply
 
Thread Tools Display Modes
armybuilder at yahoogroup
Guest
 
Posts: n/a

Old August 15th, 2002, 01:02 AM
------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------

There are 5 messages in this issue.

Topics in this digest:

1. Re: Skaven ratling gun
From: "tneva82" <tneva82@yahoo.com>
2. Read-only Files
From: ImhotepTheArchitect <imhotepthearchitect@yahoo.com>
3. reqd and -min
From: Mike Wood <balzemonn@yahoo.com>
4. Adjusting stat values
From: VanMan4311@aol.com
5. Re: Adjusting stat values
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>


__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 1
Date: Wed, 14 Aug 2002 06:22:01 -0000
From: "tneva82" <tneva82@yahoo.com>
Subject: Re: Skaven ratling gun

> There are no stats for the ratling gun in the AB files?

Make unit which can take ratling guns, choose weapon team and from
weapon team subselection choose either warpfire thrower or ratling
gun. Atleast my version of datafiles(downloaded somewhere in spring
so several month old) had them there.



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 2
Date: Wed, 14 Aug 2002 13:50:04 -0700 (PDT)
From: ImhotepTheArchitect <imhotepthearchitect@yahoo.com>
Subject: Read-only Files


After spending some time tracking down an elusive bug in the Warhammer 40k files, we discovered an interesting ummmm feature.

Files in the data directory that are marked read-only are not replaced when a datafile is imported, nor are files deleted that aren't replaced by the update if they are marked RO.

While this is a usefull method of protecting user's augmentation files, is the non-replacement by design? abexport will copy the read only bit, and set the imported file as such. The importer should either set all the read-only bits to 0 or overwrite the replaced files, or at the least, warn the user that the file wasn't replaced. Leaving non-replaced files that are marke read-only alone is a benefit though, as it eliminates the need for people to back up all their augmentations before an import. Maybe mention should be made of this is the documentation.

Cheers,


--
Graham H. Tracey - aka ImhotepTheArchitect
I'd rather have a full bottle in front of me than a full frontal labotomy.
40k3 AB Group: groups.yahoo.com/group/ab-40k3
40k3 AB Files: groups.yahoo.com/group/ab-files/


---------------------------------
Do You Yahoo!?
HotJobs, a Yahoo! service - Search Thousands of New Jobs

[Non-text portions of this message have been removed]



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 3
Date: Wed, 14 Aug 2002 15:23:55 -0700 (PDT)
From: Mike Wood <balzemonn@yahoo.com>
Subject: reqd and -min

I need a way of setting a unit's requirements to
1/1000 points, but only in armies of 2000 points or
greater. So, a 2000pt army could have 2 of these
units, but a 1900pt army couldn't have any.

I tried "reqd:1u@1000-min2000" but that only allows
one unit per 1000pts over 2000. I tried
"reqd:1u-min2000" along with "reqd:1u@1000" but that
didn't work either. Suggestions?

=====

Ba'alzemon
d%#n typos!

balzemonn@yahoo.com


__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com


__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 4
Date: Wed, 14 Aug 2002 21:55:49 EDT
From: VanMan4311@aol.com
Subject: Adjusting stat values

I want to have an option adjust the stat values of its grandparent. Is there
any way to do this within the program?
Thanks,
Brad VanMiddlesworth


[Non-text portions of this message have been removed]



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 5
Date: Wed, 14 Aug 2002 21:00:49 -0700
From: Colen 'Skrillboy' McAlister <demandred@skrill.org>
Subject: Re: Adjusting stat values

At 09:55 PM 8/14/2002 -0400, you wrote:
>I want to have an option adjust the stat values of its grandparent. Is there
>any way to do this within the program?

There is, but it involves craziness. I assume that by its grandparent you mean:

Unit A (needs stat adjusted)
|
|
Unit B
|
|
Unit C (with option)

You could do it by having Unit C assign unit B a type which activated an
option which changed the stat value of unit A, or that gave unit A a type
which activated an option which changed it's own stat value. It's a bit of
a guddle, as you can no doubt see.

Or I could be misinterpreting you (i.e. you want to make Unit C change the
stat of unit B), in which case just use the prnt: attribute.


--
Colen McAlister, demandred@skrill.org
http://www.incompetence-central.co.uk | http://www.skrill.org/
"It's time to toss the dice"



__________________________________________________ ______________________
__________________________________________________ ______________________



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
  #1 Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 10:51 PM.


Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.