Create your own terminology

[confocaloid]

Pseudo-phoenix: Every cell in the rotor dies after 1 generation.

Examples:every p2, tubber, and hustler (there are probably more)

Oscillators without any survival events in the rotor:

What is the highest period with a known oscillator without any survival events in the rotor? In other words, if an alive cell survives to the next phase then it must belong to the stator.
I found only few known p3 and p4 examples (edit 6: added more examples, including a p6). Are there higher-period examples?

Code: Select all

x = 115, y = 69, rule = B3/S23
60bobo$44b2o13bob2o14bobo$44b2o11b3o11b2o2b3ob3o2b2o6b2o$obobo10bo40bo
4b2o8bo2bo7bo2bo7bo$15b3o24b4o10bo2b2o2bob2o5bobo2b3o2bobo8bob2o$4bo
13bo10b2o8bobo4bo8b2obo4bobo5b2obo3bo3bob2o4b2obob2o$17bo3b2o6bo3b2o4b
2obo3bo7bo3bo3bo3bo8b2o3b2o8b2ob2o$obobo12bo4bo11bo7bo3bob2o5bobo4bob
2o11b3o13bo$18b4o5b7o8bo4bobo4b2obo2b2o2bo10b2o3b2o8b2obo$4bo22bo15b4o
11b2o4bo6b2obo3bo3bob2o4b2obo2bo$20b2o8b2o29b3o8bobo2b3o2bobo8bob2o$ob
obo15b2o8b2o11b2o13b2obo9bo2bo7bo2bo7bo$43b2o13bobo10b2o2b3ob3o2b2o6b
2o$77bobo10$o3bo11b2o5bo2b2o5b2o19b2o17b2o8bo3b2o10b2o9b2o$16bo5bobo2b
o5bobo14b2o3bo18bo7bobo2bo12bo5b2obo2bo$o3bo13bo3bob2o9bo2b2o9bo2bo2bo
b2o10bo2bo8bo2bo3bo8b3o3bobobobo2bo$17b2o2b2o11b2obo2bo9b2obobo2bo8b3o
2b2o6bo4b3o2b2o4bobo4bo4b2o2bobo$obobo18b3o11bo2bo12b2obo9bo7bo6b2o5b
2obo4bobo4bo3b2o4b2o$15b3o2b2obo2bo11b2ob2obo9b2ob4o4bo2b2ob2o2bo7bo2b
obo8b3o7b2o$4bo10bo2bob2o4bo8b2ob2obob2o6b2ob2obo2bo5b2o2b2ob2o8bobobo
b2o10b4o6bo$16bob2o2b2o2bob2o6bo15bo14bo2bo2bo6b2obo2b2o3bo5b2o2b2o5bo
2bo$4bo12bo2bo3b2o2bo7bo3bo11bobo12bobobobo6bobob2o4bo6bobo5bobobo2bo$
18b2o2b3o3bo6b2obobo10b2obobo11b2ob2o11bobo2bo15bo$22bo2b3o6bo2b2ob3o
7bo2b2ob3o24bo2bobo9bo2bobo2bo4bobo$18b3obo11b2o7bo6b2o7bo23b2o2bo11bo
2bo5b2o2b2o$17bo3bob3o16b2o14b2o39bo6b4o$17b2o2bo3bo76b2o7b3o$19bobo
47b2o25b2o4b2o3bo4bobo$19b2o44b2obo2bo24bobo2b2o4bo4bobo$65bo3bo2bo25b
o2bobobobo3b3o$66b3o4bo24bo2bob2o5bo$68bob2obo25b2o9b2o$70b2ob2o$obobo
17b2o46bo2bo$22bo46bobobo$o22bo3b2o38b3ob2o$22b2o2bobo37bo$obobo10b2o
4bo2b3o2b2o35b2o$15bobo2bob2o3b2o2bo$o3bo12bo2bobo2b2o2b2o2b2o$15bobo
2b3o2bobo3b2o2bo$obobo10b2o4b2o2b2o2b2o2b2o2b2o$20bo3b3o2bobo3b2o2bo7b
o19b2ob2o2b2o$19bob2obo3bobo2b2o2b2o2b2o3bobo18b2obo2bo2bo$19bo2bo2b2o
2b2o2bobo3b2o2bo2bobo21bob2obo2b2o$20bo2b2o2b2o3bobo2b2o2b2o2b2o2b2o
16b2o2bo3b3o2bo4b2o$21b2o2b2o2b2o2b2o2bobo3b2o2b2o2bo14bo2b2o2b2o3b2ob
o2bobo$23bobo2bo2b2o3bobo2b2o2b2o2bo2bo12bo2bo2b2o2b2o2bobo2bo$23bobo
3b2o2b2o2b2o2bobo3bob2obo12bob2obo3bobo2b3o2bobo$24bo7bo2b2o3bobo2b3o
3bo14bo3b3o2b2o2b2o4b2o$33b2o2b2o2b2o2b2o2b2o4b2o4b2o4b2o2b2o2b3o3bo$
36bo2b2o3bobo2b3o2bobo4bobo2b3o2bobo3bob2obo$37b2o2b2o2b2o2bobo2bo8bo
2bobo2b2o2b2o2bo2bo$40bo2b2o3b2obo2bobo4bobo2bob2o3b2o2b2o2bo$41b2o2b
3o2bo4b2o4b2o4bo2b3o3bo2b2o$43bobo2b2o18b2o2bob2obo$43b2o3bo22bo2bo2bo
b2o$49bo22b2o2b2ob2o$48b2o!
#C [[ THEME Generations ]]

Edit: the following oscillators are "nearest failed examples" I found, which have relatively few survival events in the rotor:

• xp3_o80j9abgz23034s0t552zy21 has one survival event in the rotor (over one cycle)
• xp5_w3p64koz31255kia952zy0121 (technician) has eight survival events in the rotor
• xp6_0c88baa4ozc9j0u1aap56zw124311 has six survival events in the rotor
• xp7_0g88b5oz1255kk3033zy011 (burloaferimeter) has nine survival events in the rotor
• xp8_gg0gba9jz11078987066zx3213 (Hertz oscillator) has six survival events in the rotor
• xp8_oo0u130v1oozx347074 has eight survival events in the rotor
• xp9_064kjaabgz32hu0i8fg7czx47011 has twenty survival events in the rotor

Edit 4: here is a known p6 oscillator, which does not have survival events in the rotor:

Code: Select all

x = 30, y = 20, rule = B3/S23
21b2o$22bo$16b2o3bo$9bo6bobo2b2o$8bobo3b2o2b3o2bo4b2o$8bobo2bo2b2o3b2o
bo2bobo$6b2o2b2o2b2o2b2o2bobo2bo$5bo2b2o2b2o3bobo2b3o2bobo$4bo2bo2b2o
2b2o2b2o2b2o4b2o$4bob2obo3bobo2b3o3bo$5bo3b3o2bobo3bob2obo$2o4b2o2b2o
2b2o2b2o2bo2bo$obo2b3o2bobo3b2o2b2o2bo$2bo2bobo2b2o2b2o2b2o2b2o$obo2bo
b2o3b2o2bo2bobo$2o4bo2b3o2b2o3bobo$7b2o2bobo6bo$8bo3b2o$7bo$7b2o!
#C [[ THEME Generations ]]

Further relaxed, to require only that there must be at least one phase without any old cells in the rotor: viewtopic.php?p=177549#p177549

[tommyaweosme]

5m,4m ravenship
5m,3m robinship
5m,2m storkship
6m,5m alpacaship
7m,6m galaxyship
7m,5m sunship
7m,4m planetship
7m,3m cloudship
7m,2m skyship
7m,m rainbowship
23m,5m waterbear
23m,4m firebear
23m,3m airbear
23m,2m earthbear
23m,1m bearship

(i know this isnt fairy chess but i found opportunities and filled them in)

[Anivec]

Universal construction based replicators can be divided in to two classes, each with their own sub classes. The two classes of replicators are "tape based replicators" and "channel construction replicators". The sub classes for "tape based replicators" are "stable tape replicators" (e.g. William R. Buckley's replicators, NP-replicator, anything that has a static tape), and "moving tape replicators" (e.g. JVN loop replicator, rct (although I don't think the rct counts). The subclass for "channel construction replicators" are "single channel construction replicators" (e.g DOGun SaGaQR, 0E0P metacell(?)) and "multiple channel construction replicators" (e.g. Linear propagator). Additionally, replicators can be linear, super-linear, or quadratic.

Building off of this idea, the term "single channel construction replicators" can be shortened to "serial replicators" and "multiple channel construction replicators" can be shortened to "parallel replicators". Both of these are named after data transmission methods. Similarly, the term "tape based replicators" can be referred to "static replicators" but calling "moving tape replicators" "dynamic replicators" doesn’t make as much sense.

[tommyaweosme]

following the recent condition-transition war, i will now make new terminology away from those gross words:

stuff - the stuff in neighborhood
way - what happens because of stuff

hensel table has stuff

"stuff rules" and "way rules" dont make sense. its just "rule".

there is bways and sways. there is no bstuff and sstuff.

there are no ways on the hensel table.

[confocaloid]

[...] new terminology away from [...]

I think that's misunderstanding of the topic. It's not really about "this word vs. that word". Instead, the topic is about the underlying concepts, and about intuitively clear/suggestive ways to refer to those specific underlying concepts.

What each word/phrase suggests intuitively to an "interested but not invested" wiki reader?

It seems helpful to use the word 'condition' to refer to a condition on the current states of some cells. To specify a condition, one needs to tell some information about states of cells in the current generation.
"The cell is currently alive and has at least four alive neighbours" is a condition.
"The cell is currently dead" is a condition.
"The cell currently has no alive neighbours" is a condition.

It seems helpful to use the word 'transition' to refer to a state-to-state transition, when some state-X cell transitions into a state-Y cell.
"The cell is born", "the cell survives", "the cell remains dead", "the cell dies" are examples for two-state CA.

It seems helpful to use the phrase 'transition rule' to refer to a rule that dictates a certain condition under which a certain transition will happen.
An example of a transition rule is "If the cell is currently alive and has at least four alive neighbours, then the cell will die".

(Note that neither of the above words/phrases is recently invented, and neither is invented on these forums. This terminology and these concepts existed for many years in the Life/CA community.)

Why all of the above seems helpful? Because that wording agrees with common-sense intuition, and because that wording suggests the correct overall picture of the underlying ideas and the relationships between those underlying ideas. A rule prescribes; a transition happens; a condition is checked/tested when deciding whether or not a transition will happen.

In contrast, the words 'stuff' and 'way' you propose seem too vague in comparison, and do not provide any intuitively clear picture.
For example, if I say or write something like "B3 stuff" or "B3 way", I'm pretty sure nobody will understand what I mean by that, unless and until they go and read the written definitions.

If you write "the B3 condition" (e.g. when discussing Life-like cellular automata) it's pretty clear that you mean a condition; conditions don't tell the future. In this case, the condition tells "the cell is currently dead and has exactly three alive neighbours".
If you write "the B3 transition rule" (e.g. when discussing Life-like cellular automata) it's pretty clear that you mean a transition rule. In this case, the transition rule tells "if the cell is currently dead and has exactly three alive neighbours then the cell is born in the next generation".

[Mathemagician314]

A rake that shoots spaceships in all directions: omnirake

[tommyaweosme]

that would be an omnibreeder or an omnipuffer because of all the glider collisions.

[b-engine]

that would be an omnibreeder or an omnipuffer because of all the glider collisions.

Won't, as the spaceships produced never collides, else the omnirake will break down. 2G collisions can't produce a puffer, too.
EDIT:
In response to confocaloid's opinion, I think an omnirake could be required tl shoot only 4 or 8 spaceships.

[confocaloid]

A rake that shoots spaceships in all directions: omnirake

I can imagine a "rake" that would shoot engineered spaceships with infinitely many distinct directions. Construct an oblique spaceship with direction (n, 1); move away by some fixed displacement and increment n; repeat forever. Incrementing n means that even if the output is ignored, the "rake" would never repeat twice.

edit:

One possible different definition would be:
"a rake that shoots spaceships of some types in all directions that are possible for spaceships of those types"
In that case, if all escaping spaceships are gliders from CGoL (xq4_153), then the rake must send them in four directions (NW, NE, SW, SE).
If it's a rake in LeapLife that shoots some gliders and some lepas (and possibly other spaceships), that would imply some knightship must be sent in each of 8 possible knightwise directions, and some diagonal spaceship must be sent in each of 4 diagonal directions.

Another possible definition would be
"a rake that shoots spaceships of some types, sending a spaceship of every type in all directions possible for spaceships of that type"
In that case, if it's a rake in LeapLife that shoots some xq4_153 gliders and some lepas (and possibly other spaceships), that would imply a lepa must be sent in each of 8 possible knightwise directions, and a xq4_153 glider must be sent in each of 4 diagonal directions.

[tommyaweosme]

we should redefine when a soup settles when it goes to a same state it did before (except for spaceships and stuff), so the highest lifespan on torus problem could have been solved by my answer

[confocaloid]

we should redefine when a soup settles when it goes to a same state it did before (except for spaceships and stuff), [...]

The part "and stuff" is vague, and excluding spaceships feels artificial. Why not simply wait for the first generation that can be decomposed into still lives, phases of oscillators and/or phases of spaceships that will never interact with each other?
If the initial generation (the soup) is T = 0 and the final generation (with the described property) is T = n, then the lifespan of the soup equals n ticks.

One would need some adjustments and clarifications, to be able to unambiguously define lifespans for predictable infinite growths. But the complexity of that puzzle does not rely on whether or not one requires some state to repeat twice in some sense.

[tommyaweosme]

infinite growth (breeders) doesnt settle
rakes and puffers do
so do spaceships
all once they have went through one full cycle and everything else in the life universe has

[tommyaweosme]

ok here:
blinkers have 2 lifespan
gliders have 4 lifespan
space rakes have 20 lifespan
pulsars have 3 lifespan
a pulsar next to a blinker where they dont interacts have 6 lifespan
etc. etc.
this soup

Code: Select all

r=B3/S23
b3ob5o$bobo2bob3o$2o2b2ob3o$b4o2bo2bo$bo2bobo2bo$b3o5b2o$bobo2bo3bo$o
2bob5o$4o2b4o$4bo3bobo$2o2b3ob3o!

has a lifespan of 55

[confocaloid]

ok here:
blinkers have 2 lifespan
gliders have 4 lifespan
space rakes have 20 lifespan
pulsars have 3 lifespan
a pulsar next to a blinker where they dont interacts have 6 lifespan
etc. etc. [...]

I think it's simpler to view each of those patterns as a pattern with lifespan 0. In other words, those patterns are already settled in the initial generation.

The blinker is a period-2 oscillator; the pulsar is a period-3 oscillator; a pulsar next to a blinker (where they don't interact) is a (trivial) period-6 oscillator.
The glider is a period-4 diagonal c/4 spaceship.
The space rake is a period-20 orthogonal c/2 rake emitting forward gliders.

[...] this soup

Code: Select all

r=B3/S23
b3ob5o$bobo2bob3o$2o2b2ob3o$b4o2bo2bo$bo2bobo2bo$b3o5b2o$bobo2bo3bo$o
2bob5o$4o2b4o$4bo3bobo$2o2b3ob3o!

has a lifespan of 55

You're using an unsupported pattern format that can't be easily viewed in Golly/LifeViewer. Here is what is probably the same pattern, copied from Golly and pasted unchanged:

Code: Select all

x = 11, y = 11, rule = B3/S23
b3ob5o$bobo2bob3o$2o2b2ob3o$b4o2bo2bo$bo2bobo2bo$b3o5b2o$bobo2bo3bo$o
2bob5o$4o2b4o$4bo3bobo$2o2b3ob3o!

This pattern has lifespan 53, and settles into a stationary constellation (a beehive, a block and a traffic light) without any escaping moving objects. The final pattern has period 2.

[tommyaweosme]

(i really want to win highest lifespan on tori b3/s23 by placing a really high period glider tracks with lcm)

[confocaloid]

SKROP(n): smallest known real oscillator of period n.
Context: https://conwaylife.com/w/index.php?diff ... did=149434

[confocaloid]

A kugelblitz is a stationary alien object (either a still life or an oscillator) with all of the following properties:

• (a) A kugelblitz can be formed in previously empty space, by colliding several photons of some specific type (said photon type is denoted P). All colliding photons must be of the same type P, without any other interacting objects. The photon collision must be naturally rewindable arbitrarily far back in time.
• (b) Whether or not an approaching photon of type P interacts with a (fully formed) kugelblitz, depends only on the lane on which the photon arrives, and doesn't depend on the phase of the kugelblitz. If an interaction happens, it happens regardless of the phase; if it doesn't happen, it doesn't happen in any phase.
• (c) For every two distinct parallel lanes, if a photon of type P approaching on either of the two lanes collides with the kugelblitz, then a photon of type P approaching in the same direction on any intermediate lane also necessarily collides with the kugelblitz.
• (d) A (fully formed) kugelblitz cleanly absorbs every single photon of type P that interacts with the kugelblitz at all, without suffering permanent damage.

A kugelblitz doesn't have to be indestructible. For example, it may be possible to destroy a kugelblitz by hitting it with a photon of a different type.
A kugelblitz doesn't need to cleanly absorb any other photons, spaceships or reactions, besides photons of type P arriving one at a time with enough time for the collision to settle before the next photon arrives.
A kugelblitz doesn't have to be stable to meet the requirement (b), although stability automatically guarantees (b) since there's only one phase in that case.

[tommyaweosme]

ta1 gate

its ta1 because "tommyaweosme's first"

Code: Select all

x = 10, y = 6, rule = Sticky
3.A.3A.A$4A.A.A.A$A8.A$A.3A3.2A$A8.A$3A.6A!

it acts like a normal and gate if both inputs are same
if the first input is activated and not the second, it outputs through the second
if the second input is activated and not the first, nothing happens

im sure this is useful to someone somewhere

[NimbleRogue]

Foam is a pattern has a still life core made of connected bubbles, and where most of the active regions lay on the edge of the core.
Some Examples:
viewtopic.php?f=11&t=3120&p=51764&hilit ... acs#p51764
viewtopic.php?f=11&t=3120&p=185396&hili ... ot#p185396

Code: Select all

x = 16, y = 12, rule = B2ce3ajk4ak5ajk6e78/S2ei3aejkr4eijkrw5-e6-ae78
9bo$7bo3bo$6b8o$5bob4ob3o$bob7o3b3o$2b2ob3ob2ob3o$obo3bo3b4o$2b2ob3ob
3ob2o$bob3ob4o3b2o$7b2ob2ob2o$11b3o$13bo!

One important thing is that the core of Foam must strongly tend toward stability, stabilize fast, and active regions must form and stay around the core.
Meaning patterns like these do not count:
viewtopic.php?f=11&t=1971&p=188909&hili ... ia#p188909
viewtopic.php?f=11&t=3120&p=190866&hilit=holes#p190866
viewtopic.php?f=11&t=3120&p=68349&hilit ... bia#p68349

[CARuler]

5m,4m ravenship
5m,3m robinship
5m,2m storkship
6m,5m alpacaship
7m,6m galaxyship
7m,5m sunship
7m,4m planetship
7m,3m cloudship
7m,2m skyship
7m,m rainbowship
23m,5m waterbear
23m,4m firebear
23m,3m airbear
23m,2m earthbear
23m,1m bearship

(i know this isnt fairy chess but i found opportunities and filled them in)

I also have my own:
(7,1):
Lionship
Lionwise
(8,1):
nautilusship
nautiluswise
(9,1):
elephantship
elephantwise
(10,1):
ogreship
ogrewise
(20,1):
whaleship
whalewise
(50,1):
pandoship
pandowise
(100,1):
gaintship
gaintwise
(1 000,1):
titianship
titianwise
(10 000,1):
terrestrialship
terrestrialwise
(100 000,1):
celestialship
celestialwise
(1 000 000,1):
colossalship
colossalwise
(10 000 000,1):
quasarship
quasarwise
(100 000 000,1):
galaxyship
galaxywise
(1 000 000 000,1):
cosmosship
cosmoswise
(5,2):
kiwiship
kiwiwise
(5,3):
peacockship
peacockwise
(5,4):
parrotship
parrotwise
(6,5):
eagleship
eaglewise
(7,2):
leopardship
leopardwise
(7,3):
panthership
pantherwise
(7,4):
cougarship
cougarwise
(7,5):
tigership
tigerwise
(7,6):
lynxship
lynxwise
(8,3):
squidship
squidwise
(8,5):
cuttlefishship
cuttlefishwise
(8,7):
octopusship
otcopuswise
(9,2):
rhinoship
rhinowise
(9,4):
hippoship
hippowise
(9,5):
buffaloship
buffalowise
(9,7):
waterbeastship
waterbeastwise
(9,8):
wildbeastship
wildbeastwise
(10,3):
golemship
golemwise
(10,7):
trollship
trollwise
(10,9):
goliathship
goliathwise
(23,5):
watership
waterwise
(34,7):
nameship
namewise

[confocaloid]

5m,4m ravenship
5m,3m robinship
5m,2m storkship
6m,5m alpacaship
[...]

One obvious problem with such arbitrary fancy terms is that they would be hard to remember. People would often confuse them, and either apply various terms to various speeds in a random-ish way, or else avoid using fancy terms entirely and instead write down the displacement. (With few exceptions of terms that are already widely used, e.g. knightship, camelship.)

One other possibility is to describe oblique spaceships (and possibly non-oblique spaceships, too) according to the Euclidean distance the spaceship moves over (period) ticks.
For example, a root-fifty spaceship is a spaceship that moves by the distance equal to the square root of 50.
Note that such description does not always tell the slope. (For example, a root-65 spaceship can be either (7,4)c/n or (8,1)c/n, since 7^2+4^2 = 8^2+1^2 = 65.) Nevertheless, it is a description that actually tells something about the spaceship.

Root-5 spaceships are (2,1)c/n knightships; root-10 spaceships are camelships with displacement (3,1); oblique root-50 spaceships have displacement (7,1).

Code: Select all

5 : (2, 1)
10 : (3, 1)
13 : (3, 2)
17 : (4, 1)
20 : (4, 2)
25 : (4, 3)
26 : (5, 1)
29 : (5, 2)
34 : (5, 3)
37 : (6, 1)
40 : (6, 2)
41 : (5, 4)
45 : (6, 3)
50 : (7, 1)
52 : (6, 4)
53 : (7, 2)
58 : (7, 3)
61 : (6, 5)
65 : (7, 4) (8, 1)
68 : (8, 2)
73 : (8, 3)
74 : (7, 5)
80 : (8, 4)
82 : (9, 1)
85 : (7, 6) (9, 2)
89 : (8, 5)
90 : (9, 3)
97 : (9, 4)

[erictom333]

The following 14-cell alien still life in ruels with S4z should be called a zeppelin, as it occurs in rules with S4z from the Z-hexomino, and it kind of looks like one.

Code: Select all

x = 6, y = 5, rule = B3/S234z
3bo$b5o$o4bo$5o$2bo!

Also, the following motif should be called a book, as it fits between two bookends.

Code: Select all

x = 4, y = 3, rule = B3/S23
b3o$o2bo$3o!

[pifricted]

Also, the following motif should be called a book, as it fits between two bookends.

Code: Select all

x = 4, y = 3, rule = B3/S23
b3o$o2bo$3o!

Lumps of muck or blockade

[H. H. P. M. P. Cole]

A kugelblitz is a stationary alien object (either a still life or an oscillator) with all of the following properties:
[...]

Does this count as a kugelblitz, then, if I am following the definition correctly?

Code: Select all

#C Six 2-cell photons form a p2 oscillator which then 
#C collides with photons from thirteen lanes, recovering
#C from all 26 collisions.
x = 135, y = 28, rule = KugelblitzTest
13.B$13.A6$34.AB49.AB$38.AB49.AB$42.AB49.AB$14.B31.AB49.AB$14.A35.AB49.
AB$54.AB49.AB$BA23.AB31.AB49.AB$62.AB49.AB$12.A53.AB49.AB$12.B57.AB49.
AB$74.AB49.AB$78.AB49.AB$82.AB49.AB6$13.A$13.B!

@RULE KugelblitzTest
@TABLE
n_states: 3
neighborhood: Moore
symmetries: rotate4reflect
var a = {0,1,2}
var a1 = a
var a2 = a
var a3 = a
var a4 = a
var a5 = a
var a6 = a
var a7 = a
var a8 = a
0,1,0,0,0,0,0,0,0,1
1,a1,a2,a3,a4,a5,a6,a7,a8,2
2,1,0,0,0,0,0,0,0,0
0,0,1,0,0,0,1,0,0,1
0,2,1,1,1,0,0,0,0,2
2,2,0,2,0,2,0,2,0,1
0,1,0,0,0,1,0,0,0,2
0,0,2,2,2,0,0,0,0,1
2,2,0,0,0,2,0,0,0,2
2,1,0,0,0,1,0,0,0,1
2,1,1,0,0,1,0,0,0,1
2,1,0,2,2,0,0,0,0,1
2,1,0,0,2,0,0,0,0,1
2,1,0,0,2,0,1,0,0,1
0,1,0,0,1,0,0,0,2,1
0,2,0,2,2,0,1,0,0,2
0,2,0,0,1,0,0,2,0,2
a,a1,a2,a3,a4,a5,a6,a7,a8,0
@COLORS
0 0 0 0
1 0 255 255
2 0 0 255

[confocaloid]

A kugelblitz is a stationary alien object (either a still life or an oscillator) with all of the following properties:
[...]

Does this count as a kugelblitz, then, if I am following the definition correctly?
[...]

Yes, that's a kugelblitz indeed, although your pattern doesn't quite demonstrate that, because photons are too close to each other (and some photon is deleted due to the oscillator consuming the preceding photon):

Code: Select all

x = 17, y = 11, rule = KugelblitzTest
11.AB$15.AB$.BABABAB$B7.B$A7.A$B7.B$A7.A$B7.B$A7.A$B7.B$.BABABAB!

Here is a demonstration, with construction and hitting each of two phases separated into three "rows". Due to symmetry, it suffices to consider photons arriving from one direction.

Code: Select all

x = 173, y = 112, rule = KugelblitzTest
23.B$23.A9$24.B$24.A12$BA43.AB12$22.A$22.B9$23.A$23.B31$31.AB$41.AB$
51.AB$11.BABABAB43.AB$10.B7.B52.AB$10.A7.A62.AB$10.B7.B72.AB$10.A7.A
82.AB$10.B7.B92.AB$10.A7.A102.AB$10.B7.B112.AB$11.BABABAB123.AB$151.A
B$161.AB$171.AB6$31.AB$41.AB$51.AB$11.ABABABA43.AB$10.A7.A52.AB$10.B
7.B62.AB$10.A7.A72.AB$10.B7.B82.AB$10.A7.A92.AB$10.B7.B102.AB$10.A7.A
112.AB$11.ABABABA123.AB$151.AB$161.AB$171.AB!

@RULE KugelblitzTest

Source: https://conwaylife.com/forums/viewtopic.php?p=193378#p193378

@TABLE
n_states: 3
neighborhood: Moore
symmetries: rotate4reflect
var a = {0,1,2}
var a1 = a
var a2 = a
var a3 = a
var a4 = a
var a5 = a
var a6 = a
var a7 = a
var a8 = a
0,1,0,0,0,0,0,0,0,1
1,a1,a2,a3,a4,a5,a6,a7,a8,2
2,1,0,0,0,0,0,0,0,0
0,0,1,0,0,0,1,0,0,1
0,2,1,1,1,0,0,0,0,2
2,2,0,2,0,2,0,2,0,1
0,1,0,0,0,1,0,0,0,2
0,0,2,2,2,0,0,0,0,1
2,2,0,0,0,2,0,0,0,2
2,1,0,0,0,1,0,0,0,1
2,1,1,0,0,1,0,0,0,1
2,1,0,2,2,0,0,0,0,1
2,1,0,0,2,0,0,0,0,1
2,1,0,0,2,0,1,0,0,1
0,1,0,0,1,0,0,0,2,1
0,2,0,2,2,0,1,0,0,2
0,2,0,0,1,0,0,2,0,2
a,a1,a2,a3,a4,a5,a6,a7,a8,0
@COLORS
0 0 0 0
1 0 255 255
2 0 0 255