The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2018-05-08 UTCGood ★★★★

How to compute piece values here?  It's pointless to bother.  Regulator move one forward or backward is determined by play on the small board of 35 squares.  Too bad no one has experimented with the Regulator band on 8x8 with 7-square streak to the side for neat 71 square Chess Variant, a first for the size.

84-square Fourriere's Jacks and Witches lessens Bishop value to Knight by the 16-square hole in the center -- more detrimental to the Bishop now worth 2.5.   Any different board size must affect piece values somewhat.  A Fischer Random Chess array NBKRRQBN should benefit Rook to relative downgrading of Knight, maybe 5.3-2.7.  But adherents to FRC have not gotten that far yet.  So the starting line-up alone affects piece-values.  Also do the Rules in and of themselves, such as obvious thing like Bishop one-time Wazir step conversion in some CVs. 

Take the simple Regulator embodiment here.  Level 6 of regulator makes Knight into Marshall, and Level 3 makes Bishop into Cardinal.  If the board were 8x8, it's not definite which in a given game benefits more, Bishop or Knight,  because there are going to be enough move- and capture-triggers to jockey the calibration up towards level 7 tactically pretty easily, and keep it there.  Over the long haul however, Bishop value is going to show relative increase, on any rectangle 35 to 100.  That is because of its compound to BN being in effect 5/7 of the time and the other to NR only 2/7 the time.

Next, there is room for subvariants, that either side can alter the calibration, let's say forward by agreed-on even number of steps across 7 and back to 1 and onward, in lieu of a move. That can include in the Regulator Band not just moving the Regulator but either of the two trigger levels the same way, as not overcomplicated move addition.


Edit Form

Comment on the page Regulator Chess page

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.