Check out Chess with Different Armies, our featured variant for July, 2024.

Enter Your Reply

The Comment You're Replying To
A. M. DeWitt wrote on Sat, Feb 3 02:55 PM UTC in reply to Florin Lupusoru from Fri Feb 2 08:06 PM:

So close... However, a few things are worth mentioning. (Also, take notes for your other submission, Black Swan)

I. Kings and Dictators

Modest note:

"Crossing back into own territory will not make a King lose its "dictatorial powers"."

"Once a King becomes a Dictator it will remain a Dictator till the end of the game."

These sentences can be merged into one because they carry one sense.

Though so many paragraphs is not normal in my honest opinion, a blocks for each rule can be very useful for better finding the corresponding rule in the text, which is much more useful than correct visual looking.

Lev makes some good points here.

In particular, you could (and probably should) omit two sentences about Kings and Dictators and simply say that a King immediately promotes to Dictator when it crosses into enemy territory.

However, in doing so, you would need to make a separate image for the Dictator and ideally show it in the Pieces section, since it does not appear in the initial setup. Fortunately, the Musketeer Chess Board Painter (which you probably used when making the board image) lets you save the images in its image list. Simply save an appropriate-looking image and upload it to the page's directory, and you should be good.

It may also be helpful to mention that the second Dictator step cannot jump (per I understanding), to avoid confusion from Chu Shogi players, who may think the Dictator is equal to a royal Lion.

II. Paragraph Structure

This issue is way more prominent in Black Swan. It is okay to run sentences together sometimes. The point of a paragraph visually is to divide the text up so it doesn't look like one giant mass of text, making the text easier to read.

In this submission, this isn't a problem.

Redundant Sentences (My own observations)

One of the guidelines for approval is "Write clearly and briefly, so that you are quickly understood." Part of this is avoiding redundant sentences, especially if you could say the same thing by tweaking another sentence.

1. The same is true for the corresponding enemy Pawns.

2. The four Pawns on the third rank can still get a double move if they land on the fourth rank, the starting position of the 12 Pawns. 

The first sentence (1) is redundant, because it is generally understood that the rule applies to each player. To fix this you can replace the second sentence (2) in the Rules section the following:

"Pawns can still make a double move if they land on the starting square of another friendly Pawn."

This is simpler and doesn't depend on the rank number.

The King can also be called Emperor, without changing anything about the rules.

This sentence is unneccessary, and in fact counterproductive. In general, it is best to give pieces one distinct name and only refer to them by that name. However, in keeping with Roman terminology, you could call the King a Consul. (I am a bit of a history nerd, and recently watched Oversimplified's Punic Wars videos. Once this game is approved, I think I might favorite it.)

Edit Form

Comment on the page SPQR

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

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.