Something I probably should have mentioned in the video is that it is not all redstone, and the display (so choosing what image is displayed) is made with command blocks. Everything else, (apart from the spinning fan blades and the message display) is redstone tho (so all keyboard signal encoding/decoding, the on/off button, all of the computer's lighting, the wifi signals, etc are redstone). All of that to say, the screen is using command blocks to make it update the image faster.
Most of the long range connections in the computer (Such as from the keyboard to the screen and from the screen to the message display) use "beep codes" as I remember I called it at the time, where one side, for example the keyboard, will send 1, and the delay in ticks between the start and end of the pulse determines the character. It has been a while since I made this computer, but I belive a delay of 9 ticks is an A, 10, ticks is a B, and so on. (The special characters are after Z). The reason A starts at 9 ticks is a bit complicated, but the simple answer is that the decoder needs 8 ticks so start measuring the length of the pulse, so from the decoders point of view, a pulse of 9 ticks will show up as a 1 tick pulse on the decoder, and any pulse shorter than 9 ticks with no show up at all. Essentially the same thing happens with the wireless signals, except that this time, it is sent as 2 pulses with variable delay between those 2 pulses that go into a T flip flop since I used skulk sensors for the wireless signals and you can't vary the length of the pulse from a skulk sensor. I might very well turn this into a video seeing how much text in took me to explain this all. Thanks for the question!
I was actually going to make an entire video about that, but decided it would be very interesting, but here is a shortened explanation: 1. This is redstone. Even if I have killaura, tracers, or aimbot on, it doesn't make my redstone not legit, since it doesn't do anything. 2. The reason I actually use it is for certain features in Wurst like fullbright, freecam, zoom, noWeather, fastPlace, and fastBreak. 3. I could recreate all of these features using separate mods, but it is more convenient to have them all in one mod.
This is redstone. Even if I have killaura, tracers, or aimbot on, it doesn't make my redstone not legit, since it doesn't do anything related to redstone. The reason I actually use it is for certain features in Wurst like fullbright, freecam, zoom, noWeather, fastPlace, and fastBreak, which make building massive things like this way easier.
How, this looks so good
Something I probably should have mentioned in the video is that it is not all redstone, and the display (so choosing what image is displayed) is made with command blocks. Everything else, (apart from the spinning fan blades and the message display) is redstone tho (so all keyboard signal encoding/decoding, the on/off button, all of the computer's lighting, the wifi signals, etc are redstone). All of that to say, the screen is using command blocks to make it update the image faster.
@@Daxis1make a fully redstone computer
@@aracno211 ;)
Goodjob!!
Thanks!
Can I ask how many FLOPS it has? How many bytes of RAM does it have?
Cool i subed
Nice
Thank you!
@@Daxis1 ☺
how did you made the wireless connection? i want to make it too make a tutorial about it
Most of the long range connections in the computer (Such as from the keyboard to the screen and from the screen to the message display) use "beep codes" as I remember I called it at the time, where one side, for example the keyboard, will send 1, and the delay in ticks between the start and end of the pulse determines the character. It has been a while since I made this computer, but I belive a delay of 9 ticks is an A, 10, ticks is a B, and so on. (The special characters are after Z). The reason A starts at 9 ticks is a bit complicated, but the simple answer is that the decoder needs 8 ticks so start measuring the length of the pulse, so from the decoders point of view, a pulse of 9 ticks will show up as a 1 tick pulse on the decoder, and any pulse shorter than 9 ticks with no show up at all. Essentially the same thing happens with the wireless signals, except that this time, it is sent as 2 pulses with variable delay between those 2 pulses that go into a T flip flop since I used skulk sensors for the wireless signals and you can't vary the length of the pulse from a skulk sensor. I might very well turn this into a video seeing how much text in took me to explain this all. Thanks for the question!
@@Daxis1 i didint understand anything from text make a video about it later I SAID "LATER"
How you make 1 by 1 pixel screen
It uses command blocks to get a better response time and resolution.
Why are you using wurst client... u hacker or smth...........
I was actually going to make an entire video about that, but decided it would be very interesting, but here is a shortened explanation:
1. This is redstone. Even if I have killaura, tracers, or aimbot on, it doesn't make my redstone not legit, since it doesn't do anything.
2. The reason I actually use it is for certain features in Wurst like fullbright, freecam, zoom, noWeather, fastPlace, and fastBreak.
3. I could recreate all of these features using separate mods, but it is more convenient to have them all in one mod.
@@Daxis1 fair enough
that doesn't work but it look cool😎
?
hacked client alert
This is redstone. Even if I have killaura, tracers, or aimbot on, it doesn't make my redstone not legit, since it doesn't do anything related to redstone. The reason I actually use it is for certain features in Wurst like fullbright, freecam, zoom, noWeather, fastPlace, and fastBreak, which make building massive things like this way easier.