How about some videos instead:
Or if you prefer a 1 block wide solution:
- Registered Member
Member for 9 years, 11 months, and 4 days
Last active Thu, Oct, 16 2014 22:53:57
- 0 Followers
- 291 Total Posts
- 1 Thank
- To post a comment, please login.
Aug 19, 2011Hans_Lemurson posted a message on Hans Lemurson gives a Preview: Minecraft in MinecraftYou all know that joke when somebody is showing off their brand new Redstone Computer and somebody asks: "Can it run Minecraft?" You have a chuckle at how clever you are while people variously chime in "LOL" or "It's impossible numbskull!!!".Posted in: Redstone Discussion and Mechanisms
I was one of the people in the latter group, continuously annoyed by people who don't understand the orders of magnitude of difference in computing power between a Redstone Computer (they are on par with 1930's technology) and a modern computer. After a fresh session of apoplectic rage however, I began to ponder: "What sort of program could you feasibly run on a Redstone Computer that would still retain the essence of Minecraft?" And thus a dream was born.
That was 3 months ago. After months of planning and sporadic construction work, I have finally completed this great and grand project which I intend to be my "Magnum Opus". I have made "Minecraft in Minecraft", or "Mini-Minecraft".
-8x8 Pixel Screen
-64 bits of Landscape Data
-Directional Control Interface
-Moderate Signal Latency (4,000ms)
And now to show that I'm not just full of ****, I give you screenshots:
Display viewed from control-box
Here you're staring at the crazed mish-mash of all the terrain created/destroyed in my debugging attempts. Player position is not visible, since that square is currently OFF in its blink-cycle.
The orange and pink lines are carrying the Vertical Position data from its register to the display. The sharp-eyed will notice that there is a torch lit on right side of the middle pink line. That's the current height of the player. I placed those torches there for debugging purposes when I was having problems with data corruption.
High view of back of Display
Light and Dark Green helixes carry new data to the Display, one Bit per column. Purple lines in the background carry the "Write" command to an individual Row to update its D Flip-Flops when a block there is placed or removed.
Guts of the machine
Here you see all the parts of the machine that do the actual calculations. Underneath the green lines is the 64 bits of RAM (the green lines are its input) that store the terrain information for calculations. In Blue at the far end are the Horizontal positional controls which both keep track of the player's horizontal position and govern interaction with blocks. The Gray stuff to the left is the circuitry needed for the "Jump" command, and underneath it is the rest of the Vertical positional controls.
Here you can see 4 of the 9 Control-Bits that govern the machine. Combining "Shift Up" with "Place/Remove Block" results in the block above your current position toggling between ON and OFF. Note the long chains of Repeaters on some lines: It was necessary to introduce carefully tuned signal-delays to ensure that the Positional/Terrain actions don't happen until they have already been pointed to the right location. Getting the signal-delays synchronized like this took many hours of frustrating debugging even after I thought I was "95% done!". Well, I'm done NOW.
Wires Leading to Command Decoder
Here you see the wires from the Control-Box going down to be converted into signals sent to the Control-Bits that actually govern the machine. Pink/Orange are Down/Up and Light Blue/Teal are Left/Right. They split into 2 lines in the decoder: one for Movement, the other for Block manipulation. The Red line is in charge of triggering an extra "Move Downward" command after every action you perform in order to simulate gravity. A solid block underneath you will prevent this downward motion.
Here are the 5 controls that will let you move through the world. 4 directional controls and a switch to toggle between Movement and Block Placement/Removal. It's humbling to realize just how much work is required to convert a simple button-press into an executable command. It takes about 4 seconds for the effects of a button-press to be visible on the screen.
So, that's the sneak-preview of my machine.
I'm calling this a "Sneak Preview" because the real presentation is going to be the Youtube Video I'm planning on making which will show this thing in action, accompanied by mad laughter and melodrama and will get its own dedicated thread. My intention is for that video to go viral and explode the internets.
Oh, and also I'd like to give thanks to Conundromer for deciding not to beat me to completion of this project while I was on vacation, even though he probably could have if he'd set his mind to it(he's good).
If you think that "Minecraft in Minecraft" is totally awesome then feel free to +1 my Reputation. The higher it gets, the sooner my video comes out!
Edit: The video is out as of Aug 31st.
See this thread:http://www.minecraftforum.net/topic/590096-hans-lemurson-makes-minecraft-in-minecraft/
Aug 16, 2011The D-Flip-Flop, or "Data" Flip-Flop is the fundamental unit of computer memory systems. It is a device which lets you automatically store values in a place where they can be accessed later. The "Flip-Flop" part of its name refers to how the memory cell at its core can switch between two different stable states, much like a flat rock that gets flipped over (only without the rock).Posted in: Redstone Discussion and Mechanisms
"Data Flip-Flop" can be abbreviated to "DFF" for ease of typing.
A DFF contains 2 Inputs and 1 Output:
-The "Data Input" delivers information to the device that may or may not be stored.
(Commonly represented by the letter D)
-The "Enable" Input which causes the Data to be written to memory. Also commonly called the "Clock" input, but I find this misleading.
(Represented by the letter E (or C in some diagrams)).
-Lastly, the "Output" displays whatever value was last stored in the memory.
(Represented commonly by the letter Q. (Don't ask.))
However, although its usage is fairly straightforward to understand (E makes D->Q), the manner of building such a device and its internal operation are rather mysterious to many people.
I intend to correct this using the POWER OF COLORED WOOL!!! I will be showing you a fairly basic DFF design with all it's different components color-coded for your convenience. It's not the most compact design, but I chose it because it's easy to actually see what's going on.
Is the Memory Cell itself. It is an "RS NOR Latch", or "SR Latch" or "SR Flip-Flop". "SR" stands for "Set-Reset", referring to how data is entered into it. Its great strength is how small and compact it can be. Its great weakness is that it requires 2 different inputs in order to operate. :angry.gif:
Fixes that problem. It holds a pair of torches which are always in the opposite state of one another. One acts as the "Set" input for the SR Latch, and the other acts as the "Reset" input. But most importantly, they themselves can be controlled by a single input. Unfortunately, this component also has a critical weakness: It writes to memory all the time, since at least one of the torches is on at any given time. An SR Latch by itself is a stable memory cell, but once you add the Orange torch-pair it's continually buffeted by the winds of change. Solution: Add another component. That'll fix things for sure!
Holds a carefully positioned torch which when ON, will shut-off both of the Orange Torches. While the Purple torch is ON, the Latch can rest in peace. Torch ON = Hold, Torch OFF = Write. Given this functionality, it is unsurprising that the Enable input controls this torch directly.
Fortunately for you the Reader, I have included pictures to better illustrate what I'm talking about.
Behold the screenshot!
Here we see a DFF with 2 inputs and an output.
On the left, connected to Purple is the "Enable" input.
See how the torch is causing both Orange-torches to be shut off. No data is getting into the Latch so long as that torch is on.
Activate the D Input...and nothing?
The "Data Input" in the middle has just been turned on. The Purple torch is still suppressing any and all Writing, so the little output wire on the right is still off. So long as it remains active, the fluctuations of the D Input will be ignored.
Open the gates and unleash the flood!
The "Enable" input on the Left has just been turned ON, causing the suppressing torch to deactivate. Now the value from the "Data" input is feeding directly into the Latch, causing the Output to turn ON just like the "Data Input" is.
What goes in, comes out.
The "Data Input" has been turned OFF, and the Output follows suit. This is what happens when "Enable" is ON.
D Flip-Flops can take many different forms, but operate under the same principles.
Here is a "Vertical" (one block wide) DFF built using the same color-coding scheme as before (but with some additional colors to reduce ambiguity). Green represents the "Data Input" which although it feeds into the Orange torch-pair, needs to be treated as a separate component. Similarly, Teal is the "Output" which although it simply displays the data from the Latch, some more advanced designs (those used in RAM) require that you be able to turn off the output without corrupting its Data.
In this picture, the "Data Input" is ON, but since "Enable" is OFF, the Output remains unaffected.
(If you felt that this post was educational, feel free to give me a nice +1 to my rep! If you push it above 50, I get a gold star!)
- To post a comment, please login.