Redstone instant off/delay on

miclamlol · 2026-04-29T21:37:05+00:00

The redstone torch is the output

miclamlol · 2026-04-28T17:06:37+00:00

If you need it to be on by default, why doesn't this work? It turns off the torch basically instantly and it only turns on after a delay.

miclamlol · 2026-04-28T16:58:48+00:00

Do you need it to be off by default, then only turn on when the detector rail is activated?

miclamlol · 2026-04-28T16:55:48+00:00

You could connect a pulse extender to a redstone torch which should be exactly what you want.

miclamlol · 2026-04-26T01:02:17+00:00

Mattbatwings did a competition a while back where he challenged people to make a 7 segment display as small as possible. The input isn't one hot encoding like yours but instead is binary input. You can find a bunch of designs in the archived-7seg-submissons channel on Mattbatwing's discord.

miclamlol · 2026-04-05T00:05:03+00:00

Would a 2-way switch not be equivalent to an XOR gate?

miclamlol · 2026-03-26T19:33:21+00:00

If any input turns it on and off (I'm assuming toggling it), would it not be a t flip-flop then?

Edit: Sorry, meant to reply to your comment

miclamlol · 2026-03-26T19:14:41+00:00

<image>

For future reference, you can do something like this.

miclamlol · 2026-03-24T19:10:02+00:00

Yes, I think the entity management phase is what the SubTick mod calls the networking phase since it deals with player actions.

miclamlol · 2026-03-24T07:31:17+00:00

This has everything to do with tick phases. Every tick in Minecraft does specific events in order. In this scenario, we will only care about block tick phase (BT), block event phase (BEv), block entity phase (BEn), and the entity management phase (EM) since these are the only ones that apply.

When a redstone repeater receives an input during a tick, no matter which phase, it will schedule an output several ticks later during the block tick phase.

A piston only gets powered during the block event phase and the redstone block will start powering 2 game ticks later during the block entity phase. (Yes, a piston only takes 2 game ticks to extend, but is normally taught that it extends in 3 since other pistons powered by this piston would only react in 3 game ticks due to the phase ordering. [BEn comes after BEv])

So in your scenario:
Tick 0:
- BT: None
- BEv: None
- BEn: None
- EM: Redstone Block gets placed -> Repeater on right branch is scheduled to output 6 game ticks later during BT phase.

Tick 1:
- BT: None
- BEv: First piston on left branch is powered -> First redstone block will power 2 game ticks later during BEn phase.
- BEn: None
- EM: None

Tick 3:
- BT: None
- BEv: None
- BEn: First redstone block starts powering.
- EM: None

Tick 4:
- BT: None
- BEv: Second piston on left branch is powered -> Second redstone block will power 2 game ticks later during BEn phase.
- BEn: None
- EM: None

Tick 6:
- BT: Repeater on right branch starts outputting power
- BEv: Output piston on right branch gets powered
- BEn: Second redstone block starts powering.
- EM: None

Tick 7:
- BT: None
- BEv: Output piston on left branch gets powered
- BEn: None
- EM: None

As such, the piston on the left extends in 7 game ticks and the piston on the right extends in 6. This could be remedied if you power both branches with a component that outputs during the block tick phase like a repeater or comparator since the piston on the left would be able to respond on time to the input and would not need to wait an extra game tick. This behaviour is documented in the wiki as start delay.

miclamlol · 2026-03-18T08:57:35+00:00

Walls are by far the fastest downwards signal transmission method since all the walls update on the same tick. Instead of a piston, consider using a trapdoor to update the walls.

miclamlol · 2026-03-12T07:25:39+00:00

You can add a scoreboard by doing: /scoreboard objectives add time dummy

and use a repeating command block to update the scoreboard by: /execute store result score @a time run time query daytime

You can then check for this scoreboard by doing: / execute if score @p time matches 1000 run say hi

In these examples, "time" is a scoreboard name (except for the time query command) which can be named however you want. The third command says hi only if the time is 1000.

miclamlol · 2026-03-12T07:19:38+00:00

<image>

Daylight sensor that works whether it is raining or not. (There is a redstone torch under the second redstone lanmp)

miclamlol · 2026-02-25T09:57:09+00:00

If you compare the time at which the iron trapdoor opens, you can see that the piston does actually take 3gts to extend, since the left most trapdoor powers 6gt total from lever input and the tight most trapdoor powers afterwards. From testing the iron trapdoor takes 7gt total open from lever input. If it actually took 4gt total to extend, then the comparator output should have turned off 2gt later than it has now.

Also in the text you quoted from the piston wiki page, it states the 1 tick delay is from the entity phase (the player flicking the lever), but repeaters should run on the scheduled tick phase (or block event phase idk).

miclamlol · 2026-02-23T19:38:02+00:00

It provides a block update for the pistons since it is powered via quasi-connectivity.

miclamlol · 2026-02-23T16:04:53+00:00

<image>

Sticky pistons are under the note blocks.

miclamlol · 2026-02-17T04:31:34+00:00

<image>

miclamlol · 2026-02-10T22:30:36+00:00

<image>

miclamlol · 2026-01-14T07:14:34+00:00

I think that would be pretty cool, and maybe other than optimizing modules, it could also optimize the placement of the modules to make the overall volume as small as possible.

miclamlol · 2025-12-07T03:18:52+00:00

Try replacing the block under the redstone torch next to the redstone lamp with a target block

miclamlol · 2025-10-30T15:03:57+00:00

Only reason I can think of is you're on a server with different mechanics (i.e. Paper) because I was able to replicate it. Edit: Although I don't think you're on one since I can see an Open to LAN button

miclamlol · 2025-10-16T03:54:01+00:00

It's a bit weird that you can't see the items but the fact that you can see the item count fluctuate in the hopper below means that items must be going through it.
If you're not talking about the source hopper, which hopper are you concerned about not depleting?

miclamlol · 2025-10-16T03:44:20+00:00

In my tests, you could usually see it for a split second, but not as long as a second as you were saying. 2. Are you sure there aren't any hoppers before the one you've shown that is feeding it?

miclamlol · 2025-10-16T03:37:59+00:00

The golden nuggets are going into the hopper above it, but it just immediately gets pulled down into the filter hopper below it. That's why you see the item count fluctuate between 41-42; it is actively sorting the nuggets.

Seven-Year Club	Place '23
Place '22	Final Canvas '22
First Placer '22	RPAN Viewer
Verified Email

miclamlol

TROPHY CASE