[xogo.git] / variants / Baroque / complete_rules.html

<html>
<head>
  <title>Baroque Rules</title>
  <link href="/common.css" rel="stylesheet"/>
  <link href="/variants/Baroque/style.css" rel="stylesheet"/>
</head>
<body>
<div class="full-rules">
<h1>Baroque Rules</h1>

<div>
  <h4>Pieces names</h4>
  <p>Pieces names refer to the way they capture, which is described later.</p>
  <ul>
    <li>Pawn : Pawn or Pincer</li>
    <li>Rook : Coordinator</li>
    <li>Knight : Long Leaper</li>
    <li>Bishop : Chameleon</li>
    <li>Queen : Withdrawer</li>
    <li>King : King (same behavior as in standard chess)</li>
  </ul>
  <p>
    There is also a new piece : the immobilizer,
    represented by an upside-down rook.
  </p>
  <figure>
    <div class="diag"
         data-fen='8/8/4m3/8/8/8/3M4/8 w 0'>
    </div>
    <figcaption>Immobilizers on d2 and e6.</figcaption>
  </figure>
</div>

<div>
  <h3>Non-capturing moves</h3>
  <p>
    Pawns move as orthodox rooks, and the king moves as usual,
    one square in any direction.
    All other pieces move like an orthodox queen.
  </p>
  <p>
    When a piece is adjacent to an enemy immobilizer, it cannot move unless
    the enemy immobilizer is adjacent to a friendly immobilizer or chameleon
    (cancelling the powers of the opponent's immobilizer).
  </p>
  <p>
    Note : this corresponds to the "pure rules" described on
    <a href="http://www.inference.org.uk/mackay/ultima/ultima.html">
      this page
    </a>
    , which slightly differ from the initial rules.
    The aim is to get rid of the weird suicide rule by weakening the
    immobilizers lock. In particular, in the original rules two adjacent
    immobilizer are stuck forever until one is captured. Note that it's still
    the case if all chameleons disappeared.
  </p>
</div>

<div>
  <h3>Capturing moves</h3>
  <p>
    Easy case first: the king captures as usual, by moving onto an adjacent
    square occupied by an enemy piece. But this is the only piece following
    orthodox rules, and also the only one which captures by moving onto an
    occupied square. All other pieces capture passively: they land on a free
    square and captured units are determined by some characteristics of the
    movement.
  </p>
  <p>Note: the immobilizer does not capture.</p>

  <h4>Pawns/Pincers</h4>
  <p>
    If at the end of its movement a pawn is horizontally or vertically adjacent
    to an enemy piece, which itself is next to a friendly piece (in the same
    direction), the "pinced" unit is removed from the board.
  </p>
  <figure>
    <div class="diag"
         data-fen='7k/5ppp/2N5/2n5/3rB3/8/PPP5/K7 w 0'>
    </div>
    <figcaption>1.Pc2c4 captures both coordinator and long leaper.</figcaption>
  </figure>

  <h4>Coordinators (rooks)</h4>
  <p>
    Imagine that rook and king of the same color are two corners of a rectangle
    (this works if these two pieces are unaligned).
    If at the end of a rook move an enemy piece stands in any of the two
    remaining corners, it is captured.
  </p>
  <figure>
    <div class="diag"
         data-fen='8/2b4K/2q5/3p1N1p/8/8/2R5/k7 w 0'>
    </div>
    <figcaption>1.Rc5 captures on c7 and h5.</figcaption>
  </figure>

  <h4>Long leapers (knights)</h4>
  <p>
    A knight captures exactly as a queen in international draughts game: by
    jumping over its enemies, as many times as it can/want but always in the
    same direction. In this respect it is less powerful than a draughts' queen:
    on the following diagram c8 or f6 cannot be captured.
    However, the knight does not have to maximize the number of captured units
    (as is the case in draughts).
  </p>
  <figure>
    <div class="diag"
         data-fen='2n4k/3r4/5b2/3p4/1m6/3b4/3N4/K7 w 0'
         data-mks='d4,d6,d8,a5'>
    </div>
    <figcaption>All marked squares captures are playable from d2.</figcaption>
  </figure>

  <h4>Withdrawer (queen)</h4>
  <p>
    The queen captures by moving away from an adjacent enemy piece, in the
    opposite direction (without jumping, the path must be free).
  </p>
  <figure>
    <div class="diag"
         data-fen='7k/8/8/3Qr3/8/8/8/K7 w 0'
         data-mks="a5,b5,c5">
    </div>
    <figcaption>1.Qa5, 1.Qb5 or 1.Qc5 captures the black rook.</figcaption>
  </figure>

  <h4>Chameleon (bishop)</h4>
  <p>The chameleon captures pieces in the way they would capture. So, it</p>
  <ul>
    <li>pinces pawns (if moving like a pawn),</li>
    <li>withdraws from withdrawers,</li>
    <li>leaps over long leapers,</li>
    <li>coordinates coordinators.</li>
  </ul>
  <p>...and these captures can be combined.</p>
  <p>
    Remark: the move indicated on the diagram doesn't capture the black pincer
    on e5, since it is a diagonal move (not like a pawn).
  </p>
  <figure>
    <div class="diag"
         data-fen='7k/8/8/r3pP2/2n5/8/B7/K7 w 0'
         data-mks="a5,c4">
    </div>
    <figcaption>1.Bd5 captures the two marked pieces.</figcaption>
  </figure>
  <p>
    Besides, chameleon immobilizes immobilizers (but cannot capture them since
    they do not capture).
  </p>
  <p>
    A chameleon captures the king in the same way the king captures, which
    means that a chameleon adjacent to a king gives check.
  </p>
</div>

<div>
  <h3>End of the game</h3>
  <p>
    The game ends by checkmate or stalemate as in standard chess. Note however
    that checks are more difficult to see, because of the exotic capturing
    rules. For example, on the following diagram the white king cannot move to
    e5 because then the black pawn could capture by moving next to it.
  </p>
  <figure>
    <div class="diag"
         data-fen='7k/8/8/p4r/4K3/8/8/8 w 0'
         data-mks="e5">
    </div>
    <figcaption>1.Ke5 is impossible</figcaption>
  </figure>
</div>

<div>
  <h3>More information</h3>
  <p>
    The
    <a href="https://en.wikipedia.org/wiki/Baroque_chess">Wikipedia page</a>
    is a good starting point.
  </p>
</div>

</div>

</body>
<script src="/utils/drawDiagrams.js"></script>
<script>fenToDiag("Baroque");</script>
</html>
Commit	Line	Data
	1	<html>
	2	<head>
	3	<title>Baroque Rules</title>
	4	<link href="/common.css" rel="stylesheet"/>
	5	<link href="/variants/Baroque/style.css" rel="stylesheet"/>
	6	</head>
	7	<body>
	8	<div class="full-rules">
	9	<h1>Baroque Rules</h1>
	10
	11	<div>
	12	<h4>Pieces names</h4>
	13	<p>Pieces names refer to the way they capture, which is described later.</p>
	14	<ul>
	15	<li>Pawn : Pawn or Pincer</li>
	16	<li>Rook : Coordinator</li>
	17	<li>Knight : Long Leaper</li>
	18	<li>Bishop : Chameleon</li>
	19	<li>Queen : Withdrawer</li>
	20	<li>King : King (same behavior as in standard chess)</li>
	21	</ul>
	22	<p>
	23	There is also a new piece : the immobilizer,
	24	represented by an upside-down rook.
	25	</p>
	26	<figure>
	27	<div class="diag"
	28	data-fen='8/8/4m3/8/8/8/3M4/8 w 0'>
	29	</div>
	30	<figcaption>Immobilizers on d2 and e6.</figcaption>
	31	</figure>
	32	</div>
	33
	34	<div>
	35	<h3>Non-capturing moves</h3>
	36	<p>
	37	Pawns move as orthodox rooks, and the king moves as usual,
	38	one square in any direction.
	39	All other pieces move like an orthodox queen.
	40	</p>
	41	<p>
	42	When a piece is adjacent to an enemy immobilizer, it cannot move unless
	43	the enemy immobilizer is adjacent to a friendly immobilizer or chameleon
	44	(cancelling the powers of the opponent's immobilizer).
	45	</p>
	46	<p>
	47	Note : this corresponds to the "pure rules" described on
	48	<a href="http://www.inference.org.uk/mackay/ultima/ultima.html">
	49	this page
	50	</a>
	51	, which slightly differ from the initial rules.
	52	The aim is to get rid of the weird suicide rule by weakening the
	53	immobilizers lock. In particular, in the original rules two adjacent
	54	immobilizer are stuck forever until one is captured. Note that it's still
	55	the case if all chameleons disappeared.
	56	</p>
	57	</div>
	58
	59	<div>
	60	<h3>Capturing moves</h3>
	61	<p>
	62	Easy case first: the king captures as usual, by moving onto an adjacent
	63	square occupied by an enemy piece. But this is the only piece following
	64	orthodox rules, and also the only one which captures by moving onto an
	65	occupied square. All other pieces capture passively: they land on a free
	66	square and captured units are determined by some characteristics of the
	67	movement.
	68	</p>
	69	<p>Note: the immobilizer does not capture.</p>
	70
	71	<h4>Pawns/Pincers</h4>
	72	<p>
	73	If at the end of its movement a pawn is horizontally or vertically adjacent
	74	to an enemy piece, which itself is next to a friendly piece (in the same
	75	direction), the "pinced" unit is removed from the board.
	76	</p>
	77	<figure>
	78	<div class="diag"
	79	data-fen='7k/5ppp/2N5/2n5/3rB3/8/PPP5/K7 w 0'>
	80	</div>
	81	<figcaption>1.Pc2c4 captures both coordinator and long leaper.</figcaption>
	82	</figure>
	83
	84	<h4>Coordinators (rooks)</h4>
	85	<p>
	86	Imagine that rook and king of the same color are two corners of a rectangle
	87	(this works if these two pieces are unaligned).
	88	If at the end of a rook move an enemy piece stands in any of the two
	89	remaining corners, it is captured.
	90	</p>
	91	<figure>
	92	<div class="diag"
	93	data-fen='8/2b4K/2q5/3p1N1p/8/8/2R5/k7 w 0'>
	94	</div>
	95	<figcaption>1.Rc5 captures on c7 and h5.</figcaption>
	96	</figure>
	97
	98	<h4>Long leapers (knights)</h4>
	99	<p>
	100	A knight captures exactly as a queen in international draughts game: by
	101	jumping over its enemies, as many times as it can/want but always in the
	102	same direction. In this respect it is less powerful than a draughts' queen:
	103	on the following diagram c8 or f6 cannot be captured.
	104	However, the knight does not have to maximize the number of captured units
	105	(as is the case in draughts).
	106	</p>
	107	<figure>
	108	<div class="diag"
	109	data-fen='2n4k/3r4/5b2/3p4/1m6/3b4/3N4/K7 w 0'
	110	data-mks='d4,d6,d8,a5'>
	111	</div>
	112	<figcaption>All marked squares captures are playable from d2.</figcaption>
	113	</figure>
	114
	115	<h4>Withdrawer (queen)</h4>
	116	<p>
	117	The queen captures by moving away from an adjacent enemy piece, in the
	118	opposite direction (without jumping, the path must be free).
	119	</p>
	120	<figure>
	121	<div class="diag"
	122	data-fen='7k/8/8/3Qr3/8/8/8/K7 w 0'
	123	data-mks="a5,b5,c5">
	124	</div>
	125	<figcaption>1.Qa5, 1.Qb5 or 1.Qc5 captures the black rook.</figcaption>
	126	</figure>
	127
	128	<h4>Chameleon (bishop)</h4>
	129	<p>The chameleon captures pieces in the way they would capture. So, it</p>
	130	<ul>
	131	<li>pinces pawns (if moving like a pawn),</li>
	132	<li>withdraws from withdrawers,</li>
	133	<li>leaps over long leapers,</li>
	134	<li>coordinates coordinators.</li>
	135	</ul>
	136	<p>...and these captures can be combined.</p>
	137	<p>
	138	Remark: the move indicated on the diagram doesn't capture the black pincer
	139	on e5, since it is a diagonal move (not like a pawn).
	140	</p>
	141	<figure>
	142	<div class="diag"
	143	data-fen='7k/8/8/r3pP2/2n5/8/B7/K7 w 0'
	144	data-mks="a5,c4">
	145	</div>
	146	<figcaption>1.Bd5 captures the two marked pieces.</figcaption>
	147	</figure>
	148	<p>
	149	Besides, chameleon immobilizes immobilizers (but cannot capture them since
	150	they do not capture).
	151	</p>
	152	<p>
	153	A chameleon captures the king in the same way the king captures, which
	154	means that a chameleon adjacent to a king gives check.
	155	</p>
	156	</div>
	157
	158	<div>
	159	<h3>End of the game</h3>
	160	<p>
	161	The game ends by checkmate or stalemate as in standard chess. Note however
	162	that checks are more difficult to see, because of the exotic capturing
	163	rules. For example, on the following diagram the white king cannot move to
	164	e5 because then the black pawn could capture by moving next to it.
	165	</p>
	166	<figure>
	167	<div class="diag"
	168	data-fen='7k/8/8/p4r/4K3/8/8/8 w 0'
	169	data-mks="e5">
	170	</div>
	171	<figcaption>1.Ke5 is impossible</figcaption>
	172	</figure>
	173	</div>
	174
	175	<div>
	176	<h3>More information</h3>
	177	<p>
	178	The
	179	<a href="https://en.wikipedia.org/wiki/Baroque_chess">Wikipedia page</a>
	180	is a good starting point.
	181	</p>
	182	</div>
	183
	184	</div>
	185
	186	</body>
	187	<script src="/utils/drawDiagrams.js"></script>
	188	<script>fenToDiag("Baroque");</script>
	189	</html>