Problem with CGOL (Custom Game of Life)
-
I recently saw that there was an update that introduced custom games of life, so I naturally updated to play with it.
After a little while messing around with it I wanted to make multiple instances of the GOL life type (B3/S23) with different colors so that they could "battle".
However, I noticed that after creating one custom GOL any new custom GOL's would persist the original custom GOL's color (Ex. I make a new life type called GOLR and make it red. I then try to make a new one called GOLB and make it blue, yet when I place it the color is red as if I was using GOLR). It would only use a new color if I changed the rule, and sometimes only if I changed the B part of it.
Please, please fix this so that its possible to do this!
It's good to know that a lot of people are seeing this so quickly as that means its more likely that someone will respond with help.
Edited 3 times by CarterLimb. Last: 11th Jul 2021 -
Custom GOL is uniquely identified by the rulestring. Meaning you can't have two GoL with the same rulestring, this will happen. The real solution to this is preventing multiple GoL from being added with the same rulestring.
You can manually deco the GoL and it will function how you want - you can see the GoL battle that way. -
I mean I guess that works, sucks that clones won't persist the decoration of a previous GOL when duplicating them.
-
Yeah CLNE won't do that, when it's stored in the CLNE it's just stored as the rulestring .. the manually applied deco color will only pass from GoL to its children that get spawned.
Way more effort than it's worth, but maybe you could have a BIZR contraption to decorate the GoL, or some DRAY copying the GoL from inside stasis wall. (this is an extreme solution to the problem though, lol) -
@jacob1 (View Post) By putting colored GOL pixels inside a stasis wall and then having a DRAY clone it constantly, it does create more GOL pixels of the same color. The only issue left is that the pattern which it is duplicated is predictable while having a clone making GOL pixels is random (so the "battles" would be the same each and every time).
I suppose having a clone on the initial green color of the GOL could potentially bring different results, but the "enemy" would always have the same tactic at the start.
EDIT: Ok I figured out how to make it random! I make a little circuit with a clone that would duplicate electrons (turned off heat simulation) and had some metal hooked up to DRAY pixels that duplicate GOL pixels suspended in a stasis wall! Providing unique results each and every reload!
EDIT 2: Could a sensor or something else be used to detect a specific decor on a pixel? (I would assume it's not possible as that doesn't seem like something that would be added, but I am unsure as I am still new to the program) This would basically be used for one GOL to destroy another one's "base".
Edited 2 times by CarterLimb. Last: 12th Jul 2021
