Design *moves*.

[cdunn2001]

This is hard to use here because some cards take n as an argument, which can be up to 65535. We really need to think in terms of a series of turns as a single move. We need to design what the moves are.

[lybrown]

Yea, I was thinking the same thing.

We could divide up work by each designing sequences of turns that accomplish
useful tasks. We can write functions that return these as a list. The
function could have parameters where appropriate.

Then, whoever is writing the main game engine can make use of these
functions to build up higher level functionality.

Cheers,
Lyren

On Fri, Jun 17, 2011 at 4:38 PM, cdunn2001 <
reply@reply.github.com>wrote:

This is hard to use
here because some cards take n as an argument, which can be up to 65535.
We really need to think in terms of a series of turns as a single move. We
need to design what the moves are.

Reply to this email directly or view it on GitHub:
#1