Comments by ChessShogi
Should be fixed now.
This preset of yours for detecting captures is huge. The fact that it reliably detects where the suicide occured means that I can use it to test whether the suicide is a King's move away from the moving Fire Demon and ensure that no suicides are done when a non-Fire Demon moves, which should solve the majority of problems with coding the burning move. If something similar could be used to detect the type of piece affected by the suicide, that should be everything I need to enforce the burning rules using suicides, at least in theory. Best of all, I can just ask players that haven't made a burn after moving a Fire Demon rather than worry about displaying legal moves on the board.
You could adapt it. For the multi-move variants, there are usually the same number of move parts each turn. So, it makes sense for these games to do the multi-part analysis globally for all pieces. But for games that include pieces with multi-part moves, you may want to reserve the multi-part analysis for specific pieces and tailor it to each piece that needs it.
This is what the original Suzumu Shogi preset (and all presets using the same general codebase) does, which is largely thanks to its isdoublemove subroutine. So, I guess I could use integers instead of booleans and sub ismultimove instead of sub isdoublemove to keep track of which part of the move suffices. The only major problem is that I'm not exactly sure how to enforce rules for the third part of a three-part move. Perhaps I am overthinking it though. Perhaps just copy-pasting and tweaking the code for the second part of multi-moves will be enough. This requires testing, but thankfully, the Taishin Shogi preset (which is fully coded, at least for enforcing the old rules) affords just such an opportunity.
Edit: I figured out how to detect the type of piece that committed the suicide. Now we should be all good.
As it turned out, I didn't need the suicides to perform the burns in Suzumu Shogi. I just needed to tweak the isdoublemove subroutine a little bit, add a FD subroutine for the Fire Demon, tweak the Fire Demon functions to include the new subroutine, and return the Fire Demon to its destination square with empty and add after it made a burning move. I love GAME code... :)
I finally have the new Fire Demon fully and correctly implemented. Now I just need to carry the changes over to the other presets that use it.
Bugfixes for all Suzumu family GC Presets: The Fire Demon's double move option now only triggers if the piece moved to an adjacent square or there are enemy pieces adjacent to its destination, making it more user friendly. I also fixed some bugs with the Queen and Reverse Chariot not being able to promote and the promoted Queen not being given the option to make a double move when it was able to.
The Edit Comment scripts aren't working properly. Whenever I try to edit a comment it fails. Posting comments still works though.
Is it just me, or is the latest version of my Taishin Shogi GC preset overloading this whole site? Whenever I click on my settings file to play it, I get nothing but 524 errors for a while.
I will admit that the thing is one of the biggest GC presets out there in terms of file size (if not the biggest) since there are so many piece types, as well as special promotion rules (i.e. contagious pieces), and all manner of multi-part moves, but I haven't had problems like this before.
Edit: I found the problem. It was a tiny syntax error in the isdoublemove subroutine. Everything works fine now.
I saw your comment after I fixed the error in the preset's code, but thank you for posting the information anyway. I'm guessing the errors above the subroutine error in the log were the main cause of the Error 524 problem, but it could be that the preset was just so big that it took too long to spot the error and print the log. After all, Taishin Shogi's GC preset is the largest GC preset with full rule enforcement and display of legal moves that I know of (in terms of board size (25x25), number of piece types (232 in total), and number of lines of code (total is probably close to or over 1000 as of right now)).
What if there was a two player version? Or I could just make one myself...
When I reverted the Futashikana Shogi pages back to their original form, they also reverted to pending editorial approval. This game has already been approved before. If an editor could fix this that would be great.
An influence display like the one in the ShogiVars program would be a really nice feature to add, especially for the really big games.
I think mobile devices are suffering from a similar misalignment problem to the one I pointed out earlier. Whenever I load a GC preset that uses an image format on a mobile device, the hitboxes are misaligned, and the image is much smaller than normal. However, whenever I clear my browser cache everything looks fine the first time I load the preset page.
The Raven in the diagram can also move from c2 to a3, but this is not shown in the diagram.
Hectochess now has a diagram with playable AI. I also made a new variant, Banner Xiangqi, which has its own playable diagram as well.
I would like the following presets deleted:
betzatest (Yangsi) - This preset was accidentally saved during a test of H. G. Muller Game Code Generator for his interactive diagrams, and is no longer needed.
default2, promotest (Suzumu Shogi) - The promotest preset was made in an attempt to resolve the server-side multi-move promotion bug, and is no longer needed. The default2 preset was made during the final phase of experimentation trying to find a good starting position for Suzumu Shogi, and is no longer needed now that the starting position is finalized.
There shouldn't be any game logs using these presets, as they redirect to the correct presets, so they should be pretty easy to delete.
The settings files themselves seem to be cleared, but the links to them are still showing.
I would like to have the abstract preset for Dragon Chess deleted.
The triple capture ability for Lion Dogs works perfectly, at least in regards to executing the moves. There seems to be a problem when highlighting destination for the third leg of a triple capture move. The possible destination squares (aside from the one travelled to via the second leg) generate in all directions where there is a piece on one such square in said direction.
Edit: Also, the moving piece isn't deselected if it can't move back to its starting square when the diagram generates the moves for the next leg. There also seems to be a problem with contageous promotions not taking effect if you make a three leg move to an empty square
I am sure I am not using the old script. Try doing the same thing in the sandbox that you did last time, but with the following moves instead: b2-b4 c2-c4 d2-d4 e12-e4 e4xd4xc4xb4. You should notice spurious highlights when asked to enter the third leg of the move. Note that the bug only works if both the first and second square in a given direction are occupied by enemy pieces.
I tried this in both Edge and Google Chrome, and it seems only the latter has the spurious highlighting. When executing the moves on Chrome with the compact description assigned, I also see a spurious highlight on e1 when entering the third leg of the move.
Maybe it only takes place when I clear my browser cache.
Edit: I tested this in Edge, and yes, it only works if you clear your browser cache.
Try clearing your browser cache (cached images and files, any browser) assigning KADGHmcavKmpafcavKcafcmpavK (the complete Lion Dog move) to the star piece in the XBetza sandbox, and making the following moves: b2-b4 c2-c4 d2-d4 f2-e3 e12-e4 e4xd4xc4xb4. You should see spurious highlights e3 and e1 (it only works if the first and second squares in a direction are occupied by enemy pieces). If you don't see spurious highlights after this, then it must be something on my end.
25 comments displayed
Permalink to the exact comments currently displayed.
Hmm. Perhaps the step-by-step approach would be better. After all, the Suzumu Shogi preset is essentially on a more restrictive form of the other multi-move presets with more pieces.
So the tentative process would then be the folowing
Do a regular move
Then I would need to assess whether or not there are pieces available to burn (which should be easy thanks to the burn subroutine in my Tenjiku Shogi preset). If so, after the move, do an igui capture or pass.
Or it may be simpler to simply always give the player to optionally shoot any enemy piece a King step away after moving.
This could potentially solve the problems of detecting a suicide move if I knew how to do it.
Since I am already writing this, would the system used for the multi-move variants be able to handle moves with three or more parts (i.e. that of the Lion Dog in Maka Dai Dai Shogi)? This will be important for my larger games with Lion Dogs, Furious Fiends, Kirin Masters, and Phoenix Masters, as well as if I use the move breakdown method for the Fire Demon's burns.