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.
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.
In the former two cases a custom theme is also created.
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 ]]
Trying to change the colour of DEAD in a Generations rule with 255 or 256 states, or DEADRAMP in a rule with 256 states, will change nothing, however, again, no error is produced indicating that these are invalid to customize.
A custom theme is also created when it should not be.
G255
G256
x = 2, y = 2, rule = /2/255
AB$AB!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ STARTFROM 256 COLOR DEAD Blue THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]]
Trying to change the colour of DEAD in a rule with HISTORYSTATES 0 or 1, DEADRAMP in a rule with HISTORYSTATES 0, or ALIVERAMP in a rule with AGESTATES 0, will change nothing, however, yet again, no error is produced indicating that these are invalid to customize.
Custom themes are also created as a result.
In Help > Themes, the values for DEAD, DEADRAMP and ALIVERAMP are all also still present, rather than being eliminated due to their absence in such cases.
Bizarrely, for HISTORYSTATES 1, despite DEADRAMP being used, the colour for DEAD is instead shown in Help > Info > Cells (matching any custom specifications), with DEADRAMP, the colour which is actually in use, being absent.
HISTORYSTATES 1
HISTORYSTATES 0
AGESTATES 0
x = 2, y = 4, rule = B2/S
bo$o$o$bo!
#C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]
#C [[ THEME Blues STARTFROM 5 HISTORYSTATES 1 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, and un-maximizing the popup will result in the settings menu closing. However, it may remain open for one frame before closing, showing buttons in an intersecting state.
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]