Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
Nick Wolff wrote on Fri, Jun 2, 2017 05:11 PM EDT:

Ok, so I've been on a good venture trying to figure out how to code a Rose.  With the help of Fergus, I have learned about the logride function and after lots of experimenting on format, I discovered how to do it!  I successfully did one leg (out of 16) of the Rose's pathways, but when I tried to add a second leg, the code stops functioning as if the piece had no moves at all.  I'll copy the partial code used.

def RO logride #0 #1 (ro1 ro5 ro7 ro3 ro4 ro8 ro6) or logride #0 #1 (ro1 ro2 ro6 ro8 ro4 ro3 ro7);
def ROL merge lograys #0 (ro1 ro5 ro7 ro3 ro4 ro8 ro6 stop) lograys #0 (ro1 ro2 ro6 ro8 ro4 ro3 ro7 stop);

The ro#'s are previously defined and mapped to each individual knight moves so I can use the logride command.  I believe the problem lies in the ROL function, but I can't find any mispellings, errors in the merge command, etc.  It all worked fine until I added the second logride and logray.  Any assistance would be appreciated!

Also, any suggestions on code condensing on this point?  Am I able to create a function for each leg without having a piece on the board to name the function after?

 


Edit Form
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.
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.