Search results

Those screens have the label "METADATA" above them, that's the raw data which has been processed to be somewhat meaningful. Typically hex data ends up looking more like this; And when the Nasometer's storage is full, it should look somewhat like this; That takes a long time to observe...

I think that a universal data storage method may be difficult. Some applications require different solutions to more effectively use space. This is kind of a bad example, but we can look at the differences between Galactus' storage needs, in his latest thing, and my storage needs, in the...

I might make a guide on them sometime. Essentially, they are what their name entails - pulses which are instant. Basically by using some logic (mostly with flipflops and activators, but some other things work as well.) you can make it so that the visual output of a system is constant while the...

I made a 3x3 circuit that closes a door 1.5-2 seconds after you open it. Just hook up the sensor to one door, and the flipflop to all the doors. I had to cheat and use instant pulses, but it does its job.

If you're looking to add a command to the beginning of a text, I like to use [replacefirst][with][add] since it has no prerequisite for what characters must be contained in the text. You probably already know this, but maybe someone else will find it useful.

You can compare the contents of display modules using sensors, if that's what you mean.

Is this not the functionality you are describing?

1: Copy the original statement onto a second display block. 2: Use "[REPLACEFIRST]regex[WITH]temp" on the second display block. 3: Use a sensor to determine if they are the same. 4a: If they are the same, the text did not contain "regex". 4b: If they are not the same, the text contained the word...

.

That being said, that sensor idea got a huge boost in viability with the addition of fleets. Now, you can send your sensor wherever you want, it just takes a little time.

This is totally possible, the reason people don't use it is the set up requirement and the issue of having people at your HB accidentally messing with your chaindrive.

Just experiment with a lot of things, anything you think might be cool. Try to make logic weapons, see what passives and other systems interact with logic, play around with displays. Just do stuff, and see what you can do. If you have a question, ask on the docks, and see how different people...

I was going to say something, but Heillos beat me to it. If 800+ people downloaded logic that just charges their JD's for them, and lets them go across the galaxy faster, I really don't know how many people wouldn't download something that eliminates both cloakers and radar jammers. TBH, I like...

A video showing the functionality of the new METADATA command will be added to the main post soon™. Basically the thing is 4 taller now, for not a lot more functionality. Hopefully I'll add more soon. This thing takes, like, five fucking minutes to figure its data out.

[SUGGESTED]<multiple times>

For my nasometer, I needed to increment in decimal and in hexidecimal, so I decided to figure out Snapems counter. TBH, modifying it is p. easy. As a base, the original is [REPLACEALL]\b([0-9]+)\b[WITH]0$1~01234567890 [REPLACEALL]\b0(?!9*~)|([0-9])(?=9*~[0-9]*?\1([0-9]))|~[0-9]*[WITH]$2 My...

if you press f5 or f6, you take an in-game screenshot.

Nope. If you just have content, you get an exact copy of the input, which would still end up with [SPEED] and [25 m/s] being compared. If you use other tags, like [ADD], you get roughly the same effect as the direct copy, with [SPEED] being added, rather than the output. What you see on the...

Unfortunately this doesn't work. Display modules only compare the input, not the output. You may see [25 m/s] and [25 m/s] as the same, but a sensor see's [SHIPSPEED] and [25 m/s].

Thing is, it's really easy to parse backwards, i.e. remove one word at a time, compared to parsing forwards, adding one word at a time. I might try to do something with this tho.