• 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

Important note to data file authors when writing rules....

R

rob

Administrator
Staff member
I received an email from an author regarding the writing of rules, and I
used an important "trick" to figure out the problem that might not be
obvious to everyone. So I thought I would post it here for everyone to use
as a debugging aid when writing rules.

The trick is to use stats for debugging rules. :-)

Why? Well, stats can give you direct feedback about the values that are
being used within rules. For example, if I've got a rule that is based on a
particular tag expression, I can define each term of that expression as a
separate stat. Then I can see the actual numbers for each of those terms
within the stat display in CV.

Once I have the stats in place, I can add cards to the deck and what the
stats get calculated appropriately. If the stats don't look right, then you
can check the tags on cards to find out why the stats aren't tallying
correctly. Once the stats look right, then you know the basic values used
in the rules are correct. So now all you need to worry about is making sure
the logic of the rule is correct, instead of also trying to determine
whether the component elements of the rule are correct.

This technique makes it much easier to diagnose rules and get them working
in CV. I hope this proves useful to some of you authors (and would-be
authors) out there. :-)

Thanks, Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (559) 658-6995
Lone Wolf Development www.wolflair.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/WuQolB/TM
---------------------------------------------------------------------~->
 
This is great! It should be added to the authoring kit! ;-)

Rob Bowes wrote:

> I received an email from an author regarding the writing of rules, and I
> used an important "trick" to figure out the problem that might not be
> obvious to everyone. So I thought I would post it here for everyone to
> use
> as a debugging aid when writing rules.
>
> The trick is to use stats for debugging rules. :-)
>
> Why? Well, stats can give you direct feedback about the values that are
> being used within rules. For example, if I've got a rule that is based
> on a
> particular tag expression, I can define each term of that expression as a
> separate stat. Then I can see the actual numbers for each of those terms
> within the stat display in CV.
>
> Once I have the stats in place, I can add cards to the deck and what the
> stats get calculated appropriately. If the stats don't look right,
> then you
> can check the tags on cards to find out why the stats aren't tallying
> correctly. Once the stats look right, then you know the basic values used
> in the rules are correct. So now all you need to worry about is making
> sure
> the logic of the rule is correct, instead of also trying to determine
> whether the component elements of the rule are correct.
>
> This technique makes it much easier to diagnose rules and get them
> working
> in CV. I hope this proves useful to some of you authors (and would-be
> authors) out there. :-)
>
> Thanks, Rob
>
> ---------------------------------------------------------------------------
> Rob Bowes (rob@wolflair.com) (559)
> 658-6995
> Lone Wolf Development
> www.wolflair.com
>
>
> Yahoo! Groups Sponsor
> <http://rd.yahoo.com/M=259395.3614674.4902533.1261774/D=egroupweb/S=1705053078:HM/A=1524963/R=0/SIG=12o885gmo/*http://hits.411web.com/cgi-bin/autoredir?camp=556&lineid=3614674&prop=egroupweb&pos=HM>
>
>
>
> To unsubscribe from this group, send an email to:
> cardvault-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/>.



--
Jim Williamson <jim@timewarpcomics.com <mailto:jim@timewarpcomics.com>>
TimeWarp Comics & Games
(973) 857-9788
www.timewarpcomics.com <http://www.timewarpcomics.com>



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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/WuQolB/TM
---------------------------------------------------------------------~->
 
It will. But it's something I wanted to let everyone know about right away
instead of waiting for the next update (where some folks that have read the
docs already won't even see it).

-Rob

At 09:00 PM 10/13/2003 -0400, you wrote:
>This is great! It should be added to the authoring kit! ;-)
>
>Rob Bowes wrote:
>
> > I received an email from an author regarding the writing of rules, and I
> > used an important "trick" to figure out the problem that might not be
> > obvious to everyone. So I thought I would post it here for everyone to
> > use
> > as a debugging aid when writing rules.
> >
> > The trick is to use stats for debugging rules. :-)
> >
> > Why? Well, stats can give you direct feedback about the values that are
> > being used within rules. For example, if I've got a rule that is based
> > on a
> > particular tag expression, I can define each term of that expression as a
> > separate stat. Then I can see the actual numbers for each of those terms
> > within the stat display in CV.
> >
> > Once I have the stats in place, I can add cards to the deck and what the
> > stats get calculated appropriately. If the stats don't look right,
> > then you
> > can check the tags on cards to find out why the stats aren't tallying
> > correctly. Once the stats look right, then you know the basic values used
> > in the rules are correct. So now all you need to worry about is making
> > sure
> > the logic of the rule is correct, instead of also trying to determine
> > whether the component elements of the rule are correct.
> >
> > This technique makes it much easier to diagnose rules and get them
> > working
> > in CV. I hope this proves useful to some of you authors (and would-be
> > authors) out there. :-)
> >
> > Thanks, Rob


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (559) 658-6995
Lone Wolf Development www.wolflair.com


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/WuQolB/TM
---------------------------------------------------------------------~->
 
You must log in or register to reply here.
Back
Top