You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
This is hard to use here because some cards take
n
as an argument, which can be up to65535
. We really need to think in terms of a series of turns as a single move. We need to design what the moves are.The text was updated successfully, but these errors were encountered: