K
kschafer1 at kc.rr.com
Guest
Well, I thought I had this licked but it's reared its ugly head
again.
Raw Deal background: Decks are built around a WWE Superstar and may
contain any number of non-superstar specific cards, but may only
contain their own superstar specific cards. The Rock cannot use a
Steve Austin card, for example.
Right now Superstar specific cards have a tag from the group reqss.
Superstar cards have a tag from the group isSS.
I have tried to steal the Will Only Join rule from the L5R files.
So I first identify the type of deck being played with a series of
rules along this line:
<rule id="Is3Min" message="Error: Cannot set Is3Min" priority="1"
scope="deck2">
<![CDATA[
eval Is3Min as { test { card:isSS.3Min > 0, 1, 0}}
]]>
</rule>
Then check the cards with this rule:
scope="card"
!reqss.? | (reqss.3Min & ( @Is3Min > 0))
This works fine except that there are over 70 superstar cards so the
rule over flows and won't parse.
So I broke the rule into 26 pieces and did one rule for each letter
of the alphabet. This would work fine except that some cards have
more than one superstar and so it activates more than one rule so I
get false negatives.
The only solution I can think of right now is to do seperate entries
for the different superstars and indentical them together, but that
seems like to much of a kludge. Any thoughts?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cardvault/
<*> To unsubscribe from this group, send an email to:
cardvault-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
again.
Raw Deal background: Decks are built around a WWE Superstar and may
contain any number of non-superstar specific cards, but may only
contain their own superstar specific cards. The Rock cannot use a
Steve Austin card, for example.
Right now Superstar specific cards have a tag from the group reqss.
Superstar cards have a tag from the group isSS.
I have tried to steal the Will Only Join rule from the L5R files.
So I first identify the type of deck being played with a series of
rules along this line:
<rule id="Is3Min" message="Error: Cannot set Is3Min" priority="1"
scope="deck2">
<![CDATA[
eval Is3Min as { test { card:isSS.3Min > 0, 1, 0}}
]]>
</rule>
Then check the cards with this rule:
scope="card"
!reqss.? | (reqss.3Min & ( @Is3Min > 0))
This works fine except that there are over 70 superstar cards so the
rule over flows and won't parse.
So I broke the rule into 26 pieces and did one rule for each letter
of the alphabet. This would work fine except that some cards have
more than one superstar and so it activates more than one rule so I
get false negatives.
The only solution I can think of right now is to do seperate entries
for the different superstars and indentical them together, but that
seems like to much of a kludge. Any thoughts?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cardvault/
<*> To unsubscribe from this group, send an email to:
cardvault-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/