Setting up paste commands that cancel out to produce nothing will have differing results in the range-1 algorithm versus the general-range algorithm.
At T=0, in the range-1 algorithm, a dead cell is visible in the thumbnail, but is not present in the popup viewer; in the general-range algorithm, it is present in both cases. In both cases, dead cells will manifest from T=1 onwards.
The dead cells in the general-range algorithm, besides the first two, will never fade.
Attempting to customize the colour of GRIDMAJOR in a hexagonal or triangular rule, or a square grid rule with a GRIDMAJOR interval of 0, will not display an error.
This is unlike when trying to color cell states which do not apply to the active rule, as well as bounded grid edge cells in rules which do not specify a bounded grid; both cases produce an error to indicate that the customization is irrelevant.
Hexagonal
Triangular
GRIDMAJOR 0
x = 2, y = 2, rule = B/S0123HT
o$2o!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ COLOR GRIDMAJOR Blue THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
Changing the color of "dead" in [R]Super or [R]Investigator will not change the color of any cell states. However, it also will not display an error indicating that "dead" is not a valid element to customize for these specific rules.
In [R]Standard and [R]History, "dead" will affect the colors of freshly-dead cells.
Attempting to customize the capitalized "DEAD" in [R]Super or [R]Investigator will display an error.
[R]Standard
[R]History
x = 3, y = 2, rule = B2a3r/S
obo$o!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ STARTFROM 8 COLOR dead Green THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
Different errors will be produced when trying to customize the colors of history, mark1, markoff, mark2 and kill in a rulespace which does not support these states if they are specified as lowercase compared to uppercase.
Lowercase
Uppercase
x = 4, y = 4, rule = B3/S23
2bo$obo$bobo$bo!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ COLOR history Pink COLOR mark1 Pink COLOR markoff Pink COLOR mark2 Pink COLOR kill Pink THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
If a pattern that uses HISTORYFIT has its evolution modified by PASTE or Kill Gliders in a certain way, AUTOFIT will ignore all preceding history cells when calculating the box to fit the pattern to.
User interfaces interact incorrectly with specific values for popup width and height as defined in script commands.
On some touchscreen devices, the popup created by the right thumbnail is twice the size it should be.[2]
If a viewer window has a height of below 480, the Settings button will be disabled as the contents of that menu would not display in a usable way. Maximizing the popup on the right will enable that button, allowing it to be entered, but un-maximizing the popup will result in the settings menu remaining on-screen, with all buttons and sliders intersecting in an unusable fashion (which is why the button was disabled in the first place). Expected results here would be for the settings menu to be closed when the popup is restored to its original size.
A height of below 480 also modifies the Help menu: instead of all buttons being stacked vertically, they are spread out horizontally as well. Maximizing the viewer in this screen will keep them in the height-below-480 layout, despite the height now being sufficient to accommodate the traditional view.
If some commands are provided with a value exceeding 2147483647, they will overflow, rather than rejecting the value as it is provided. This does not apply to all commands.
These values are presumably those which are handled as Uint32Arrays.[3]