Chess

An example game of chess:

---
GameType: International Chess
...
{"The Immortal Game: Adolf Anderssen - Lionel Kieseritzky, 1851"}
1. e2-e4 1... e7-e5 2. f2-f4 2... e5:f4
3. f1-c4 3... d8-h4 4. e1-f1 4... b7-b5
5. c4:b5 5... g8-f6 6. g1-f3 6... h4-h6
7. d2-d3 7... f6-h5 8. f3-h4 8... h6-g5
9. h4-f5 9... c7-c6 10. g2-g4 10... h5-f6
11. h1-g1 11... c6:b5 12. h2-h4 12... g5-g6
13. h4-h5 13... g6-g5 14. d1-f3 14... f6-g8
15. c1:f4 15... g5-f6 16. b1-c3 16... f8-c5
17. c3-d5 17... f6:b2 18. f4-d6 18... c5:g1
19. e4-e5 19... b2:a1 20. f1-e2 20... b8-a6
21. f5:g7  21... e8-d8 22. f3-f6 22... g8:f6
23. d6-e7 {checkmate!}

Checkers

An example game of checkers:

---
GameType: American Checkers
...
1. e3-d4 1... d6-e5 2. d2-e3 2... h6-g5
3. g3-h4 3... e7-d6 4. f2-g3 4... b6-a5
5. g3-f4 5... e5-g3;*f4 6. h2-f4;f4-h6;*g3*g5 6.... c7-b6
7. c1-d2 7... f6-e5 8. d4-f6;*e5 8... g7-e5;*f6
9. e3-d4 9... e5-f4 10. d4-e5 10... d6-c5
11. c3-b4 11... c5-d4 12. d2-e3 12... f4-d2;*e3
13. e1-c3;*d2 13... d4-e3 14. c3-d4 14... e3-d2
15. b4-c5 15... d2-e1;Mv@e1 16. b2-c3 16... 2e1-d2
17. a3-b4 17... 2d2-e3 18. a1-b2 18... d8-c7
19. b2-a3 19... f8-e7 20. c5-d6 20... e7-c5;*d6
21. b4-d6;*c5 21... 2e3-c5;2c5-e7;*d4*d6 22. g1-f2 22... 2e7-d6
23. e5-f6 23... b6-c5 24. f2-e3 24... a7-b6
25. h4-g5 25... 2d6-e5 26. f6-e7 26... b8-a7
27. e7-d8;A@d8 27... c5-d4  28. e3-c5;*d4 28... b6-d4;d4-b2;*c3*c5
29. 2d8-b6;*c7 29... a7-c5;*2b6 30. g5-f6 30... 2e5-g7;*f6
31. h6-f8;*2g7 C@f8 31... b2-c1;Sv@c1 32. 2f8-e7 32... a5-b4
33. 2e7-d6 33... b4-c3 34. 2d6-b4;2b4-d2;*c3*c5 34.... 2c1-e3;*2d2
35. a3-b4 35... 2e3-d4 36. b4-a5 36... 2d4-c5
37. a5-b6 37... 2c5-a7;*b6

Desfases

An example game of Desfases:

---
GameType:
    Name: Desfases
    Seed: 42
...
1S. ?S{n,a,2,3,5}@>90; a1-a4; ?Sd~3
1M. ?M{n,a,2,4,5}@>90; e3-c1; ?Md~2
1C. ?C{n,2,3,4,5}@>90; e2-e4; ?Cd~n
1A. ?A{n,a,2,4,5}@>90; b5-e5; ?Ad~2
2S. ?S{a,2,4}@>90; a4-b3; ?Sd~2
2M. ?M{0..4}@>90; c1-b2; ?Md~a
2C. ?C{0..5}@>90; &?dC[2]-c3; ?Cnc{~b,_%?Cd}
2A. ?A{0..4}@>90; e5-d4; ?Ad~a
3S. ?S{n,a,3,4,5}@>90; b3-a2; ?Sd~a
3M. ?M{0..4}@>90; b2-a3; ?Md~n
3C. ?C{1..5}@>90; &?dC[2]-e5; ?C4c{~b,_%?Cd} ?Cd~4
3A. ?A{a,2,3,5}@>90; d4-d2; ?Ad~n
4S. ?S{n,a,2,4,5}@>90; a2-b2; ?Sd~n
4M. ?M{0..4}@>90; &?dM[2]-b3; ?M2c{~b,_%?Md} ?Md~2
4C. ?C{0..5}@>90; e4-a4; ?Cd~3
4A. ?A{n,2,3}@>90; &?dA[2]-d3; ?Aac{~b,_%?Ad} ?Ad~a
5S. ?S{n,a,4}@>90; &?dS[2]-a2; ?Snc{~b,_%?Sd} ?Sd~n
5M. ?M{n,a,2,3,5}@>90; a3-a1; ?Md~a
5C. ?C{0..4}@>90; a4-b3; ?dC~2
5A. ?A{n,2,3,4}@>90; d2-e2; ?dA~n
6S. ?S{n,a,5}@>90; &?dS[2]-c2; ?S2c{~b,_%?Sd} ?Sd~2
6M. ?M{n,a,2,3,5}@>90; a1-a3; ?Md~n
6C. ?C{n,2,4}@>90; b3-a4; ?Cd~a
6A. ?A{0..3}@>90; &?dA[2]-e3; ?A2c{~b,_%?Ad} ?Ad~2
{ 15 more rounds to complete a full game... }

Four Field Kono

An example game of Four Field Kono:

GameType: Four Field Kono

1. b1:b3 1... d3:b3 2. c1:c3 2... a3:c3 3. c2-c1 3... b4:b2 4. a1-b1 4... b3:b1
5. d1:b1 5... c3-c2 6. a2-a3 6... b2:d2 7. a3-b3 7... c4-c3 8. c1-d1 8... d4-d3
9. b1-b2 9... d2:b2 10. b3-a3 10... b2-b1 {Player 1's loss is assured with the
 separation of their two remaining pieces and they should resign in a real game}
11. a3-a2 11... b1-c1 12. d1-d2 12... c1-d1 13. a2-a3 13... a4-b4
14. a3-a4 14... b4-c4 15. a4-b4 15... c4-d4 16. b4-a4 16... d4:d2 {Player 2 wins}

Fuji-san

A game of Fuji-san with a specific starting coin setup:

---
GameType:
  Name: Fujisan
  Coins: "44452n24n3aa/a25335325ann"
...
1. a1-b1 2. n2-k2 3. b1-e1 4. e1-j1 5. j1-j2 6. j2-l2 7. k2-m2 8. m2-m1
9. l2-l1 10. n1-k1 11. m1-i1 12. i1-d1 13. d1-d2 14. l1-i1 15. i1-i2 16. k1-k2
17. k2-e2 18. i2-c2 19. a2-f2 20. e2-h2 21. h2-g2 22. c2-h2 23. h2-h1 24. d2-h2
25. f2-b2 26. b2-b1 27. b1-g1

Ice Floe

A game of Ice Floe:

---
GameType: Ice Floe
...
PlacePawns. pS@e11 pM@k6 pC@f0 pA@(0,5)
RollDice. dS5@f11 dMa@k5 dC3@e0 dA2@(0,6)
PlacePyramids. xn{S@h7,M@d5,C@j1,A@b1}; xa{S@d3,M@f3,C@j9,A@f9};
               x2{S@b5,M@b9,C@h1,A@j3}; x3{S@h5,M@d9,C@d7,A@f1};
               x4{S@h9,M@b3,C@d1,A@b7}; x5{S@h3,M@j7,C@f7,A@j5};
Round1. ?xS4-3L; ?xM3-f10; *4?Ca; ?xC2-g3; ?xAn-d4;-h4; *4?C2;
        ?d{S~5,M~n,C~n,A~a} . c5A@g11 c4A@k4 c3A@d0 cnS@(0,7) . *2?An . *?M2
Round2. ?xMn-3L;-2U; ?xC3-b8; *4?S4; ?xA3-3R; ?xSa-3L;
        ?d{S~5,M~a,C~n,A~a} . 2@g0; 2@d11; a@h0; */cf; ?c5~C ?c{4,3,n}~S . *2?Sn; *?S3
Round3. ?xC4-4R; ?xA3-3L; ?xSn-3L; ?xM2-2SE;-f8; *4?Aa;
        ?d{S~5,M~4,C~5,A~5} . ?c{5,3,n}~M ?c4~C . *2?M5 . *?S5
Round4. ?xA3-2UL;-b4;*4?A2; ?xS2-4U; 2?Ma-2U; ?xC4-i3;
        ?d{S~3,M~3,C~2,A~3} . ?c{5,4}~C ?c3~A ?cn~M;
        a@(0,4); 2@k3; 2@(0,3); a@{k2,d11} . */cf; *3?C3; *?M4
{ Final coins: Suns: none; Moons: none; Crowns: none; Arms: none }
{ Final score: Suns: 3, Moons: 2, Crowns: 3, Arms: 0 }

Japan

An example game of Japan:

---
  GameType:
    Name: Japan
    Seed: 42
...
1R. R`6-3'<@(10.5,3)
1B. B`4-4'<@(2.5,5)
2R. R`1-5'@(12,4.5)
2B. B`6-4'@(4,6.5)
3R. R`5-2'<@(7.5,2)
3B. Ada@(7,1); (8,1)-(15,3)
4R. R`0-1'@(13,2.5)
4B. (7,1)-(14,3); ?Ad~5; (14,2)-(15,2)
5R. Sp@(12,2); (12,3)-(0,4)
5B. B`2-6'<@(1.5,6)
6R. Sda@(1,4); (1,5)-(0,5)
6B. Ap@(2,7); (1,7)-(15,3)
7R. R`2-0'<@(12.5,7)
7B. B`2-1'@(11,7.5); (12,8)-(15,3)
8R. R`1-3'<@(13.5,6); (14,7)-(0,4)
8B. B`0-2'@(5,2.5)
9R. R`5-5'@(11,5.5); (12,6)-(0,2)
9B. B`1-5'<@(2.5,3)
10R. R`3-3'@(10,4.5); (11,4)-(0,6)
10B. B`1-1'@(3,1.5)
11R. R`6-1'@(1,2.5); *(2,2)
11B. B`5-4'<@(8.5,4)
12R. R`6-2'<@(9.5,2)
12B. B`3-1'>@(3.5,4)
13R. R`6-4'@(9,6.5)
13B. (14,3)-(10,7); (10,7)~4; (10,6)-(15,4)
14R. R`6-0'@(8,5.5); (9,5)-(0,5)
14B. (8.5,4){~v,-(14\,2.5)} B`0-0'<@(8.5,4)
15R. R`6-5'@(7,4.5)
15B. B`6-3'@(6,4.5)
16R. */Sp
16B. B`6-5'<@(6.5,6)
17R. R`6-6'<@(3.5,8)
17B. ?Ad-(3,6); ?Ad~3; (3,7)-(15,7)
18R. (3.5,8)-(7.5,8) R`0-0'>@(3.5,8)
18B. B`6-6'<@(5.5,7)
19R. R`2-4'@(12,1.5)
19B. ?Ad-(14,5); ?Ad~2
20R. ?Sd-(6,3); ?Sd~5; (6,2)-(0,3)
20B. */Ap
21R. Sp@(8,3); (7,3)-(0,6) (9,3)-(0,7)
21B. Ap@(13,4); (14,4)-(15,6) (13,5)-(0,2)
22R. */Sp
22B. */Ap
23R. Sp@(11,2); (11,1)-(0,5)
23B. Ap@(5,5); (4,5)-(15,5) (5,4)-(15,4) (5,6)-(15,7)
24R. ?Sd-(7,7); ?Sd~4; (8,7)-(0,7)
24B. ?Ad-(4,1); ?Ad~n
25R. ?Sd-(4,3); ?Sd~3; (4,2)-(0,6)

Martian Chess

An example game of Martian Chess:

---
MovetextParser: Icehouse
GameType:
  Name: Martian Chess
  Seed: 42
...
1. d3-d4 1... b6-c5
2. d4-c4 2... b7-b5
3. c5-c0 c4-c5 3... b3-b9 b5-b3
4. b3-a3 4... c3-a9 c5-c3
5. d2-d3 5... c7-d6
6. a6-a0 d3-a6 6... a3_%a9 a6-a3
7. a7-b0 a3-a7 7... b2-d9 b8-b2
8. c3-c4 8... c6-b5
9. b5-d0 b2-b5 9... b1-c9 b5-b1
10. c4-a4 10... a4_%b9 a7-a4
11. a8_%a0 a4-a8 11... d6-c7
12. b1-b3 12... a8-d5
13. d5_%d0 d1-d5 13... b3_%c9 d5-b3
14. b3-c4 14... c8_%c7
15. 2c7-b0 c4-c7 15... c2_%d9 c7-c2

Plans of Action

An example game of Plans of Action:

---
GameType:
    Name: Plans of Action
    Coins: SASASS/MMACSS/CACCAA/MCMCMM
...
(5,3)-4U; (3,3)-2L; 5(5.5,5.5)$>90!; (5,5)-4L; (2,5)-3R;-2D; (3,5)-2D;
({2..7},3)-2D; (3,4)-3U; (4,5)-2U; (6,4)-3L;-4U; (6,6)-2U; (2,6)-4R; (1,5)-4R;
(7,6)-3D;-2L; (4,6)-3R; (6,6)-3D;-3L; (5,3)-3L; (7,6)-3D; (3,3)-2U; (7,3)-3L;
({3,5,6,7},5)-2D; (5,4)-4L; (1,3)-3U; (5,7)-3D; (1,4)-5R; (1,6)-2D; (7,4)-2U;
(3,6)-3R; (5,6)-2L;-2D; ({1..6},4)-2D; (4,7)-2D;-2R; (3,7)-3D;-2R; (3,8)-2D;
(6,8)-2L;-2D; (6,5)-3U;-2R;-2D; (5,4)-2U;

Relativity

An example game of Relativity:

---
Round: Night
GameType:
    Name: Relativity
    Coins: "n45a5n/3a2243/3n4a2n/a25345"
...
{ Notes: Space has power of adjacency while Time has power of sequence }
1S. d3#e3 1T. d3#d1
2S. c2#c3 2T. d2#b1;M2@e6
3S. b2#a2 3T. e3#b2
4S. f1#f4 4T. e2#a3;M3@e6
5S. c4#d4 5T. f1#a1
6S. c1#c4;M5@b6 6T. b3#a3
7S. f3#a3 7T. d1#a3
8S. f2#f3 8T. b1#d2
9S. f3#a3;Mn@b6 9T. e2#c2
10S. e1#f1 10T. f1#d4
11S. c2#c3 11T. d4#c4
12S. b2#c2 12T. c1#e2;Ma@e6

Tablut

An example game of Tablut:

---
GameType: Tablut
...
1. a4-a3 1... c5-c3 2. d1-d3 2... e7-c7
3. f1-f3;*e3 3... e4-e3;*d3 4. f9-f7 4... g5-g3;*f3
5. h5-g5 5... d5-d1 6. d9-d3 6... f5-f1;*e1
7. a3-b3;*c3 7... c7-c3;*d3 8. i4-e4;*e3 8... g3-e3;*e4
9. i5-i4 9... e5-f5 10. i6-f6 10... f5-f4
11. a5-a4 11... f4-g4 12. e2-g2 12... e3-g3
13. f6-f4 13... e6-e4;*f4 14. f7-f4 14... g4-h4
15. f4-g4;*h4

Tic-Tac-Toe

A simple game of Tic-Tac-Toe with no automatic setup:

---
Event: Example Tic-Tac-Toe Game
Result: 1-0
...
setup. t@b2
1. S@b2 1... M@a2 {? (1... M@a1)}
2. S@c1 2... M@a3
3. S@a1 3... M@c3
4. S@b1 {X wins}

Metadata

• The Metadata section should be a single “Mapping” expressed in YAML.
  • It is recommended to use the subset of YAML understood by both the 1.1 and 1.2 YAML standards since not all popular parsers understand both (or just YAML 1.2).
• It should begin with a line starting with ---
  • This is the same --- we said begins each game.
  • The --- is recommended but optional for the first game in a PPN file.
• It should end with a line starting with ...
  • This ... is recommended but optional if the Metadata section does not have any empty lines and there is at least one empty line between the Metadata and Movetext sections.
  • If there are no lines starting with ... and no empty lines the Metadata section should be assumed to be empty.
• All Metadata keys are optional.
  • If the Metadata section is empty PPN parsers should use the default Movetext parser described in a later section to interpret the Movetext (without doing any initial game piece setup).
  • One can specify the Movetext parser to use (possibly a diferent one for each game) via the MovetextParser key with a string indicating the parser to use. Movetext parsers are passed both the Metadata section and the Movetext section.

Movetext

• Regardless of the Movetext parser to be used the Movetext should not have any lines starting with --- or ...
• Should be (initially) parsed as UTF-8 text without restrictions on line length.
• Additional restrictions based on which Movetext parser is used to parse it. The default Movetext parser and its additional restrictions are described in the Default Movetext Parser section.

Setup

• Currently the Movetext Parser uses the SetUp field in the Metadata to provide game setup, if that field is missing it will use the GameType field to provide game setup. This value should either be a string with the game’s name or a mapping with the field Name with the game’s name and optionally System of the game system to use (for games that can be played with multiple game systems); all other values of this mapping will be passed to the setup.

  • Although in general tags will treated case sensitive in this case we first process the string by converting to lower case, removing apostrophes and hyphens, “squishing” the whitespace, and converting spaces to underscores e.g. “Nine Men’s Morris” will be treated as equivalent to “nine_mens_morris”. Occasionally we will provide aliases e.g. “Baroque chess” will be treated as an alias for “Ultima”.

  • GameType example of just string of game’s name for setup:

    GameType: Four Field Kono
    

  • GameType example that allows passing more info to setup:

    GameType:
      Name: Fujisan
      Seed: 11
    

  • SetUp and GameType can be used together when a game variant shares its physical setup with another game. GameType records the game being played while SetUp specifies the piece arrangement to use:

    GameType: Suicide Chess
    SetUp: Chess
    

  • A SetUp of None will explicitly do an initial board setup with no pieces at all, useful for games you will set up manually in the movetext:

    GameType: Tic-Tac-Toe
    SetUp: None
    ...
    setup. t@b2
    

• If there is neither a SetUp field nor a GameType field then this will also result in an initial board setup with no pieces at all.

Parser options

• The following built-in parsers are available via the MovetextParser field. They are all built on top of the default parser but differ in their default game system for Setup and their default configuration for colored bits (●):

  • piecepack — the standard piecepack parser; this is the default parser used when no MovetextParser is specified (also accessible as default for backwards compatibility)
  • alquerque — for alquerque-style games; colored bits use an alquerque configuration
  • checker — for checker/draughts games; colored bits use a checkers configuration
  • chess — for chess games; colored bits use a chess configuration
  • domino — for domino games
  • go — for go games; colored bits use a go configuration
  • marble — for marble games; colored bits use a marbles configuration
  • morris — for Morris games (e.g. Nine Men’s Morris); colored bits use a morris configuration
  • tarot — for card games; since French tarot is a superset of the traditional 52-card deck this parser works for both tarot and regular playing card games

• Optional arguments can be passed to the parser via the MovetextParser mapping form e.g.:

  MovetextParser:
    Name: piecepack
    ScalingFactor: 2
  

  • ScalingFactor changes how many “inches” a coordinate unit represents i.e. with ScalingFactor: 2 then a1 corresponds to an x-coordinate of 2 inches and a y-coordinate of 2 inches. Accepted by all parsers.

  • CellWidth sets the width of each board cell in inches. Valid values are 1 or 2 (default 2). Accepted by the checker and chess parsers e.g.:

    MovetextParser:
      Name: checker
      CellWidth: 1
    

Macros

The default Movetext Parse performs macro substitution in the Movetext.

• Macros are strings surrounded by a ` and ' e.g. `q'@b2 {The default "q" macro is for a black chess queen}.
• Macros can be defined in three places (with any identically named macros earlier in this list replacing those later in the list):
  1. In a “Macros” field in the Metadata
  2. By a specified game setup function
  3. The parser includes some builtin macros.
• Macro names cannot include whitespace nor the semi-colon ;.
• Macro substitution happens after “moves” and “comments” are identified (and split).

Comments

• Comments are any text between braces { and }
  • All whitespace will be parsed as single spaces, in particular comments can span multiple lines
  • Braces are not allowed within comment braces
  • Must have white space before the { and after the } (otherwise will be considered to be a brace expansion)

MoveNumbers

• Ordinary MoveNumbers are one or more letters, numbers, periods, and/or underscores followed by at least one period
  • Unlike in PGN MoveNumbers must end in (at least one) period.
  • Ordinary MoveNumbers must have white space before and after.
  • One must not have any line start with ... (which could interfere in determining where the Metadata ends).
• A single period . (surrounded by white space) is a special shortcut for writing the previous MoveNumber with an extra period added to the end of it e.g. 2. a4-b4 . b4-c4 is equivalent to 2. a4-b4 2.. b4-c4
• The semi-colon ; is a special shortcut for writing the minimal a single period MoveNumber (adding some spaces around it if necessary) e.g. 2. a4-b4;b4-c4 is equivalent to 2. a4-b4 . b4-c4 which is equivalent to 2. a4-b4 2.. b4-c4 [1].
• Putting MoveNumbers in one’s Movetext is optional but if they exist PPN parsers will often break down and label moves by MoveNumbers (to make animations of a game or visualize the game state at a particular point in the game).

Moves

• Moves are comprised of PieceSpec, Location, PieceId, and MoveToken.

• One can use Unix-shell-style brace expansions as a shortcut for expressing multiple moves e.g.:

  t@{b,d}{2..8..2} {Shortcut for t@b2 t@b4 t@b6 t@b8 t@d2 t@d4 t@d6 t@d8}
  *{b..f}2 {Shortcut for *b2 *c2 *d2 *e2 *f2}
  

  • Unlike Bash-style brace expansions must have a “preamble” or “postscript” otherwise will be interpreted as a comment (but the preamble or postscript can be another brace expansion)

PieceSpec

• The default Movetext parser supports specifying pieces by their Piece, Side, Suit, Rank, Angle, and (game system) Configuration.
• Any attribute specifications beginning with a comma , must go after the other attribute specifications, otherwise it does not matter which order the piece attributes are specified. However the following ordering may improve readability (omitting any unnecessary elements as necessary):
  1. Piece
  2. Side
  3. Suit
  4. Rank
  5. Angle
  6. Configuration
• When necessary the default Movetext will make Assumptions about unspecified elements.

Location

• The default Movetext parser supports locations by Cartesian coordinates, chess-algebraic-style coordinates, or by preceding a PieceId with an &.

Examples:

• (2.5,3.5)
• (3,2)
• c2

PieceId

A PieceId is used to identify specific pieces on the board. Currently PPN supports the following types of PieceId:

• A Location is used to identify the top piece at that Location
• N Location is used to identify the top N pieces at that Location
  • An example would be 2b4-b3*2a2 {Move top two pieces at b4 to b3 and remove top two pieces at a2}
  • If there are less than N pieces at that exact Location it will identify the N nearest pieces to the Location (according to 2D Euclidean distance)
• Location[Slice] is used to identify a “slice” of pieces at that Location
  • Pieces at a location are indexed starting with 1 with pieces “later” in the internal ordering (i.e. “above”) having a lower index
  • An example would be b4[1]_%b3[2] {Move the top piece at b4 directly under the secord piece at b3}
  • Another example would be b4[3:6]-b3 {Move the third, fourth, fifth, and sixth pieces (from the top) at b4 to b3}
  • Another example would be *(2,4)[1,3,5] {Remove the first, third, and fifth pieces (from the top) located at (2,4)}
• ?PieceSpec is used to identify a single piece with a “non-greedy” search based on their PieceSpec
  • First, the PieceSpec is parsed and only the explicitly listed features are searched against. If there is a unique match it is identified e.g. ?dS identifies the “Suns” dice in a game with a single piecepack.
  • Second, if no match the PieceSpec is parsed and all assumptions listed in PieceSpec are made including angle, if there are any matches the one last in the internal play order is returned.
  • Third, if no match the PieceSpec is parsed and all assumptions listed in PieceSpec are made except angle, if there are any matches the one last in the internal play order is returned e.g. ?S5 identifies the “5 of Suns” tile in a game with a single piecepack.
• /PieceSpec is used to identify piece(s) with a “greedy” search based on their PieceSpec
  • The PieceSpec is parsed and only the explicitly listed features are searched against e.g. /M identifies all the “Moons” pieces, /cf identifies all the coins face up, etc.
• A PieceId preceded by a ^ identifies the piece from the game state at the beginning of the move
  • An example would be a1-a2 a2-a3 {equivalent to a1-a3} versus a1-a2 ^a2-a3 {equivalent to a2-a3 a1-a2}.
• An empty PieceId corresponds to the last “active” piece(s).
  • An example would be ?Sp-a4;-a5;* {equivalent to ?Sp-a4 . ?Sp-a5 . *?Sp}
  • Note if this refers to multiple pieces then the Location of these pieces is then that of the “active” piece last in the internal ordering of pieces. However if these pieces were originally specified by the N Location PieceId formulation then the Location originally corresponded to Location but now does not.

MoveToken

The default movetext parser supports the following MoveTokens:

Default Macros

The default movetext parser has the following built-in macros (these can be over-ridden by the Setup function or by the user in the Metadata):

Extending the PPN R parser

If one would like to help develop the prototype R parser here are some notes.