Does anybody have a really fast design for a decoder? And I mean really fast. I need something to designate address locations extremely quickly. This model works fine manually, but in a computer everything is going to be activated at the same time. I'm afraid the information will be sent and read too quickly and by the time my signal arrives to allow pulses to be received, I will lose a few bits of data. I haven't been able to find one good enough so far, and have had trouble designing anything faster than 4 ticks at the last location. =/
Well, I was bored last night, so I decided to complete another mini-project. M'ladies, M'gents, I give to you... the REDSTONE INTERNET!!! Well... actually this is more like system link, but it is still the base of networking, which is the base of the internet. It can send and receive packets of data over an arbitrary distance, so it is still a network of sorts.
Although, the system is very much stripped down. The device connected to the computer can only send data, and the other component can only receive data. I pretty much just put this together to test a method I've seen used very few times, which allows one to send information, of any size, over a single line. That's right, one single line.
Behold:
This is how it would connect to the computer... sort of. Only the data inputs are connected, they're attached to the reading bus. I didn't bother hooking up the instructions since this is only a prototype. I only needed a functional model that I could operate manually. It was never used by the computer, I simply hard-coded bits into the device and activated the instructions by hand. This photo is just to show you how it would be connected to a computer.
This is the entire system. All of the data is sent on a single wire, a 1 is represented by a 4-tick pulse and a 0 is represented by the line remaining in a low state for 4 ticks. This could be faster, and will be by the time I have a complete router for my next computer. Also, all the repeaters on the data line are unnecessary, that was a part of testing, making sure the pulses were timed correctly.
I'm sure you're wondering how an 8-bit binary word is converted to a system based on pulses. Well this is the point where I'll start getting into that. It involves very precise timing and it's an extreme pain in the ass to deal with. In the above screenshot is the start of the process, an 8-bit register that saves your regular ol' binary data.
Here is where all the timing comes into play. This is... I guess you could call it a decoder. The pistons extend for a period of 4 ticks each, one by one, leaving no gaps in the pulse-based coding. It basically converts 8-bit binary words into a 32-tick string of pulses, allowing it to travel on a single line.
The pulses are sent onto the line in front of the repeaters and travels along the top line that exits the left side of the shot. The pistons must be activated by a 1-tick pulse, which is why they are activated by a monostable circuit. The bottom line is a signal from the monostable that travels to a set of pistons in the receiver, timed to arrive 4 ticks before the data arrives, making sure the pulses are read correctly.
This is the receiver, where timing issues became a real pain in the ass. After building, it took probably half an hour to get this thing to work correctly. It is built in a very similar way to the first device, only it's designed to read the pulses and convert them to a stable binary state.
This is where the packet of data winds up in the end of it all. This is just a series of RS NOR latches that save the information once read by the receiver. Even though it's nothing like it, you could think of this as cloud storage. They're somewhat similar... sort of... in a way.
ANYWAY, let's send some dataz. We'll be sending 00101111. Which is, you guessed it, 47.
^^^ Binary input
^^^ Receiver output (top torch = 1, bottom torch = 0)
That's really all there is to it. By the time I implement this in an actual computer the design will be a lot faster and much more advanced. I plan on using this basic system to actually build a full router. Keep in mind this is an extremely basic example, and is more like system link than true internet. The final version will have a hub to connect multiple devices together, and every device will have its own "IP address" more or less, it will be a LAN. But, with very few modifications and a lot of expansion, LAN can easily be turned into WAN.
Comments, questions, yada yada, you know the drill.
+1 Your the only person i know that can use redstone in ways ill never understand
I think I may be one of the few people here that actually read and understands what you did here. Not a small feat at all considering this is an arcade game on a 360. I was just trying to explain this exact theory to someone a few days ago, explaining how much can actually be done with the limits of redstone and the possibility of sending binary data down a single line. I've been tempted to start building some basic circuits to play around but haven't gotten bored with the survival part. Once creative mode is available I'll probably start building something. Thanks for an interesting post. +1
And just to chime in on the section issue, I prefer this stuff gets posted here as I don't wander off the XBox section.
Shouldn't you be working for NASA or something...Very impressive. +1
I've actually thought about replicating Apollo 11's Guidance Computer. But, most of the components are impossible in Minecraft, as far as I know. The rest of the parts just aren't practical.
The CPU is set up in a very strange way. The ALU is actually very simple and would be easy to build, but the problem is how it receives information. In my CPU's I take the data from the reading bus and wire it to two registers, that can send it through the ALU. In Apollo's computer these registers are set up to output onto the reading bus. If you tried to read from both registers at the same time it would OR the values together, then send it through the ALU. This would be nice in some rare extremely specific scenarios, but most of the time it Would just be slowing things down.
Dude your redstone builds are seriously impressive. Are you a programmer or something?
Believe it or not, I'm pretty amateur as a programmer. I play around with Python sometimes, but haven't written anything that impressive. I enjoy programing redstone computers a lot more. There is nothing more low-level than physically (you know what I mean) writing a program with raw 1's and 0's. I like controlling every single instruction, as opposed to using modules in high-level programming languages that do several things at once.
Forgive me for sounding dumb asking this question but the simple fact is that whilst I haven't used red stone a great deal I don't see the point of something so large, no matter how impressive the build might be.
If you want a detailed explanation, read the OP. I went over just about every aspect in detail. But, here's a rundown anyway.
It has a line of D flip flops (called a register) that save a binary input. When you send the data, a series of pistons extend, one after the other, putting blocks in the correct position to allow data from the registers to pass through. (this is how the pulses are made, I guess you could call it a decoder) The other device uses a similar method to read the information and convert it back to binary. On this side I only have a series of RS NOR latches, they're only there for testing purposes.
To you, there is no point in building this. Just like, for me, there is no point in building a mob grinder, castle, or even a house. There is no true objective to Minecraft. The point of the game is whatever you decide it should be. To me, the point of the game is to push the limits of redstone and see if it can accomplish what has been done in the PC version.
Okaaaaay. So perhaps you could explain it a bit more noobish so someone like me can understand it. There's a few terms I'm seriously not familiar with.
.....and no. I'm not trying to be smart or sarcastic in any way. I mean I can make very basic red stone things but this is way beyond me.
That's what I was attempting to do, but it's kind of difficult.
NOT gate - This is just an inverter, a torch connected to a block.
From this point, keep in mind that a high signal means the power is on, and is considered a 1. A low signal means the power is off, this is considered a 0.
1 = on
0 = off.
RS NOR latch - The most basic memory cell. It uses two NOT gates to store a 1 or a 0. If you send a signal to a NOT gate that is outputting a 1, it will then toggle. If you activate the other NOT gate it will toggle to the previous state. The RS in RS NOR means "Set" and "Reset" when you activate one NOT gate this is called setting the latch, when you activate the opposing gate, that is called resetting the latch.
D flip flop - This is pretty much a modification of an RS NOR latch. The latch will only change states when an additional input is activated. This extra input is usually called "Cin" which means clock input. Think of it this way: When you draw a picture in MS Paint, it is like sending data to a D flip flop. If you close MS Paint your picture will be gone forever until you draw it again, this is like sending a signal to the D flip flop without activating the clock input. However, if you save the picture, you can view it again whenever you want, same thing with the flip flop, when you activate the clock input, that signal is stored and you can read it whenever you want.
Register - This is just something built to save data, made with D flip flops. When a high signal is stored, it is considered a 1. If a low signal is stored, it is a 0.
Okay so I had to read that twice and do some hunting around for further info, but I think I got the basic idea. Still beyond me though so I will leave it at that.
It's much easier to understand if you look up a design and build one yourself. They're very small and pretty easily to build, might take a minute or less. That's why I like redstone as opposed to programs like LogiSim. With redstone the components are large and it's easy to see exactly what is going on. Watching everything work together to accomplish complex tasks.
Thank you!Thought it was going to be some idiot saying we need computers (not redstone ones) that can connect to the internet..
Well, I actually do support the ComputerCraft mod and I think it would be great to see something like it on MCXBLA. They're great for password locks and things like that. Plus ComputerCraft comes with its own programming language, so they're a lot easier to program. I would still build redstone computers though, it's just fun to me. Oh! And they have different bots, which I think would be fun to program.
Something like ComputerCraft will never come to the 360 anyway. The target audience is too specific and the DLC wouldn't sell well at all. But I can still dream.
Lol, the internet has no screen.. it's a network. This is how the words I'm writing write now are sent from my computer to be stored in a server somewhere. This is how your computer retrieves that information, stores it temporarily, sends it through your GPU (video card) and to your monitor, so you can read it. Like Ted Stevens once said, "It's a series of tubes!"
Forgive me for sounding dumb asking this question but the simple fact is that whilst I haven't used red stone a great deal I don't see the point of something so large, no matter how impressive the build might be.
Nosejobs's explanation may have still been a little too low level.
His design lets him transmit data from point A to point B over a SINGLE redstone wire. Imagine you and I each having our own House on opposite sides of the world. I can transmit a simple message to you. Granted, we could just use Xbox Live's chat of mic feature, but pretent we're limited to in-game stuff. Then it's pretty handy.
There's a lot more to it than that, but that's the basic.
Nosejobs's explanation may have still been a little too low level.
His design lets him transmit data from point A to point B over a SINGLE redstone wire. Imagine you and I each having our own House on opposite sides of the world. I can transmit a simple message to you. Granted, we could just use Xbox Live's chat of mic feature, but pretent we're limited to in-game stuff. Then it's pretty handy.
There's a lot more to it than that, but that's the basic.
^^^ Yes, that. I was explaining more of the "how" than the "what" I tend to do that a lot. I think I defined the technical jargon pretty well. That's just how the register works though, which has nothing to do with transmitting the data. It just holds the information to be sent, whenever necessary.
How it sends data over one line is actually really simple. I would assume redstone devices that read Morse code work in the same fashion. (Saw one once, it was the most amazing thing ever. That's where I got my inspiration for this.) The main difference is there aren't really dots and dashes. There's only one size of pulse (sort of) and they're all read in the same way. Now, if two 1's are sent next to each other, it will look like one long pulse, but it is read as two. The "transmitter" has inputs for binary data, which in this case is just 8 lines of redstone dust. There is a one meter gap in each line with a repeater on the other side. Pistons place blocks here, one after another, for a period of 4 ticks each, they kind of do a wave. There are no gaps between times that the pistons extend, and alternately, they don't overlap each other. This is what turns binary values into a string of 4-tick pulses. The pistons are sending the data over a single line, breaking it up bit by bit. The "receiver" pretty much does the same thing, in the opposite fashion. The main difference is getting the timing right becomes crucial, and a huge pain. Also there has to be at least a 2-tick delay on the repeaters that send the pulses through the piston's blocks on the receiver. Not exactly sure why, I think it may be a bug. Hopefully it won't be a problem, since they fixed redstone related block update bugs in the newest update.
well, it's still all pretty cool. if folks took the time, trying to invent something like this can be very educational. If you want to understand how a bunch of computers can all be hooked up to the same hub and Computer A can talk to Computer C, while Computer's B and D ignore the conversation, this is where it starts.
The mental exercise of how to make that happen in redstone gives one insight into how it really was done. Conversely, this is why Nosejob is able to make it work in MC, he understands how it works in the real world, so can work out an analog solution in MC.
It's funny that he mentions telegraph, because in my first post, I was thinking of mentioning that this an advanced form of that.
For the people who "don't understand", I think it's a good thing to try to wrap your head around this. Not the nuts and bolts of exactly what block does what and where in the design. Just work through the principal involved.
Let's say you and I are 500 blocks apart. We can't see each other, but would like to pass a message from one to the other. We're in creative mode, let's say (or duping. whatever).
The simplest thing for me is a telegraph. It's just me pressing a button in a dot and dash pattern that means something, which puts signal on a wire and gives a click or buzz or lights up a light on your end. In MC, we could simulate that with a lever on my end (because I can leave it in the ON position longer for the dashes) a redstone trail from my lever to a piston on your end. imagine we put the repeaters in place to keep the signal up over distance. Repeaters aren't important to the concept, except as a mechanical requirement in the game.
to send a signal of SOS (because monsters are coming), in Morse code that would be ...---... as 3 dots, 3 dashes, 3 dots. A dot is a quick on/off on the lever, a dash is where I turn it on, wait 2 seconds, turn it off.
at this point, you have to watch the piston, and when it starts moving, write down (with paper) the exact order of how long it was in the up position. You'd see the piston pop up and down three times quick, that's the first S. Then you'd see it pop up and stay up for 2 seconds before it pops down three times. That's the O. Then it's do the quick triple pop-up again for the other S.
That's pretty primitive, and requires you to be watching the piston to know I'm trying to tell you something. If you wanted to tell me something back, we'd need a second redstone line for you to send to me and I receive on it. Or, we'd have to break and rewire the line to my piston and your lever, so you could respond. That requires me know you want to reply.
this is where the advanced ideas come in. How can you record the message I send so it'll be waiting for you when you come to look, rather than having to watch the piston?
How can we use the same redstone line instead of running a second line? Traditionally, for 2 stations, it's been acceptable for there to be a pair of lines. One to send, the other to recieve on.
But once you get to 3 or more systems, you don't want to have to run 2 lines per stations to each. That would just get messy. You want to re-use the same 2 lines so that my station listens to its reciever line and figures out what station is talking and what he's saying. The sending station wants to send out on his sending line, but also make sure he only talks when nobody else is talking. Otherwise, it'll just get messy.
this is where networking comes into play.
The idea of an engineering exercise is to figure out how to create a simple version of the real thing, to better improve your understanding of the real thing. You don't have to "create the internet" to complete the exercise. But figuring out how to do it in MC will give you a better understanding of how it was done in the real world, because you'll be solving some of the same problems.
Keep in mind, the original internet and EtherNet had origions on AlohaNet, which was multiple stations on different islands sharing the same radio frequency in hawaii. The goal was to make it so one station could check to see if anybody else was transmitting, if not, then it would broadcast. The other stations listened, and if the actual target heard the message, it recorded it. The other stations ignored it. This is the same engineering problem.
Being a pedantic smartass, calling this the internet is the same as calling two flip-flops a computer I wouldn't call two simple transceivers with an proprietary protocol the internet (and i think that term confuses too many people here).
I'll have greatest respect for your efforts and redstone awesomeness :> But the "internet" is a cloudy term for a bunch of computers hooked up to each other offering a bunch of services talking over a well-defined protocol suite ... or something like that... no that doesn't really get it,but i think you know very well what the real ""Internet"" is.
Minimum requirements for something you could call the Minecraft internet for me would be at least 3 (!!) nodes connected to each other, having a protocol specificiation which contains addresses and doing some routing (!!), so we need an intermediate router/switch (or maybe just a hub if you do address matching at each host)
Oops, i just realized you had all this in your future work, sorry.
*Starts reading post...*
"Oh hell naw, OH HEEELLL NAW!"
*Reads last line*
"That's right."
Lmao
But, you're right, it's nowhere near internet, which I stated in the OP. I said it was "like system link" which isn't really the case either, it was just to give people an idea of what this would compare to in the real world. It's not even two transceivers, it's one transmitter and one receiver. Point A to point B, point B can't even talk back, only listen. Also, there is no kind of protocol here, there is only one feature in this machine related to protocol, and that's the defined format of the data, which doesn't come close to being considered protocol, especially since this "network" is a one way street. You can't hardly consider something a protocol when there is only one machine to follow the rules... at least, I don't think so. I might not even implement "true" internet in the final version, I'm thinking more along the lines of a LAN since that's all I'll really need. But, I know I'm going to be building many more computers before I ever completely give up Minecraft. So maybe one day I might expand the LAN into a internet-like network of sorts, probably build another router on the opposite side of the map, maybe set up something like information servers in between them that they could access any time they wanted.
The device in this thread is just showcasing the method of transferring data. I thought it was pretty amazing, simple yet ingenious. Never meant for it to be mistaken as the internet, although I can see how someone could take it that way. This is the absolute barest, most basic foundation for my future interpretation of the internet in Minecraft. And it probably won't even truly be the internet, at least not for a good long time.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffAnd just to chime in on the section issue, I prefer this stuff gets posted here as I don't wander off the XBox section.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffI've actually thought about replicating Apollo 11's Guidance Computer. But, most of the components are impossible in Minecraft, as far as I know. The rest of the parts just aren't practical.
The CPU is set up in a very strange way. The ALU is actually very simple and would be easy to build, but the problem is how it receives information. In my CPU's I take the data from the reading bus and wire it to two registers, that can send it through the ALU. In Apollo's computer these registers are set up to output onto the reading bus. If you tried to read from both registers at the same time it would OR the values together, then send it through the ALU. This would be nice in some rare extremely specific scenarios, but most of the time it Would just be slowing things down.
Believe it or not, I'm pretty amateur as a programmer.
If you want a detailed explanation, read the OP. I went over just about every aspect in detail. But, here's a rundown anyway.
It has a line of D flip flops (called a register) that save a binary input. When you send the data, a series of pistons extend, one after the other, putting blocks in the correct position to allow data from the registers to pass through. (this is how the pulses are made, I guess you could call it a decoder) The other device uses a similar method to read the information and convert it back to binary. On this side I only have a series of RS NOR latches, they're only there for testing purposes.
To you, there is no point in building this. Just like, for me, there is no point in building a mob grinder, castle, or even a house. There is no true objective to Minecraft. The point of the game is whatever you decide it should be. To me, the point of the game is to push the limits of redstone and see if it can accomplish what has been done in the PC version.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffThe computer has been done for awhile now.
http://www.minecraft...r-built-on-360/
But no, you're not getting it.
That's what I was attempting to do, but it's kind of difficult.
NOT gate - This is just an inverter, a torch connected to a block.
From this point, keep in mind that a high signal means the power is on, and is considered a 1. A low signal means the power is off, this is considered a 0.
1 = on
0 = off.
RS NOR latch - The most basic memory cell. It uses two NOT gates to store a 1 or a 0. If you send a signal to a NOT gate that is outputting a 1, it will then toggle. If you activate the other NOT gate it will toggle to the previous state. The RS in RS NOR means "Set" and "Reset" when you activate one NOT gate this is called setting the latch, when you activate the opposing gate, that is called resetting the latch.
D flip flop - This is pretty much a modification of an RS NOR latch. The latch will only change states when an additional input is activated. This extra input is usually called "Cin" which means clock input. Think of it this way: When you draw a picture in MS Paint, it is like sending data to a D flip flop. If you close MS Paint your picture will be gone forever until you draw it again, this is like sending a signal to the D flip flop without activating the clock input. However, if you save the picture, you can view it again whenever you want, same thing with the flip flop, when you activate the clock input, that signal is stored and you can read it whenever you want.
Register - This is just something built to save data, made with D flip flops. When a high signal is stored, it is considered a 1. If a low signal is stored, it is a 0.
I think the rest is pretty easy to understand.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffIt's much easier to understand if you look up a design and build one yourself. They're very small and pretty easily to build, might take a minute or less. That's why I like redstone as opposed to programs like LogiSim. With redstone the components are large and it's easy to see exactly what is going on. Watching everything work together to accomplish complex tasks.
Well, I actually do support the ComputerCraft mod and I think it would be great to see something like it on MCXBLA. They're great for password locks and things like that. Plus ComputerCraft comes with its own programming language, so they're a lot easier to program. I would still build redstone computers though, it's just fun to me. Oh! And they have different bots, which I think would be fun to program.
Something like ComputerCraft will never come to the 360 anyway. The target audience is too specific and the DLC wouldn't sell well at all. But I can still dream.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffLol, the internet has no screen.. it's a network. This is how the words I'm writing write now are sent from my computer to be stored in a server somewhere. This is how your computer retrieves that information, stores it temporarily, sends it through your GPU (video card) and to your monitor, so you can read it. Like Ted Stevens once said, "It's a series of tubes!"
Nosejobs's explanation may have still been a little too low level.
His design lets him transmit data from point A to point B over a SINGLE redstone wire. Imagine you and I each having our own House on opposite sides of the world. I can transmit a simple message to you. Granted, we could just use Xbox Live's chat of mic feature, but pretent we're limited to in-game stuff. Then it's pretty handy.
There's a lot more to it than that, but that's the basic.
-
View User Profile
-
View Posts
-
Send Message
Retired Staff^^^ Yes, that. I was explaining more of the "how" than the "what" I tend to do that a lot. I think I defined the technical jargon pretty well. That's just how the register works though, which has nothing to do with transmitting the data. It just holds the information to be sent, whenever necessary.
How it sends data over one line is actually really simple. I would assume redstone devices that read Morse code work in the same fashion. (Saw one once, it was the most amazing thing ever. That's where I got my inspiration for this.) The main difference is there aren't really dots and dashes. There's only one size of pulse (sort of) and they're all read in the same way. Now, if two 1's are sent next to each other, it will look like one long pulse, but it is read as two. The "transmitter" has inputs for binary data, which in this case is just 8 lines of redstone dust. There is a one meter gap in each line with a repeater on the other side. Pistons place blocks here, one after another, for a period of 4 ticks each, they kind of do a wave. There are no gaps between times that the pistons extend, and alternately, they don't overlap each other. This is what turns binary values into a string of 4-tick pulses. The pistons are sending the data over a single line, breaking it up bit by bit. The "receiver" pretty much does the same thing, in the opposite fashion. The main difference is getting the timing right becomes crucial, and a huge pain. Also there has to be at least a 2-tick delay on the repeaters that send the pulses through the piston's blocks on the receiver. Not exactly sure why, I think it may be a bug. Hopefully it won't be a problem, since they fixed redstone related block update bugs in the newest update.
The mental exercise of how to make that happen in redstone gives one insight into how it really was done. Conversely, this is why Nosejob is able to make it work in MC, he understands how it works in the real world, so can work out an analog solution in MC.
It's funny that he mentions telegraph, because in my first post, I was thinking of mentioning that this an advanced form of that.
For the people who "don't understand", I think it's a good thing to try to wrap your head around this. Not the nuts and bolts of exactly what block does what and where in the design. Just work through the principal involved.
Let's say you and I are 500 blocks apart. We can't see each other, but would like to pass a message from one to the other. We're in creative mode, let's say (or duping. whatever).
The simplest thing for me is a telegraph. It's just me pressing a button in a dot and dash pattern that means something, which puts signal on a wire and gives a click or buzz or lights up a light on your end. In MC, we could simulate that with a lever on my end (because I can leave it in the ON position longer for the dashes) a redstone trail from my lever to a piston on your end. imagine we put the repeaters in place to keep the signal up over distance. Repeaters aren't important to the concept, except as a mechanical requirement in the game.
to send a signal of SOS (because monsters are coming), in Morse code that would be ...---... as 3 dots, 3 dashes, 3 dots. A dot is a quick on/off on the lever, a dash is where I turn it on, wait 2 seconds, turn it off.
at this point, you have to watch the piston, and when it starts moving, write down (with paper) the exact order of how long it was in the up position. You'd see the piston pop up and down three times quick, that's the first S. Then you'd see it pop up and stay up for 2 seconds before it pops down three times. That's the O. Then it's do the quick triple pop-up again for the other S.
That's pretty primitive, and requires you to be watching the piston to know I'm trying to tell you something. If you wanted to tell me something back, we'd need a second redstone line for you to send to me and I receive on it. Or, we'd have to break and rewire the line to my piston and your lever, so you could respond. That requires me know you want to reply.
this is where the advanced ideas come in. How can you record the message I send so it'll be waiting for you when you come to look, rather than having to watch the piston?
How can we use the same redstone line instead of running a second line? Traditionally, for 2 stations, it's been acceptable for there to be a pair of lines. One to send, the other to recieve on.
But once you get to 3 or more systems, you don't want to have to run 2 lines per stations to each. That would just get messy. You want to re-use the same 2 lines so that my station listens to its reciever line and figures out what station is talking and what he's saying. The sending station wants to send out on his sending line, but also make sure he only talks when nobody else is talking. Otherwise, it'll just get messy.
this is where networking comes into play.
The idea of an engineering exercise is to figure out how to create a simple version of the real thing, to better improve your understanding of the real thing. You don't have to "create the internet" to complete the exercise. But figuring out how to do it in MC will give you a better understanding of how it was done in the real world, because you'll be solving some of the same problems.
Keep in mind, the original internet and EtherNet had origions on AlohaNet, which was multiple stations on different islands sharing the same radio frequency in hawaii. The goal was to make it so one station could check to see if anybody else was transmitting, if not, then it would broadcast. The other stations listened, and if the actual target heard the message, it recorded it. The other stations ignored it. This is the same engineering problem.
-
View User Profile
-
View Posts
-
Send Message
Retired Staff*Starts reading post...*
"Oh hell naw, OH HEEELLL NAW!"
*Reads last line*
"That's right."
Lmao
But, you're right, it's nowhere near internet, which I stated in the OP. I said it was "like system link" which isn't really the case either, it was just to give people an idea of what this would compare to in the real world. It's not even two transceivers, it's one transmitter and one receiver. Point A to point B, point B can't even talk back, only listen. Also, there is no kind of protocol here, there is only one feature in this machine related to protocol, and that's the defined format of the data, which doesn't come close to being considered protocol, especially since this "network" is a one way street. You can't hardly consider something a protocol when there is only one machine to follow the rules... at least, I don't think so. I might not even implement "true" internet in the final version, I'm thinking more along the lines of a LAN since that's all I'll really need. But, I know I'm going to be building many more computers before I ever completely give up Minecraft. So maybe one day I might expand the LAN into a internet-like network of sorts, probably build another router on the opposite side of the map, maybe set up something like information servers in between them that they could access any time they wanted.
The device in this thread is just showcasing the method of transferring data. I thought it was pretty amazing, simple yet ingenious. Never meant for it to be mistaken as the internet, although I can see how someone could take it that way. This is the absolute barest, most basic foundation for my future interpretation of the internet in Minecraft. And it probably won't even truly be the internet,