AB 3 Roster Oddness
 

After playing with AB3 and the new Fantasy and 40k files I've
noticed a "weird" bug that crops up on occasion. When you switch
between rosters, every now and then you get a validation error that
refers to the previously loaded roster, for example, right now, I have
a high elf roster up, and I'm getting flagged for "The army requires
at least one unit of Bulls"...and Ogre Kingdoms was the roster I had
open previously. I've also gotten marine errors for a loaded Ork file.
If I "switch game system" to the fantasy file (or 40k) right after
that, the problem goes away (for a while). Sometimes it happens right
after startup, when I just "OK" whatever army is defaulted to,
intending to load a different roster right away (since there's no load
button on the opening window...)

AB 3 Roster Oddness
 

There was a weird bug in how things were managed for rulesets that would
cause exactly this behavior. This was just fixed in the V3.0b update.

-Rob

At 03:20 AM 2/2/2005 +0000, you wrote:
>After playing with AB3 and the new Fantasy and 40k files I've
>noticed a "weird" bug that crops up on occasion. When you switch
>between rosters, every now and then you get a validation error that
>refers to the previously loaded roster, for example, right now, I have
>a high elf roster up, and I'm getting flagged for "The army requires
>at least one unit of Bulls"...and Ogre Kingdoms was the roster I had
>open previously. I've also gotten marine errors for a loaded Ork file.
> If I "switch game system" to the fantasy file (or 40k) right after
>that, the problem goes away (for a while). Sometimes it happens right
>after startup, when I just "OK" whatever army is defaulted to,
>intending to load a different roster right away (since there's no load
>button on the opening window...)


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 588-8252
Lone Wolf Development www.wolflair.com

AB 3 Roster Oddness
 

This is something I can reproduce as well. I originally thought it was a
Tau problem in the 40k files (since that's the list I usually generate),
but after seeing this I tried it on a couple others. I've run across it
with space marines too.

I put the error up on the 40k files maintainer site but the response I got was
that they couldn't duplicate the problem. So like I said, since this same
problem crops up across two armies of the 40k system, and appears to be
relevant to fantasy also, it strikes me that it might be an engine issue?
Here's my details:

AB v3.0a - #75 (3.0a jan 22 download update)

With (so far) Tau and Space Marines, if you put in 2 HQ units, you will get an
error saying 'Must take a parent race HQ unit'.

Comes up as a list validation error.

<EOL>
Tib

On Wed, 2 Feb 2005, taskmage1 wrote:

>
>
>
> After playing with AB3 and the new Fantasy and 40k files I've
> noticed a "weird" bug that crops up on occasion. When you switch
> between rosters, every now and then you get a validation error that
> refers to the previously loaded roster, for example, right now, I have
> a high elf roster up, and I'm getting flagged for "The army requires
> at least one unit of Bulls"...and Ogre Kingdoms was the roster I had
> open previously. I've also gotten marine errors for a loaded Ork file.
> If I "switch game system" to the fantasy file (or 40k) right after
> that, the problem goes away (for a while). Sometimes it happens right
> after startup, when I just "OK" whatever army is defaulted to,
> intending to load a different roster right away (since there's no load
> button on the opening window...)
>
>
>
>
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

AB 3 Roster Oddness
 

AFAIK it's to do with the rulesets applied and the rule not having a
ruleset attached to it. The latest version of the 40K datafile
should remedy that

--- In armybuilder@yahoogroups.com, Tib <tib@t...> wrote:
>
>
> This is something I can reproduce as well. I originally thought it
was a
> Tau problem in the 40k files (since that's the list I usually
generate),
> but after seeing this I tried it on a couple others. I've run
across it
> with space marines too.
>
> I put the error up on the 40k files maintainer site but the
response I got was
> that they couldn't duplicate the problem. So like I said, since
this same
> problem crops up across two armies of the 40k system, and appears
to be
> relevant to fantasy also, it strikes me that it might be an engine
issue?
> Here's my details:
>
> AB v3.0a - #75 (3.0a jan 22 download update)
>
> With (so far) Tau and Space Marines, if you put in 2 HQ units, you
will get an
> error saying 'Must take a parent race HQ unit'.
>
> Comes up as a list validation error.
>
> <EOL>
> Tib
>
> On Wed, 2 Feb 2005, taskmage1 wrote:
>
> >
> >
> >
> > After playing with AB3 and the new Fantasy and 40k files I've
> > noticed a "weird" bug that crops up on occasion. When you switch
> > between rosters, every now and then you get a validation error
that
> > refers to the previously loaded roster, for example, right now, I
have
> > a high elf roster up, and I'm getting flagged for "The army
requires
> > at least one unit of Bulls"...and Ogre Kingdoms was the roster I
had
> > open previously. I've also gotten marine errors for a loaded Ork
file.
> > If I "switch game system" to the fantasy file (or 40k) right after
> > that, the problem goes away (for a while). Sometimes it happens
right
> > after startup, when I just "OK" whatever army is defaulted to,
> > intending to load a different roster right away (since there's no
load
> > button on the opening window...)
> >
> >
> >
> >
> >
> >
> >
> >
> > To unsubscribe from this group, email
> >
> > armybuilder-unsubscribe@yahoogroups.com
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >