ConwayLife.com

I don't know what exactly you mean when you say "confocaloid-signal". Would you please consider putting some more effort into understanding that point, then? It's been explained quite a number of times -- here , for example. As an immediate consequence, "moving object" cannot be a superset of "sign...

I'm drawing a blank on why LifeViewer is giving an "unsupported rule name" error, since the rule is definitely out there in the LifeWiki Rule namespace It's because there's an error in the rule definition. The following line ends with a ) rather than a }. That's 15 minutes of my life I'm not gettin...

Considering that you are discussing the topic "2c/3 signal receiver", and there's just one signal (which is received) as long as you are focused on the receiving mechanism, it feels to me to be very confusing to apply the same word in the same discussion to mean a completely different thing. I'm so...

I don't really see how you would need three signals somewhere in either of those patterns. As far as I can tell, any working 2c/3 receiver accepts just one signal at a time, arriving through the wire. Um... we've been through this topic before, a truly impressive number of times. When I use the wor...

calcyman wrote: ↑

March 27th, 2024, 10:46 am

repeat time 834...

... It's an impressive coincidence that the first part of the staged-recovery mechanism, the Callahan G-to-H, also needs exactly 834 ticks to recover. (At least I think it must be a coincidence.)

Should a new category article be added for "2c/3 signal receiver"? I just put in a CurrentNews item for Entity Valkyrie's discovery, and wanted to have an article to link to -- but there doesn't seem to be one: "receiver" currently just redirects to "Herschel receiver". Details about the receiver en...

Entity Valkyrie 2 wrote: ↑

March 27th, 2024, 8:06 am

Got it! 2c/3 receiver, repeat time 876...

Awesome! For this kind of problem, 876 is a pretty darn good improvement over the previous record of 964 / 970 -- and it does work perfectly well on double-length signals, assuming I ran the test right, so it can be used just as well after a 2c/3 elbow.

I've just commited an update to safeopenclip.lua for community testing. ... Note: This version benefits from a new build of Golly to suppress warnings while testing different rule variants. Looks good! The script is eminently testable using the current beta -- there's just one extra pop-up error wi...

Discord crosspost request for context and discovery information of Rule:LiterallyAnEntireRuleForOneStupidSpaceship . What were the patterns? What is known about this thing? Not much, it appears! Sorry, I went and looked on Discord when you posted this request, but didn't find any satisfactory answe...

(Tell Ian07 not to upload any rules to LifeWiki unless allowed by the creator.) Posting rules to the conwaylife.com forums implies that they're available for public use, especially if those posts don't contain any labeling that says they're "just for test purposes". Should the posts where these rul...

How are the existing ones there, then? If I remember right, those four were maybe the only named gun patterns on the LifeWiki at one point, that had a " |synthesis = {N}" line in their infoboxes. Somebody who understands the connection between Catagolue and Shinjuku better than I do, submitted one ...

There isn't a particularly easy way to get a synthesis of a gun pattern into Catagolue, right? We either have to post a synthesis of a capped version of the gun using the nonmagical box.

-- Or, maybe alternatively, submit a pull request to Shinjuku?

I'm still looking for feedback about what exactly the toStandard.lua, toSuper.lua, and toHistory.lua conversion scripts should do with [Rule]Investigator rules =-- and what toInvestigator.lua should do with Super and History patterns. I think I have a workable plan to start with, anyway: First I'll ...

I just built a true period-41 emitter for the 2c/3 signal, which I optimized as much as I could... Nice! It looks like that works down to p36, at the 2c/3 signal insertion side anyway -- the LWSS stream would have to be built differently somehow. Not sure what the best solution would be for that. A...

Removed the extraneous period.

Unless I'm missing something, that would imply restrictions on rule filenames that are analogous to existing restrictions on LifeWiki pnames. In particular, "+" and "^" would have to be rejected. Allowed rule filenames would be those allowed by existing conventions in "Help->File Formats->@RULE" (a...

Suggested fix: undo for the first linked edit (page Butterfly hasslers ); clarify relevance for second edit (page Silver's p5 ). Question for hassler-builders and other terminology experts: is there more or less of a consensus that to be a "hassler" of Object X, a pattern has to have hassling objec...

This is deliberate. If there is an error in the bounded grid definition and it's carried across to the safe rule then the pattern still won't open. What do you think of the two-stage approach? Try opening the safe rule with the bounded-grid suffix, and then if that doesn't work, try the safe rule w...

Maybe instead add a status bar message along the lines "Unknown rule; the pattern is converted to a default 256-state rule; go to View -> Pattern Info to get the original rulestring". Yup, something along those lines seems like the important info to put in the status bar. It might not be necessary,...

[*] (a) these lines clutter pattern comments. The more is added, the harder it is to understand what is going on. The instructions belong to help system. The idea of cluttering pattern comments with extra added lines was originally yours , not mine. Once the script is adding a new comment line anyw...

Just noticed that the "safeheader" definition in the current script doesn't preserve the bounded-grid suffix from the original rule, if there is one. Any thoughts on appending the bounded-grid suffix, if any, to the "Display256" safe rule? Are there situations where the bounded grid will work for so...

In the commit you linked to, the script does not do what I suggested, but instead attempts to do the reverse. It keeps the three-line extra advice enabled, unless the script can detect some kind of unsupported character. This kind of detection cannot be done in a satisfactory way, because there wil...

It is useful to be able to view and copy the actual rulename/rulestring that was specified in the pasted pattern snippet. So, for example, a single-line message of the following form is useful for a human Golly user: #C Golly converted unsupported rule: R5,C0,S33-57,B34-45,NMHistory That line is st...

it says catagolue instead of catalogue. glad to be the first one to point out this typo. ... Heh, you're a long way from being the first. It's a rather subtle in-joke that often just escapes people's notice for a long time, just like a lot of people can read right past badly jumbled word centers as...

If the resulting script happens to have some complicated logic to make it hard to test comprehensively, well, no big deal, but it is something to keep in mind. The added code is quite minimal -- it just generates the three extra comment lines that are quoted above. And now it seems to do it correct...