05-17-2021, 11:50 AM
Ok, I will look forward to trying it out.
However, I also tried with using ands and selects, and also had the heap problem, and I tried instead to define the board as 3D in 8 layers (or even less) (in order insert pieces to store states associated to locations) but just defining the 3d board gave a similar heap problem, so I thought it might be intrinsic to the game.
To try to avoid heap space, I also tried using stacks of neutral pieces to record the movable positions, but found that the add move couldn't seem to be used as a separate consequence at a different level within the same chain of consequences. Which I guess makes sense.
However, I also tried with using ands and selects, and also had the heap problem, and I tried instead to define the board as 3D in 8 layers (or even less) (in order insert pieces to store states associated to locations) but just defining the 3d board gave a similar heap problem, so I thought it might be intrinsic to the game.
To try to avoid heap space, I also tried using stacks of neutral pieces to record the movable positions, but found that the add move couldn't seem to be used as a separate consequence at a different level within the same chain of consequences. Which I guess makes sense.