Could someone make something that requires 3 inputs to be on. and when the inputs are not powered the output is off. I can't seem to make one.
AND-Set NOR-Reset Latch (5x5x3) by banjobeni
This circuit's output is only powered if all inputs are powered. Likewise, it is only unpowered once all inputs are unpowered again. Requires:10 torches, 19 wire Delay: 3 ticks
Combination Lock (17x17x4) by Banjobeni (schematic)
Wire up the buttons to a wall. The order in which you wire them up determines the code. For the picture below, the code is right to left. You can choose any code, but each button must only be pressed exactly once. When unlocked, simply press any button Requires: 67 torches, 147 redstone
Hope you like it.
Edit: Damn, just realized that in-game it needs a longer RET (5 torches) for the buttons. Will update this tomorrow.
trunks, I do not deterministically see another big time slot where I can rework the rest of the OP. I will at some time, I just don't know when. You can apply my recent changes now. As long as you post when you make updates to the OP, we should be race condition free.
Just a very stupid, very hacky idea on how to avoid the <number of buttons>^2 "bruteforce attack": have a counter that triggers the full reset of the latches evry once in a while, say, when it overflows. Attach a torch to it and show it on the button side. This way, the user needs to have the correct combination in some time frame, and if it takes longer, the system resets itself.
No wait, I have a better idea: attach a counter to the buttons. When <number of buttons>+1 presses have occured, reset the system.
I feel like my brain is thinking now about those combo lock things. Sorry, trunks, didn't do any OP editing today.
PPS. I'm sorry to say, but I loathe trying to work from the animated GIFs. They page too quickly to get a feel for if you've got a layer right. Often I end up having to copy the details down onto paper as best i can, and hope i haven't missed anything. I far prefer the 1/2, 2/3 etc type side-by-side diagrams.
PPPS. Are you still looking for a way to split animated GIFs into individual layers? I might be able to write a program to do that (been considering it anyway, with the problems I have with the animated ones). It would be Windows-only though (using .NET)
Quote from trunksbomb »
If you could make that program, it would be perfect. I'm running on Windows so it will work for me. Banjo has expressed interest in working on the OP as well, but I don't know what OS he is running.
I use Windows and am a pretty experienced .NET developer myself. If you can code that up, that would be cool. If you need help, don't hesitate to share. I suggest by PM to not clutter up this thread.
By the way, Banjo you can run through the OP and fix stuff up. You don't need my permission for that. I'll hold off on editing the OP until I hear back from you.
Ok, great. I will do as soon as I have enough time again. I can't promise to do it before monday (GMT+1), though.
Yea that's what I thought you meant, Banjo. Which means that what icks was saying is also right. We can get rid of that bottom row of blocks completely, as these aren't represented in diagrams normally. Then the wire on the bottom would just be sitting on the ground. It won't change the size of the circuit, just the size of the diagram.
Yes, it does change the size of the circuit. If you look closely, you'll see that it is already smaller. before/after:
Hmm but I'd still prefer if the bottom row is included in the .schematic, since when I paste it in, and there is no floor, then the bottom redstone won't be placed, leaving me clueless to what's wrong.
Still, you can move the right half down by one. If you place the first torch in the yellow block sideways, the bottom row is still redstone-free.
@trunks, I didn't get the ack from you to dig in the OP, so I'll postpone it.
Doesn't work for me. When I put a torch on one end and then remove it, it starts to flicker.
It does work, but did not in MCRedstoneSim. The idea is pretty cool.
And I do agree that we could go for some standardization. I've been trying to with the new format. I haven't gone through the OP and updated all the designs that we posted before the posting guide was thought up. Is that what you were planning on doing?
I guess so. I wanted to read through it carefully once. And while I'm doing this, I might also update some information that I see fit anyway. Don't expect to much, it won't shine golden afterwards, but at least I contributed more to the hard work of keeping it together than just providing circuits.
I just think the redstount counts are not well readable. I find myself looking up again and again which number is which. I think it would be better in one of the fluent forms I posted earlier.
trunks, can we normalize things a little? Sometimes we have TFF in the collection, sometimes it's T Flip-Flop. I generally don't like abbreviations, I only use them when it is very clear what it means.
I can go over the entire OP once and update things when I see fit, including adding downloadable schematics and details where they are missing and I see value in having them. But we should do it in a mutex fashion. So tell me if you want me to go through it once, but then hold back the editing until I'm done. I'm living in western europe, so I could do it, say, in 11 hours from now on? Should not take more than three hours, I guess.
I don't like how the redstone counts are set up right now. Maybe we/I can change it to one of these on the fly?
0
AND-Set NOR-Reset Latch (5x5x3) by banjobeni
This circuit's output is only powered if all inputs are powered. Likewise, it is only unpowered once all inputs are unpowered again.
Requires:10 torches, 19 wire
Delay: 3 ticks
0
"be waiting"?
"above"?
Please explain.
0
0
Combination Lock (17x17x4) by Banjobeni (schematic)
Wire up the buttons to a wall. The order in which you wire them up determines the code. For the picture below, the code is right to left. You can choose any code, but each button must only be pressed exactly once. When unlocked, simply press any button
Requires: 67 torches, 147 redstone
Hope you like it.
Edit: Damn, just realized that in-game it needs a longer RET (5 torches) for the buttons. Will update this tomorrow.
trunks, I do not deterministically see another big time slot where I can rework the rest of the OP. I will at some time, I just don't know when. You can apply my recent changes now. As long as you post when you make updates to the OP, we should be race condition free.
0
No wait, I have a better idea: attach a counter to the buttons. When <number of buttons>+1 presses have occured, reset the system.
I feel like my brain is thinking now about those combo lock things. Sorry, trunks, didn't do any OP editing today.
0
I use Windows and am a pretty experienced .NET developer myself. If you can code that up, that would be cool. If you need help, don't hesitate to share. I suggest by PM to not clutter up this thread.
0
Ok, great. I will do as soon as I have enough time again. I can't promise to do it before monday (GMT+1), though.
0
Yes, it does change the size of the circuit. If you look closely, you'll see that it is already smaller. before/after:
0
That's what I meant.
0
Still, you can move the right half down by one. If you place the first torch in the yellow block sideways, the bottom row is still redstone-free.
@trunks, I didn't get the ack from you to dig in the OP, so I'll postpone it.
0
Doesn't work for me. When I put a torch on one end and then remove it, it starts to flicker.It does work, but did not in MCRedstoneSim. The idea is pretty cool.
0
Does anyone know how to build a two-way bus?
0
Why shorthand? Come on, we have enough space there. Make it readable in clear english:
Requires: X torches, Y redstone
Everyone understands this right away.
0
I guess so. I wanted to read through it carefully once. And while I'm doing this, I might also update some information that I see fit anyway. Don't expect to much, it won't shine golden afterwards, but at least I contributed more to the hard work of keeping it together than just providing circuits.
I just think the redstount counts are not well readable. I find myself looking up again and again which number is which. I think it would be better in one of the fluent forms I posted earlier.
0
I can go over the entire OP once and update things when I see fit, including adding downloadable schematics and details where they are missing and I see value in having them. But we should do it in a mutex fashion. So tell me if you want me to go through it once, but then hold back the editing until I'm done. I'm living in western europe, so I could do it, say, in 11 hours from now on? Should not take more than three hours, I guess.
I don't like how the redstone counts are set up right now. Maybe we/I can change it to one of these on the fly?
[*:1khc1g84]Requires: 12 torches, 15 redstone
Yes, I'm a prefectionist...[*:1khc1g84]Redstone: 12 torches, 15 wires
Edit:
I think you can move the left 7x7 blocks down by one.