The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on 2020-11-01 UTC

I'm not sure how much better this setup is than in the case of Grotesque Chess, if at all.

In Univers Chess in case of, say, a Double-King's pawn opening analogue, the opposing Archbishops might be able to oppose/trade each other off without much advantage to either player - either that, or the other player may be able to develop a bishop to the 1st/10th rank, to bother/frustrate an Archbishop (using a reverse symmetry re-positioning of the setup would not help much either, perhaps). Also, the position of the knights on their files in the setup gives them only two squares that would usually be good to be developed to (compared to if the knights were one file closer to the centre each, as in Grotesque Chess).

That's the case in orthodox chess, too, but in case a player manages to castle on either flank during a game, it might be good sometimes to have the option of developing the knight to the third rank on the 3rd/8th file, in front of the king, with an eye on possibly helping to protect the king in a number of ways.

There just might be a repellant effect on potential players when they see the bishops adacent to the rooks (on the 2nd/9th files) in CVs like Univers or Grotesque Chess - so far either variant has been played less than 10 times on Game Courier (plus, Ladorean Chess has yet to be played). I'm not sure such a sentiment is fully justified, as the bishops need not be traded off inevitably, and the bishops can be developed alternatively to the 1st/10th files instead - however, arranging the development of a bishop just might make castling on that flank less safe due to a pawn(s) being moved where the king will reside.

https://www.chessvariants.com/large.dir/grotesque.html

https://www.chessvariants.com/large.dir/ladorean_chess.html


Edit Form

Comment on the page Univers 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.