06-14-2022, 06:24 PM
Thanks a lot for both answers!
Now I understand, how to use 'pieceStackType'!, makes sense.
ad precomputed data: sorry that I didn't describe it more carefully, one word would have made it more clear, like: additional hidden board. (not possible, i guess.)
A cleaner way to store some precomputed data would be if I simply could put a named array in the equipment section!
I would like that feature a lot, like with region. easy and direct access.
But my tries in this direction didn't work.
And I also did some tests with calculations in a (do ..calculate.. next: moves... ) construction before a player makes the first move.
(maybe do..next isn't meant for this, i realize now.)
But it was interresting: a dice-roll in the (do.. ) was executed and shown on the board immediately, but setting a variable or make a note (even before the roll, with the new seq{}) was not done before the game.
So i found no way to compute something before the first move happens.
Now I understand, how to use 'pieceStackType'!, makes sense.
ad precomputed data: sorry that I didn't describe it more carefully, one word would have made it more clear, like: additional hidden board. (not possible, i guess.)
A cleaner way to store some precomputed data would be if I simply could put a named array in the equipment section!
I would like that feature a lot, like with region. easy and direct access.
But my tries in this direction didn't work.
And I also did some tests with calculations in a (do ..calculate.. next: moves... ) construction before a player makes the first move.
(maybe do..next isn't meant for this, i realize now.)
But it was interresting: a dice-roll in the (do.. ) was executed and shown on the board immediately, but setting a variable or make a note (even before the roll, with the new seq{}) was not done before the game.
So i found no way to compute something before the first move happens.