[i]posted by Muumi[/i] This 3-fold addition can be a bit complicated. But there was one formal error here: all the pieces do not have to be on the same squares, i.e. e.g. two rooks of the same color can swap places, as can e.g. knights. a) The move must have the same player, b) NB! All possible moves must be the same (e.g. the right to castling, if it was there before, must still be there; passing capture also), c) Pieces of the same type must be on the same squares (as mentioned, rooks can swap places). But this should not cause problems in programming. So capturing [because the same piece can only be obtained by pawn conversion, but then the number of pawns is not the same], pawn move, castling should reset the counter. The 50-move rule then applies to one side, i.e. white or black need to make 50 moves [quite a lot]. It shouldn't be limited to 30, because e.g. rook spear against rook is a well-known position that comes up from time to time and takes a lot of time to realize. At the same time, some fool might start to maliciously stretch the pawn against the pawn... The 50-move rule is reset by a pawn move or some kind of capture. By the way, shouldn't the system look for it automatically? Maybe we could add a button where the user can check whether it was or wasn't? But in that case, it should be limited somehow so that the user doesn't click it too much. [But this is such a random thought, I don't know if it would be reasonable. In real life, you have to determine it yourself, the position is not automatically considered a draw.] Notes: K-king, R-knight, O-spear, L-flag, V-rook 2R versus K is not a draw, the argument that it is not checkmated in real life is absurd. Then many positions could be evaluated that way. Certain draws are: a) only kings on the board [hereinafter I will only mention what can be added] b) O or R c) same-suited O versus same-suited O Now some positions that concern timeout for the stronger side [i.e. the positions are not draws, but the weaker side cannot win]: a) R versus L cannot win, b) O versus L cannot win, c) O versus V cannot win I am afraid that it is not possible to program a "dead position" in general, where, for example, pawns are blocked and kings cannot get through and there are no other pieces [then you probably have to rely on the 50 move rule v 3-fold repetition v the opponent's reasonableness that the draw will still be accepted], here is added, for example, a spear stuck behind your pawns, etc. FIDE judge and chairman of the EML jury
The ending is WRONG! A pawn against a spear or a knight wins! A pawn against a rook wins! A draw is when the same position occurs 3 times during the game! (I guess that's also correct) If no pieces are captured and no pawns are moved within 30 moves(!) the position is automatically a draw! Just like in chess tournaments when the same position is repeated 3 times, players can demand a draw, but they don't have to(!) I propose this cover: If the position is repeated 3 times, a piece would appear somewhere on the edge. Name: Demand a draw! Identifying a draw in chess
Read by 166 users
peterarthur please read the previous writer's answer carefully before you accuse the FIDE judge and the chairman of the EML jury of providing false information. He writes that you cannot win against a flag with a spear or a knight, not that a player with a flag cannot win. It is about when it exceeds the time of the player with the flag.
I think that a draw can also be considered a split-suit endgame with spears without two pawns if I stand still and the pawns are blocked.
Today I posted an update - maybe we made it better.
Let me know if you still have problems in any state!
Let me know if you still have problems in any state!