H. G. Muller wrote on Thu, Aug 20, 2020 10:19 AM UTC:
To prevent mishaps like this (people not ticking "Do not include moves in code". I stressed this should be done in the tutorial, but failed to mention it in the instructions on the Appler page itself), I could of course make the move parser detect the condition of an empty origin and the mentioned piece already on the destination, and point out the user should still do this in the error message. And adapt the text on the Applet page. But it would be nice if it was not possible to make this mistake at all.
Can we get a GAME-code command or variable that would enable the program to 'tick' this option under program control? Presumably Game Courier uses some PHP variable as a boolean to indicate whether it should execute the input moves, and all that would be needed is allow access to that as a system variable. Then I could set that option in the Pre-Game code.
To prevent mishaps like this (people not ticking "Do not include moves in code". I stressed this should be done in the tutorial, but failed to mention it in the instructions on the Appler page itself), I could of course make the move parser detect the condition of an empty origin and the mentioned piece already on the destination, and point out the user should still do this in the error message. And adapt the text on the Applet page. But it would be nice if it was not possible to make this mistake at all.
Can we get a GAME-code command or variable that would enable the program to 'tick' this option under program control? Presumably Game Courier uses some PHP variable as a boolean to indicate whether it should execute the input moves, and all that would be needed is allow access to that as a system variable. Then I could set that option in the Pre-Game code.