11-18-2020, 08:28 AM
That can be weird yes but in reality not really. Because when you put the parameter to stack:false, you did not remove the piece at (to) position, so in that sense if you see the model of the state as a stack for each site, that's pretty logical. The "stack:false" just mean that ludeme does not activate the state to be a stack model, but the other one does.
But which is weird is for a game state for flat game (non stack) when the piece of the (to) is removed even if that's not specified, but that is forced by the model of the state for non stack games in which the "what" data of a site can correspond to only one piece.
That's maybe a bit technical but that's forced by the models ;)
Regards,
Eric
But which is weird is for a game state for flat game (non stack) when the piece of the (to) is removed even if that's not specified, but that is forced by the model of the state for non stack games in which the "what" data of a site can correspond to only one piece.
That's maybe a bit technical but that's forced by the models ;)
Regards,
Eric