10-07-2021, 08:12 AM
Hi,
The problem was coming from a wrong update of the owned structure in the ActionInsert class (related to the fact that you are adding the new piece at level 0 and not to the top of the stack now). This structure is used by any (forEach Piece ...) ludeme to speed up things, but of course, if the structure is wrong the result moves are also wrong :)
Anyway, I fixed it, that will be in the next release.
Regards,
Eric
The problem was coming from a wrong update of the owned structure in the ActionInsert class (related to the fact that you are adding the new piece at level 0 and not to the top of the stack now). This structure is used by any (forEach Piece ...) ludeme to speed up things, but of course, if the structure is wrong the result moves are also wrong :)
Anyway, I fixed it, that will be in the next release.
Regards,
Eric