X-Git-Url: https://git.auder.net/?a=blobdiff_plain;f=client%2Fsrc%2Ftranslations%2Frules%2FBario%2Fen.pug;h=5c217eb1b5d21582288e667a23e04646445de2f3;hb=b376589752ce154efbd6999f39ab09bb95ab2380;hp=21203baa5e1f4ec67f253b53f9fd8b326f1f2992;hpb=0f7762c1d87e21d1c13ff0f38bd234b64b0a29d9;p=vchess.git diff --git a/client/src/translations/rules/Bario/en.pug b/client/src/translations/rules/Bario/en.pug index 21203baa..5c217eb1 100644 --- a/client/src/translations/rules/Bario/en.pug +++ b/client/src/translations/rules/Bario/en.pug @@ -1 +1,62 @@ -p.boxed TODO +p.boxed + | Your pieces remain in an undefined state until they are moved. + +p + | Bario is a chess variant invented by Panos Louridas in 1998. + a(href="https://www.bario-chess-checkers-chessphotography-spaceart.de/") + | His website + |  contains many examples and explanations. + | See also the discussion + a(href="https://www.chessvariants.com/index/listcomments.php?order=DESC&itemid=Bario") + | on chessvariants.com + | . + +figure + img.img-center(src="/variants/Bario/chessboard.png") + figcaption.text-center Undefined pieces on first ranks. + +p. + Queens, rooks, bishops and knights begin the game in a reserve below + the board, because their location isn't determined yet. + At each turn, you can either move something already defined on the board, or +ol + li move a piece from your reserve to any question mark, and then + li move the now defined piece on the board. + +p An undefined piece gives check if some specialization giving check exists. + +figure.diagram-container + .diagram + | fen:uuuuu1uk/p2p1qp1/1p6/7p/7P/5N2/PP1P1PP1/UUUKU1UU: + figcaption The white king cannot move, a rook might be on c8 or e8 + +h4 Details, special cases + +p. + At the first move, you must select a square for the king anywhere on + the first rank — preferably in a corner. This deviates from the + original intention of the author, but this way you will not need to castle + later in the game. Click on a square to place the king. + +p. + If after your move all your pieces are defined (and weren't before), then + all pieces on board revert to undefined state, unless: +ul + li. + all your pieces (board + reserve) are now of the same type, + in which case none is put back in reserve, or + li. + all opponent's pieces are of the same type, in which case + they also remain defined. + +figure.diagram-container + .diagram.diag12 + | fen:uuu1kuuu/2p5/2n5/1p1ppppp/p4PPP/3N3Q/PPPPP1BB/1RRUK3: + .diagram.diag22 + | fen:uuu1kuuu/2p5/2u5/1p1ppppp/p4PPP/3UU2U/PPPPP1UU/1UU1K3: + figcaption. + Before and after knight definition on d1 (moving to e3) + +p. + If one of your undefined pieces is captured, you first have to choose which + one was captured from the reserve: place it at the capture location.