How To Cut Wires (GROUNDBREAKING TECH)

Can you show me what you did?

2 Likes

In a minute. It does not seem to work with recursion clocks?

2 Likes

Well, if you don’t trigger at very similar times (like only minor AUO differences), then it seems to not work. My experiment backed this. This might prove ticks.

2 Likes

Wait, what is the design that you’re using? @Apoll02

2 Likes

Nice guide @Shdwy

2 Likes

GIMKIT NEWS:
@Shdwy discovers a new game mechanic!
SEE PG. 6A

3 Likes

1 Like

Wow, this is very cool!

(Apoll02’s screenshot has a rare picture of Blackhole927 in it.)

5 Likes

Ok, I can figure this out.
On the left is the confirmation mechanism. It’s hooked (via wire?) to a trigger which is hooked to a repeater (also via wire what the heck is going on here)

The repeater is also connected to a cutter, and there’s another confirmation mechanism to the right? Lifecycle triggers repeater, I assume.
In summary, you have a wire cutter and are testing 2 different methods of cutting.

Out of curiosity, a few things:
One, don’t all the wires skew the test results?
Two, why the repeater clock instead of a traditional trigger clock?
Three, the wire cutter only needs 2 outputs lol it should work fine with just that
Four, why multiple confirmation mechanisms?

Did you know that wires always go clockwise?

3 Likes

One, not necessarily; they fire at different times and would only affect it in a non-result-altering way.
Two, it didn’t work with that.
Three, it needed four for me, I tested all of this already.
Four, wdym?

For four, multiple counters. Also, is the trigger triggering itself with channels?

Yes. The extra counter is what I was testing. The one on the right is control.

@GimAI rate this 1-100

1 Like

Gimai has been discontinued.

Summary

How do you know about gimai?! It’s been 3-4 months lol.

So, given that the cap seems to be per second, I’m willing to bet that it would interfere unless you have it running before the cutter.

Two, wdym a trigger clock didn’t work?

What results have you found?

Can you explain why you think that there aren’t ticks?

1 Like

It didn’t cut correctly. Two, the second one still ran correctly without reusing a new cutter, so that means that it isn’t per second.

No. But now that you mention it…

Because I have seen incredibly conflicting evidence and we’ve found no ways to track even a semblance of ticks.

@Apoll02 What specific results did you find?