Thanks for the Diagram on this one. I was thinking about equipping the in-hand soldiers with all kinds of distant leaps from 9th rank, or situating those on extra 5th-rank squares left and right with an s(mpoa)mR move. But restricting mU with a morph is much simpler. Declaring the in-hand soldiers iron to remove the need for a gap between those and the board is also a trick I had not thought of.
P.S. It did need promoZone=2 for the white promotions to work. And it revealed a bug in the script, as the General was considered royal despite the fact that it was not mentioned in the royal=K. I suppose the problem is that a royal parameter menitioning the pieces by ID rather than number can only be processed after all piece definitions have been read, while with a number they set the royalness variables immediately. So defaulting the last-defined piece to royal in none is yet defined appears to happen too early.
@HaruN Y
Thanks for the Diagram on this one. I was thinking about equipping the in-hand soldiers with all kinds of distant leaps from 9th rank, or situating those on extra 5th-rank squares left and right with an s(mpoa)mR move. But restricting mU with a morph is much simpler. Declaring the in-hand soldiers iron to remove the need for a gap between those and the board is also a trick I had not thought of.
P.S. It did need promoZone=2 for the white promotions to work. And it revealed a bug in the script, as the General was considered royal despite the fact that it was not mentioned in the royal=K. I suppose the problem is that a royal parameter menitioning the pieces by ID rather than number can only be processed after all piece definitions have been read, while with a number they set the royalness variables immediately. So defaulting the last-defined piece to royal in none is yet defined appears to happen too early.