02-06-2014, 07:28 PM
Hey some of you will (hopefully) remember me from the RDF.
Not sure if it is necessary for me to do an application/trial (again) but didn't want to make any assumptions so here we goooo
Minecraft name: Burgled
What do you like the most about redstone?: Lots of room for innovation.
What's a thing you have made which demonstrates redstone knowledge?:
My proudest invention would be my method for addressing piston tapes, extremely compact, simple looking, can run faster than a tape can even spin. I s'pose piston tapes are bit outdated these days though
What does the thing do?:
As in how does it work? Well it uses a piston based binary clock which stops once the output reaches 0, the input toggles the pistons that show the output thus telling it how much to increment. The internal state of the clock ensures it doesn't lose its place. It's hard to explain because its complicated, the output pistons act like xors for the input and clock state but more compact and fast.
Image and/or video, from imgur.com or youtube.com:
Here's a 4 bit version of the addressing a managed to dig up on a single player world, not compacted.
This second one is a picture of my 256 byte RAM before it was finished, I did later finish it but this is just the only picture I've got. I can't recall how fast it was hrrm. Each bit was 4x3x6 tileable (IIRC) and of my own design, stacked and addressed to minimize latency.
Do you agree with the rules?: Yes
Not sure if it is necessary for me to do an application/trial (again) but didn't want to make any assumptions so here we goooo
Minecraft name: Burgled
What do you like the most about redstone?: Lots of room for innovation.
What's a thing you have made which demonstrates redstone knowledge?:
My proudest invention would be my method for addressing piston tapes, extremely compact, simple looking, can run faster than a tape can even spin. I s'pose piston tapes are bit outdated these days though
What does the thing do?:
As in how does it work? Well it uses a piston based binary clock which stops once the output reaches 0, the input toggles the pistons that show the output thus telling it how much to increment. The internal state of the clock ensures it doesn't lose its place. It's hard to explain because its complicated, the output pistons act like xors for the input and clock state but more compact and fast.
Image and/or video, from imgur.com or youtube.com:
Here's a 4 bit version of the addressing a managed to dig up on a single player world, not compacted.
This second one is a picture of my 256 byte RAM before it was finished, I did later finish it but this is just the only picture I've got. I can't recall how fast it was hrrm. Each bit was 4x3x6 tileable (IIRC) and of my own design, stacked and addressed to minimize latency.
Do you agree with the rules?: Yes