You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Support switching symmetries partway through via the `symmetries:` directive. (When parsing, this results in all transitions being expanded to the 'lowest'
105
115
symmetry type specified overall.)
106
116
117
+
## Non-table-related changes
118
+
- The `@COLORS` segment in a ruelfile allows multiple states with the same color to be defined as such
119
+
on the same line as each other, and for colors to be written as either base-10 `R G B` values or as
120
+
hexadecimal color codes. `1 10: FFF`, for instance, says to assign the color `#FFFFFF` to states 1 and
121
+
10, and can also be written as `1 10: FFFFFF` or `1 10: 255 255 255` (or as two separate lines, although
122
+
the colon is still mandatory). Comments in this segment start with `#` and go until the end of their line.
123
+
- The `@ICONS` segment uses an ad-hoc RLE syntax instead of Gollyesque XPM data. See [this post](http://conwaylife.com/forums/viewtopic.php?f=7&t=3361&p=59944#p59944)
124
+
for an explanation + example.
125
+
-**All segments are optional**. The parser will also transcribe unidentified segments as is, meaning that
126
+
a file can have a `@TABLE` segment (under which the normal Golly ruletable language is used) rather than
127
+
`@TABEL` and it will not be modified by the parser.
128
+
- Specially-treated ruel segments whose names are not respellings, like `@ICONS` and `@COLORS`, will still be
129
+
ignored by the parser if their header is immediately followed by the comment `#golly`, either on the same line (after whitespace) or on the line immediately below.
107
130
108
131
## To do
109
132
- DOCS! Or at least a proper introductory writeup.
0 commit comments