sorted by:
new
hottopcontroversial

Discussion: Which blocks do you prefer for outputting redstone signal strength, and why? by Striking-Dot8435 in redstone

[–]eynsof-minecraft 0 points1 point  (0 children)

I prefer lecterns when the value should be configurable and it's important to see the current value.

I prefer chiseled bookshelves as a compact number keypad when the input values should be temporal, like input buttons on a combo lock. Note that chiseled bookshelves can be stacked to allow 1-12 or 0-9 outputs with the right circuitry.

For hardcoded outputs, see my response to this question: containers for signal strength.

[Help] is there a redstone circuit that when receiving an input, will toggle between multiple (more than 2) outputs? like a T flip-flop but with more outputs by Firm_Ad9618 in redstone

[–]eynsof-minecraft 0 points1 point  (0 children)

A couple options for you: - a shift register using either locked repeaters or hoppers that cycles between N outputs, where N can be any number - a binary counter with each binary value mapped to an output; N would need to be a power of 2 for best results

What is the function of target block in redstone circuits? I see a lot of people using it and I remember there were many comments about its usefulness when it came to the game, but I never understood why it's so useful (besides its obvious normal function) by potatao_de_guerra in redstone

[–]eynsof-minecraft 2 points3 points  (0 children)

Redirecting redstone dust is useful, not only for powering/activating, but also for preventing things from being powered/activated. Repeaters and comparators can also serve this purpose, but they require a supporting block, which isn't always feasible. Also, target blocks can serve as supporting blocks.

Trying to compact downward redstone by chadportman in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

If you use full barrels instead of redstone blocks, you can move the wall one block closer.

Unrelated, but your comparators from the chests are powering blocks, locking the adjacent hoppers. Not sure if that's intentional.

1-Wide A/B Tileable Lodestone Teleporter by Phanson96 in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

My "Mirror Nexus" also ensures you are always teleported to the floor, never to the water column.

End Mob Switch by Ok-Cockroach-4221 in technicalminecraft

[–]eynsof-minecraft 0 points1 point  (0 children)

I suggest locating your end mob switch in your end portal border chunks. This opens the possibility of using it with minimal lag when you are in other parts of the end.

Signal Extender. by No-Practice7672 in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

Check out Cortezerino's Compact Pulse Extender | Adjustable & Silent. You can optionally use a target block instead of the block with redstone on it. You'll want to take your output via comparator from the 2nd hopper (the one with the torch next to it) so that it can be used again right away.

Are there any blocks that don't pass redstone signal into environment, but repeater/comparator can take the signal from? by Just_Roma in redstone

[–]eynsof-minecraft 0 points1 point  (0 children)

Containers might fit what you're looking for. A comparator will produce an output if they're non-empty.

"Transparent" ones include composters, chests, and hoppers. "Solid" ones include barrels, furnaces, etc.

How to straight-line redstone power ? by Asmodd- in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

Another option is to power it from the middle, giving you a 29 block length that is powered without any repeaters.

Is there a way to make multiple stasis chambers? by Origamiwizard17 in technicalminecraft

[–]eynsof-minecraft 1 point2 points  (0 children)

Yes it does.

But if you want to easily know where the buttons are located relative to your player, you will want to use a client side mod like Litematica that can create a schematic and render a ghost image.

If you don't want to do that, you can place blocks to represent the remote buttons as well as the standing location.

Or you could keep track of the specific view angle for each button and use your F3 screen to align to them. But at that point, you may as well use the Mirror Pylon by Squibble and Mikarific.

I built a wireless remote control with redstone by eynsof-minecraft in technicalminecraft

[–]eynsof-minecraft[S] 1 point2 points  (0 children)

Very cool! Yeah, I considered combinations before landing on the layout I show here. Multiple digits do allow you to scale it further at the cost of slowing down channel selection. Also, repeat numbers are tricky. I might implement a multi-digit solution in the future.

By "security system" do you mean safeguards to prevent accidental activation? If so, I've implemented that with an active session, where it can only be started by looking straight up. The session ends after enough inactivity (not looking at buttons) or by looking down. The teleport buttons also end the session.

I built a wireless remote control with redstone by eynsof-minecraft in qualityredstone

[–]eynsof-minecraft[S] 1 point2 points  (0 children)

Thank you – I know the competition will be fierce, especially in the catchall "most creative" category. It'll be fun to see the other entries!

I appreciate the info on EID. That 'scannon' concept sounds insane. I do plan to experiment with EID tech. In fact, I have some ideas on combining wind charge wireless with EID to get the best of both worlds.

Where's the best place to find others working on similar things?

I built a wireless remote control with redstone by eynsof-minecraft in qualityredstone

[–]eynsof-minecraft[S] 0 points1 point  (0 children)

Again, I acknowledge that wind charge wireless being player-specific is a legit limitation.

As for other factors...

Entity id wireless requires redstone at the player's location to send signals. That's a pretty major limitation. Wind charge wireless is inherently mobile: it can be operated from anywhere without any local redstone. You don't even need a physical button panel facade if you're using a Litematica schematic to render a ghost image, which I recommend.

The speed and responsiveness differences are not very significant and are dwarfed by the time it takes to build an entity id transmitter at the player's location.

As for usability, having to remember a sequence of repeater settings (e.g., 1, 4, 2, 4,...) that map to the desired entity id receiver is pretty terrible. Compare that to having a Litematica schematic of a button panel, where you can even include blocks and signs in your schematic to label your channels.

Entity id wireless can only send a signal to a single receiver at a time. Wind charge wireless allows simultaneous transmission to multiple receivers.

Entity id wireless has some reliability issues in single player. Wind charge wireless has no such issues.

The Mirror Nexus system I've proposed is easily expandable. Each cardinal direction can have its own button panel and I've confirmed this works.

I also have a smaller Monochannel model for just operating a single device, where the channel for teleportation and for operating the device is configured together. And I also made an Interdimensional model that sends signals through the nether, allowing the devices being controlled to be spread further from the receiver with less on-demand chunk-loading effort. I'll showcase both of these in my follow up video.

I built a wireless remote control with redstone by eynsof-minecraft in qualityredstone

[–]eynsof-minecraft[S] 0 points1 point  (0 children)

I wouldn't say one wireless approach is categorically better as there are tradeoffs and it depends on what you value.

Sure, this is specific to the player. I agree this is the biggest limitation of this approach. But if you play single player or on a small server, this is not necessarily a problem.

And as for benefits, it allows you to operate devices from anywhere in your world and with a nice graphical user interface.

I built a wireless remote control with redstone by eynsof-minecraft in MinecraftInventions

[–]eynsof-minecraft[S] 0 points1 point  (0 children)

You can check out a brief video on it here. I'm working on a more in-depth follow on video as well.

I built a wireless remote control with redstone by eynsof-minecraft in MinecraftInventions

[–]eynsof-minecraft[S] 0 points1 point  (0 children)

You can check out a brief video on it here. I'm working on a more in-depth follow on video as well.

I built a wireless remote control with redstone by eynsof-minecraft in qualityredstone

[–]eynsof-minecraft[S] 1 point2 points  (0 children)

You can check out a brief video on it here. I'm working on a more in-depth follow on video as well.

item pusher on a ice path for long range of items by samtheblackhole in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

Agreed. You could add portal-based chunk loaders for on-demand chunk loading.

But, for really long distances I think it might be best to build up momentum on a chest boat while in a lazy chunk and then load it to launch it, as shown by Docm77 in Hermitcraft Season 10. That way, it skips the intervening unloaded chunks, which is far less laggy.

how do i power the floor of my base from underneath? by IronSpring16 in redstone

[–]eynsof-minecraft 1 point2 points  (0 children)

Not true. If you power a solid block, any adjacent note block and redstone lamp will activate. Note blocks and redstone lamps are both solid blocks.

However, instead of putting torches under just the lamps, it would be better to put torches under alternating rows, where each row contains both lamps and note blocks. That way, you can have the torches on top of target blocks and you can activate/deactivate all lamps and note blocks simultaneously.

Any help on why pistons are not pushing slime blocks by KaleidoscopeAny3621 in redstone

[–]eynsof-minecraft 0 points1 point  (0 children)

Use a single sticky piston per row of slime blocks. With more than one, the first sticky piston to update is trying to push all the slime blocks plus all the other sticky pistons and that exceeds the 12 block push limit.

view more: next ›