What do you think? What do you agree/disagree with? Btw, this is the first time I’ve ever made an opinion/rant style video, so please let me know what you think! :) Have a great day!
I understand all of your points. I also think that its cool that mojang is bringing more components that arent useless. (Skulk sensor, im looking at you 😂)
feel like everyone else in the community is doing the rant videos, this ones so much better than that though, actually discussing why it's not ideal for your field of redstone piece by piece
I feel that the reset is the most annoying feature about the copper bulb. The copper bulb will probably be used more in Bedrock for counters as the Java synchronous counter design doesn't work. Without a good way to reset the bulb, designs are very large which is unfortunate. I would have liked if any additional Redstone pulses also toggle the counter, even if the bulb is being powered. The pulse shortening to 0 ticks is a bit of a weird change. I would have preferred if they make the normal bulbs 0 ticks, the exposed bulbs 1 tick and the weathered bulbs 2 ticks. This would give the other blocks more use that just light levels and also appease the general Redstone community. For computational Redstone, I think most people will just switch to these as t-flip-flops as they are easy to build.
I don't really know much about redstone, but it sounds like copper bulbs are a perfect replica of secondary storage. Most of your arguments against copper bulbs are about them being difficult to reset, but I think this actually gives a greater correlation to real life computing. Redstone lamps are volatile (like RAM) and need a signal (power) to stay on but copper bulbs are non-volatile (specifically secondary storage) and something like barrels is read-only memory as you mentioned. Resetting/flushing your redstone storage is the equivalent of turning it off and back on again! Taking this into account, they would all have great uses in computation, it's just that secondary storage happens to not be used as much in redstone projects since if a redstone engineer wanted to save the state they'd probably just save it as a schematic or make a backup of the world
Oooh… drum memory (multi-level piston tape). Early drum memories soved the persistent state problem by erasing the drum after the read head and before the write head, copying the data forward if it didn’t need to be over written.
non volatile memory is great in real life because it can preserve data in the case of a power outage, and that it allows machines to save data without being powered on 24/7. Redstone fortunately don't have this problem. They don't have a power source, so power outage isn't a thing, and it's not like you'll ever need to "turn a redstone machine off to save power". So in minecraft, volatile memory is just as good as non volatile memory, with the added benefit of not being annoying to work on
I think you're heavily underselling just how useful T-flip-flops/inverting bit patterns are, especially when movable. They can also be used as extremely compact XOR, if the inputs don't arrive at the same time (if no signal arrives, they stay OFF, if one signal is ON they are ON, and if both signals are ON in sequence they turn OFF again). I use un-synchronized counters all the time since they are so compact (even more so with copper bulbs) without issues. It should also be possible to use that piston-square trick with moving bulbs to make a super compact buffer/queue/de-serializer, where inputs are saved at on point, read at a later point, and then reset with an observer. I like how they clearly show their state visually as well, I tend to have to put lamps all over my latches to visualize which bits are set, now that is built into the storage block!
I myself find it easier to sacrifice two saved hotbars, because I never needed ten of them, and you can't build on lecterns, so they aren't as compact. But do whatever you find easiest!
this is also a good reminder of how compute shaders work in real life too. for the gpu to have performance, the shader has no state. the cpu sends whatever it needs to the gpu as a parameter, then each pixel computes and spits out the color before moving on to the next step just as quickly. no time for storage, so no time for sending anything back either.
It's not really, but tbf he couldn't have known that if you have a three tick repeater into an observer then a bulb, you can treat them like a redstone lamp. This would be worthless, except that now you can wire displays with observers, which makes matrix displays and dense segmented displays easier to wire
🎉❤🎉❤🎉❤❤ Truly truly i say to you all Jesus is the only one who can save you from eternal death. If you just put all your trust in Him, you will find eternal life. But, you may be ashamed by the World as He was. But don't worry, because the Kingdom of Heaven is at hand, and it's up to you to choose this world or That / Heaven or Hell. I say these things for it is written: "Go therefore and make disciples of all nations, baptizing them in the name of the Father and of the Son and of the Holy Spirit, *teaching them* to observe all that I have commanded you; and behold, I am with you always, even to the end of seasonal". Amen." -Jesus -Matthew 28:19-20 ❤🎉🎉🎉❤🎉❤
9:43 is a Turing complete machine. Increase the size of the feedtape and allow it to reverse and you basically have a full computer. Its not just memory.
I think the problem with all these examples is that you're only using them to try and replace lamps, which wasn't their intended purpose in the first place. Once people find niche uses for them (e.g. HDD storage, programming) it'll become that much more useful for those things
Exactly, they aren’t the same. Redstone lamps are good for short-term storage (memory/ram) & setting values while copper bulbs appear to be good for long-term storage & toggling values. Trying to toggle the value of a lamp is as difficult as setting the value of a copper bulb (I think. I haven’t used copper bulbs, but in theory it should be the same difficulty)
6:50 I can definitely see the Copper Bulb be used for Rom, specifically programmable ROM. Provides a really easy way to change the memory of the device while debugging without having to break or place blocks just by pressing a button.
"Use the right tool for the job." In this case the tool in question is basically a T-flip-flop, so don't try to use it where you need a different logic component. Personally, I will probably only use bulbs where I need a TFF
I understand the point of the video, but I feel like you're somewhat missing the point. You take the bulb, try to replace the lamp in circuits that were designed for lamps and wondering why it's worse. The circuits were originally made for active displays and not toggles, so of course it will be worse. I feel that people just haven't yet discovered the ways that the bulb is better, since it's so new. I like the video, but I'd like if it could show that this is only an opinion considering the things thus far, but the future could show more uses for them when they're discovered
Not just the fact that it has different mechanics and that's is the main reason it's harder to use in existing redstone like they said building with the new block in mind is needed plus like 90% of the actual purpose of the block seems more so for design and ambiance because it's a light source we can control the level of light put off by the block now if they update observers so that they can register the amount of light being put off like actual light not the signal put off measuring in redstone strength but that's probably the only way to actually do that since when it boils down that's what the code to the game is actually doing anyway
i do really like the rotating storage at 9:27, if it was on a piston, you could switch data sets, meaning you could even make a select screen, and if you use your extendable piston logic, you could have a virtually infinite amount of data sets.
2:36 if the user knows the slightest bit about the copper bulb then they know it can only exist in 2 states. Even if they didn't know that, they'd realize it after clicking it once makes it stay on
Right? What about a floor display with buttons on the front? Levers could be placed either way, which is infinitely more confusing than having a button that lights up a lamp. Who the hell would use a toggle light to send a single pulse?
@@eli334-1 Even with levers on walls, it can still get confusing because many people are used to the idea that up is on, and levers are the opposite. Even if someone is used to the way levers work, the person building the circuit could still have inverted the signal to make them work like light switches. There's also nothing preventing a lever from being used as a pulsed input, they're actually better at it than buttons are because buttons give a long signal but lever+observer gives a 1 tick signal.
it's not about Minecraft knowledge, it's about user experience design. Everyone on the computer knows by experience that little things going side to side is a yes or no choice. That's because it follows an unspoken standard you'd notice everywhere, like the settings app on your phone. While both options work fine if the player is focused on the lamp, the lever option is more clear about the purpose, and a button that toggles (unlike normal buttons) is ambiguous.
@@erich_ika And then there are checkboxes. The idea that a button + lamp that stays on is less intuitive than a lever is nonsense. The only possible argument there that isn't garbage is that the button might be harder to see than the lever, except the lever being disconnected from the light actually makes it harder for people to make the connection between the two.
@@SirSpence99 well hold on, no need to get heated. I'm not here to argue, I'm here to argue, just showing a different perspective. Let's put it this way: All I'm saying is that if there's a lever, I know it's a toggle. If there's a button, it might do anything. And this property is valuable.
T latches are actually somewhat popular for real life memory. the advantage is that it reduces the number of i/o lines. SR and gated D each require 2 inputs, T only needs 1. of course that means you now have to read every time you write, and writing is rather slow. so it's only useful if you plan to read a lot more than you write. if you don't have to write fast, why dedicate more wires to writing? main uses i have planned for the bulb are cases where you need a toggle state but the state itself doesn't actually matter (mainly observer tech), and off pulses (also observer stuff). one other nice thing is that bulb -> comparator -> observer makes a very simple monostable. which actually makes me kinda annoyed that observers can detect the little red dot changing. if observers could only detect the lit state, it'd be the ultimate monostable.
Thanks (again) for featuring my build. Now that I watch the full context, I can say more. I'm researching copper bulb as RGB screen and I don't really thing resetting is a problem for copper bulb screen. Well, we can just use observer to observe redstone torch behind them. This is actually not very useful and inefficient because we can just use redstone lamp which is faster and smaller. But it's very useful if you want to make RGB screen using copper bulb. The actual problem is RGB screen only work if it is big enough and you are far enough. So for fellow redstoner who want to research this block as RGB screen, good luck.
Having made one copper bulb computer and working on a second, I have to say that copper bulbs can be used for really interesting data storage and computation systems, it requires a very different non traditional kind of architecture. I used the bulbs to make a really interesting hybrid 16x16 screen with 8x8 inputs, but then in order reset it without command blocks I have to give it much longer input pulses and might need to limit how often the screen updates. I also made a better rippling up/down binary counter, I should probably make that it's own video soon. Lots of really weird trade offs, some of the UI stuff is up to preference but it is disappointing how many things have a clear and final answer.
There's no point in replacing the note blocks with copper bulbs because then you need to add an input like buttons which will then dilute the image anyway. Might as well just use note blocks because those are already player-interactible
@@nichard101 Replacing the note block might not make much sense (just slap a button on a bulb though, it still looks nicer than janky pixels) but you could replace the lamps with bulbs so you don't need to store and repeatedly send the current state, which should make for a more compact screen.
@@GremlinSciencesthat is pretty ironic that his example against copper bulbs could’ve been improved with copper bulbs. One bulb with a button and 3 bulbs that get toggled with the button as well and voila, a readable 2x2 light-up display without constant observer ticks
The pushing mechanic makes me think of old turing machines. Like the simple sequence of 0's and 1's moved back and forth. I wonder if anyone has made it yet
3:00 i think that by using copper bulbs you are signifying to the user that you are using a toggle for reset, you may be able to make it small by just running its output back into itself (if you did that i’m sorry i missed it)
Alternate title to this video " The copper bulb is not the same as the redstone lamp, and that makes me sad." They are not interchangeable. They are 2 very different components.
Ultimately I feel like copper bulbs are never the perfect fit for a lot of computational redstone stuff because they are stateful. The standard in computational redstone is to work with direct values of 1 and 0 to avoid state, and generally to work with copper bulbs you want pulses and observers and stuff. For memory, I'm guessing the copper bulb will overall not be good for making the standard type of memory more compact, but the piston based stuff would be really cool for making a slower but vastly more compact memory (like a hard drive compared with RAM). If reading things sequentially, it probably wouldn't even be slower, given the bulbs would arrive in order. So, perhaps good for large files that are processed sequentially but can be modified? Or could be used to store large amounts of memory that are bulk-loaded into a cache by spinning one full slice of the disk.
@@Takyodor2 i just know you dont for basic gates. one person was like "yeah you can make a tiny xor with these" and its like you *can*, but its a terrible idea, will fail on bad input timing, overall not the right move
@electra_ There are cases where you know two values to be XOR'ed will arrive at different times, though. Copper bulbs aren't an obvious replacement for something existing in all situations, but they are better under some circumstances.
i think youre limiting yourself to using copper bulbs for things that are already in the game instead of thinking of what you could do with copper bulbs that you cant do with the other things.
I agree with your point, but they can be used for one thing: screenshotting a redstone display. You just write the data to a blank copper bulb sheet and it'll stay there.
ram memory with copper bulbs are smaller because the xor is commun at the end , you don't need a xor for each bit , treat it like a destrictive write xored although speed get a little hit because of the write back if the bit doesn't change
Terraria's wiring (its version of redstone) actually works similar to copper bulbs - in the way that power works in pulses so everything gets toggled instead of constant power like redstone does it.
11:50 Incrementing with lamps changes the number from 7 to 15 to 8. 12:01 Incrementing with bulbs changes the number from 7 to 8. I like the bulb version better because it lacks the awkward moment of having a rogue output of 15.
Not sure how plausible it would be to build because of solid lamps, but what if you combined the display at 5:40 with the copper bulb approach, allowing you to press a button on the bulb to get instant feedback as well as pressing directly on the screen, but it doesn't remove one block per screen pixel like the noteblock would?
Maybe due to the input? With noteblocks it's a pulse, but with bulbs, it's a constant output. Maybe the redstone was a little more difficult? But i dont know for sure, it does sound like a good solution though
@@zelioz848 I doubt it, since the only block that can read the playing of a note block to activate redstone signal is an observer, which would react to seeing the block state of a copper bulb change just the same as it would react to a note block. But, depending on how the other 3 lights get powered, one may need to worry about the solid lamp blocks causing the bulb to get powered again, turning it off. But that's but a best guess based on the hunch that it's for some other reason than "I didn't think of it".
Instead of a Xor latch, it's easier if you just use the signal to wipe the cell and then one tick later write the new value. Repeater latches already have a tick of delay for write so it doesn't even change the timings. And the wiping circuit is easy and can be done in 0 ticks now that the bulb has no delay. Just connect the output to the input for one tick, then connect the input for one tick. You can even create a massive memory array and using a timing circuit to wipe one row of memory and then write to only that row, allowing for a single input bus that writes to an entire array as long as you time your inputs to match the clock circuit.
"Because having a lever makes it immediately clear to the user that it is a toggle" How did the user learn to identify what a lever is in minecraft? Won't this familiarity with game objects not apply to the copper-bulb? "Oh look, a copper-bulb ergo a toggle". So no, I don't agree with the statement.
Using T-latches in RAM can be a bit annoying, since you have to read the register before writing to it. But I think it's worthwhile tradeoff if it makes the RAM highly compact, especially if you're using it as a large secondary storage. I can easily see this sort of thing being used to store kilobytes of data. But using T-latches also means that you can do inversions directly in-memory, with no data transfer. You can perform these operations during both read and write. This would allow you to perform some of the ALU logic in memory, and do the rest in a simplified near-memory ALU. You can also do XOR and XNOR in-memory in certain cases.
The whole “levers signify toggles better” thing is very overstated, contextually you can almost always tell if it’s a toggle or not, like if it’s a binary input you can assume it’s a toggle. Plus buttons look better.
"Actually, one of your personal reasons for not using them is very overstated and I can with context tell if something is a toggle therefore you must too; following that my opinion (which as stated, is correct) - which is that buttons look better" If you can't tell what I'm getting at: this is somebody's own opinion about why THEY are not going to use it. Not only does it not really not affect you in the slightest but also also you are telling them your opinion as a counter to theirs because you have a bias to it thinking it's correct, AKA Get a life.
@@hellvet3 It's almost as if Mattbat asked for opinions in the comments. Imagine whining over someone explaining their take in the comments as a response... 🤦
@@hellvet3 yes well you see, the point of the comment section is to tell people your opinion for no fucking reason with very little chance of it ever being seen. (Also mattbat says in the pinned comment that he wants to hear what we agree/disagree with)
Reset lines for the bulbs are super easy and expandable when dealing with feed tapes, and while the circuit isn't super small you can read out thru it.
Very interesting take on these blocks! The 1gt delay was really nice because of the limited ways to make a delay that short without making a difference 4/6gt - 5gt circuit really a shame Microsoft removed it
What if they made a redstone lamp with 16 different states? give it redstone signal of 0 being off, and 15 signal being full brightness. So you could have displays with shading.
You could also use a small bulb tape that cycles as the RAM is supposed to update, so it writes a 1 and pushes it into the read position when it's supposed to write a 1, and just pushes a 0 into the read position when it's supposed to write a 0. If you run this tape vertically, you can stack 4~5 bits vertically on one tape if you wipe the tape right after it gets read and before it gets written, and if you invert the read/write positions then a single vertical loop could handle 8~10 bits. This design would limit the ability to update any single bit on it's own and would require all bits on the tape to update at once, but it should still give a smaller footprint, and each bit could also be made to use its own smaller bulb tape if independent updates are required. EDIT: found a more compact way to write and wipe the bulb data, you can stack up to 14 bits on each leg of the tape without issues on that front, just need a _lot_ more pistons and a good timing circuit.
I needed a non glowstone (non nether) solid light block that looked…well not blue and ugly like the sea lantern. Something logical and preferably with the ability to turn on and off. After years the core game is giving me exactly what my build needed, so I am very happy.
One use I've found for copper bulbs is that you can make a 2 tick downwards vertical infinite one-way or/and gate with them, if you use wallstone. You can use trapdoors to pillarize a tower of walls, and read the change in wall state with an observer. Hook that observer up to a copper bulb and boom, you just turned an observer pulse into an on/off toggle. Could be very useful in reduction operations for more than 8 bits.
Much of your argument could be summarized quite simply with "Lamps do [this job] better", and in your examples, you're right! But this isn't the purpose of copper bulbs. They're not trying (and failing) to be "lamps but better", they're a stateful alternative and a simple T-flip flop. I think your dismissal of the application for memory is disappointing, since it's mostly done on the basis of not being able to transplant bulbs into previous designs 1:1. And for user input? Levers don't intrinsically communicate toggles better. Assuming your user won't understand "lamp stay on = lamp toggle" is nearly insulting.
The very nanosecond I saw the spinning memory setup, my first thought was "somebody is going to make a music box with an actual song scroll now" And I'm already impatient to see that happen.
As someone who deals with UX design frequently, I disagree about the lever feeling more like a toggle. It feels the same. Most toggles online are checkboxes, so just a small button, and everyone intuitively knows how that works.
i also thought about it; if you had 2 sets of copper bulbs, flushed the data to the "buffer", and then flushed the data to the actual screen, then it would automatically store current state and xor everything properly. i'm not much of a redstone person tho, so i don't know if there are hidden problems with that edit: okay i'm stupid, it only works for 2 writes 💀 edit2: you could do that with some "classic" redstone, but then it becomes kinda like reading the copper bulb state, you just have more convienient access to it
my immediate thought with the feed tape memory is I wonder if we could use that to make a CD? Find a way to use various signal strengths to output to noteblocks
The only think i've thought about that wasn't covered here is an "infinite" storage system using 0tick piston extenders to push a byte of data to and from the read/write head, but haha that's way beyond me. Good video! Really insightful.
For the record, the entire debate about whether the copper bulb should be reverted or not just shows how poor the tech community is at providing feedback. The real problem is that we would like a more convenient way to get odd gt delays. The fact that copper bulbs happened to offer this for a couple of weeks is not a good enough reason to hammer this functionality there, especially since it makes it worse for T flip-flops and binary counters, which are the more common use case by far, since a lot of the time some synchronization would be needed. Had this functionality been present in the copper trapdoor instead, people would be arguing about trapdoors now, meaning the feedback is entirely arbitrary and relies on an accident of history. I feel like people cannot think clearly.
i just have a couple things to not: in you video you talk alot about how there annoying to reset where infact there not. if you just want to reset its literally a and gate not xor and if you pair that with a input and you can get a much smaller copper bulb counter/ register or any other thing. also it isnt that hard to make 1 by 1 screens. with the copper bulb its a much better improvement as people before have made hex to 1x1 pixels so with copper bulbs it wouldn't be hard to do the inverse and wit would be even easier. either way whatever works and is better for you i approve of and ill probably forget about them anyway :P
i made read-write memory using copper bulbs, but to solve the issue of not being able to set a 1 or a 0 easily, i just attached a bitwise xor to the start of the unit. so to write a byte to an address it reads the address, does XOR with the value on the main bus, then writes to the address.
I hope your college tuition is free because redstone masters are a different breed that deserves some recognition.Ya'll out here making games within games and color TVs of all things.
Hi. When you design your games in python, why do you use classes? I mean, doesn’t that add more abstraction that you need to resolve back when building it on redstone in the end?
The 1 thing where I found the copper bulb really handy was where I had to triple pulse a crafter, so I used a copper bulb with it's state changing as one of the 3 pulses that come from 1 observer, and the other 2 from another observer looking at the observer pushed in to turn the copper bulb on/off and than being retracted. The thing turned out pretty reliable, and worked really well, the only issue was that it wasn't tileable, as one of the observers hard powered the crafter, meaning it'd cause problems to have more of these right next to one another. They were part of a cirquit to automate mosaic blocks from bamboo input.
mojang wants 0 ticks to activate it because bedrock doesn't support 1 tick delay like it is on java and that's actually fucked up. No actually the whole parity shit is the dumbest thing they set to to.
I have an amazing suggestion for you, before making any contraption on minecraft, try using the digital logic sim by sebastian league to map it out, it really helps!
As a general redstoner, I really like the bulb, and it's really fun to experiment with. What you're saying makes a lot of sense though. It's surprising, because I thought this would be one of the fields where the copper bulb would shine, but you explained very well why it won't. Oh well, maybe in the future people will find uses in this type of redstone too. I remember people being disappointed about the observer when it came out because it seemed useless xD
Yeah I think he drastically underestimated the usefulness of piston feed tape based memory. It can function amazingly as a highly dense storage disk because they don’t need to be powered to store. They’re not a replacement for lamps, they’re their own thing.
“Ooh, (grumble grumble grumble) but levers are clearly On/Off: no confusion… how tf is a user supposed to know when it’s a button” It’s definitely that it’s instantly clear from the fact the button is on a COPPER BULB that it’s a toggle 🙃 [Edit]: (corrected a typo)
I find this very similar to coding. Adding more features doesn’t necessarily mean better code, often in means more complicated and confusing code. The copper block will definitely see use in bit storage, however I don’t see it as a target block 2.0 or any other big game changer.
I may not know too much about redstone, but I will say, this video did such a good job of honestly covering a lot of the strengths and weaknesses of the copper bulb I feel like, obviously you did a great job showing how it's not going to be optimal for your set ups, but it just makes me excited to see what does get made with them! Whether that being interesting use cases that are found with redstone, or just really compact nice setups that can be used in builds!
A possible workaround for knowing the state and being able to reset it is to use droppers to pulse an item, a comparator off it lets you pull both the signal or inversion as outputs and you can pulse all the items to one or the other to reset them all. The feed tapes are cool too because you can encode or read whole bit sets. Small easy counters are nice crafty did one. I like the copper bulbs because it will get more people into computational redstone. With screens though I think any lamp behind swapping stained glass would work best, swapping which copper bulbs are light up behind the glass would allow for standard color display coding where yellow is both the red and green lights and blue is it's own.
Great video! I just came back to Minecraft after 4 years off (and it had nothing to do with the movie trailer just released, oh and I hated it!). One of the new things I found was the copper light bulb, so I needed this explanation. I'm not a hardcore redstoner (yet), but I like building counters to automate my farms and I really want to learn more on electronics, signals and redstone to be able to do greater things like the stuff you and other youtubers like Mumbo Jumbo post. Anyway I love your channel! Take care!
they should add stained glass bulbs so you can have multi color displays not that it's really needed cause it's possible to use pistons and stained glass already but it would be simple to use when building them next to each other making 16 by 16 screens or it could be possible to use lightning rods on copperbulbs to have a red green blue screen
Right tool for the right job. It's not a redstone lantern and shouldn't be treated as one. Like, the whole point is that it does something different. Ignoring it rather than trying to find ways to enhance or augment your current knowledge is just being obstinate.
I like using buttons for my toggles because I can toggle them from multiple locations. I also don't like levers because it's ambiguous whether up or down is "on."
What do you think? What do you agree/disagree with?
Btw, this is the first time I’ve ever made an opinion/rant style video, so please let me know what you think! :)
Have a great day!
I understand all of your points. I also think that its cool that mojang is bringing more components that arent useless. (Skulk sensor, im looking at you 😂)
feel like everyone else in the community is doing the rant videos, this ones so much better than that though, actually discussing why it's not ideal for your field of redstone piece by piece
review every redstone component like an unboxing video now!
Basically this video = my thoughts, but I think it’s a bit more useful in silly small circuits where you just need a t flip flop.
I feel that the reset is the most annoying feature about the copper bulb. The copper bulb will probably be used more in Bedrock for counters as the Java synchronous counter design doesn't work. Without a good way to reset the bulb, designs are very large which is unfortunate. I would have liked if any additional Redstone pulses also toggle the counter, even if the bulb is being powered. The pulse shortening to 0 ticks is a bit of a weird change. I would have preferred if they make the normal bulbs 0 ticks, the exposed bulbs 1 tick and the weathered bulbs 2 ticks. This would give the other blocks more use that just light levels and also appease the general Redstone community.
For computational Redstone, I think most people will just switch to these as t-flip-flops as they are easy to build.
I don't really know much about redstone, but it sounds like copper bulbs are a perfect replica of secondary storage. Most of your arguments against copper bulbs are about them being difficult to reset, but I think this actually gives a greater correlation to real life computing. Redstone lamps are volatile (like RAM) and need a signal (power) to stay on but copper bulbs are non-volatile (specifically secondary storage) and something like barrels is read-only memory as you mentioned. Resetting/flushing your redstone storage is the equivalent of turning it off and back on again! Taking this into account, they would all have great uses in computation, it's just that secondary storage happens to not be used as much in redstone projects since if a redstone engineer wanted to save the state they'd probably just save it as a schematic or make a backup of the world
So copper bulbs are the SSDs of the Redstone world?
Oooh… drum memory (multi-level piston tape). Early drum memories soved the persistent state problem by erasing the drum after the read head and before the write head, copying the data forward if it didn’t need to be over written.
@@lilyofluck371 Considering that HDDs are impossible to make in Minecraft...
non volatile memory is great in real life because it can preserve data in the case of a power outage, and that it allows machines to save data without being powered on 24/7. Redstone fortunately don't have this problem. They don't have a power source, so power outage isn't a thing, and it's not like you'll ever need to "turn a redstone machine off to save power". So in minecraft, volatile memory is just as good as non volatile memory, with the added benefit of not being annoying to work on
thats a fantastic way to put it!!
I think you're heavily underselling just how useful T-flip-flops/inverting bit patterns are, especially when movable. They can also be used as extremely compact XOR, if the inputs don't arrive at the same time (if no signal arrives, they stay OFF, if one signal is ON they are ON, and if both signals are ON in sequence they turn OFF again). I use un-synchronized counters all the time since they are so compact (even more so with copper bulbs) without issues. It should also be possible to use that piston-square trick with moving bulbs to make a super compact buffer/queue/de-serializer, where inputs are saved at on point, read at a later point, and then reset with an observer. I like how they clearly show their state visually as well, I tend to have to put lamps all over my latches to visualize which bits are set, now that is built into the storage block!
instead of using barrels, i use lecterns with 15 pages (it leaves room for other items in a saved hotbar, and can be switched on a whim)
I myself find it easier to sacrifice two saved hotbars, because I never needed ten of them, and you can't build on lecterns, so they aren't as compact.
But do whatever you find easiest!
@@caspermadlener4191 if you shift-right-click on a lectern, you can actually build on one (you cannot place redstone on it, but still)
Lectern are far more laggy but if you replace it by barrel once you finish it will be better.
@@Theo_El_Gato that is a fair point, but i do not notice the lag, as i usually do not use them by the hundreds
There is his redstone tools mod
"I don't want my screen to have state"
That's a great point
this is also a good reminder of how compute shaders work in real life too. for the gpu to have performance, the shader has no state. the cpu sends whatever it needs to the gpu as a parameter, then each pixel computes and spits out the color before moving on to the next step just as quickly. no time for storage, so no time for sending anything back either.
@@Wilker_uwuWell, the GPU _does_ have storage, but you shouldn't be sending it back to the CPU because it's extremely time inefficient and laggy
It's not really, but tbf he couldn't have known that if you have a three tick repeater into an observer then a bulb, you can treat them like a redstone lamp. This would be worthless, except that now you can wire displays with observers, which makes matrix displays and dense segmented displays easier to wire
🎉❤🎉❤🎉❤❤
Truly truly i say to you all Jesus is the only one who can save you from eternal death. If you just put all your trust in Him, you will find eternal life. But, you may be ashamed by the World as He was. But don't worry, because the Kingdom of Heaven is at hand, and it's up to you to choose this world or That / Heaven or Hell.
I say these things for it is written:
"Go therefore and make disciples of all nations, baptizing them in the name of the Father and of the Son and of the Holy Spirit, *teaching them* to observe all that I have commanded you; and behold, I am with you always, even to the end of seasonal". Amen."
-Jesus
-Matthew 28:19-20
❤🎉🎉🎉❤🎉❤
9:43 is a Turing complete machine. Increase the size of the feedtape and allow it to reverse and you basically have a full computer. Its not just memory.
it is quite literally a turing machine if made to infinite size lol
@@edwardmighetto7327
But can one do it? How big and can you reverse it?
you still need some form of instruction set to be a real turing machine, but this is basically the tape part of one
@@edwardmighetto7327also it can easily run regular br@1nf✓(k
Composters and cauldrons could already do this
I just think of copper bulbs as a completely different thing than redstone lamps. Both can be used for different purposes and both are still useful.
THANK YOU, FINALLY SOMEONE!!
this is what he says in the video. "these are useful and cool, but not for the things i'm doing"
I think the problem with all these examples is that you're only using them to try and replace lamps, which wasn't their intended purpose in the first place. Once people find niche uses for them (e.g. HDD storage, programming) it'll become that much more useful for those things
Exactly, they aren’t the same. Redstone lamps are good for short-term storage (memory/ram) & setting values while copper bulbs appear to be good for long-term storage & toggling values.
Trying to toggle the value of a lamp is as difficult as setting the value of a copper bulb (I think. I haven’t used copper bulbs, but in theory it should be the same difficulty)
6:50 I can definitely see the Copper Bulb be used for Rom, specifically programmable ROM. Provides a really easy way to change the memory of the device while debugging without having to break or place blocks just by pressing a button.
Mattbatt in his video: tbh, it's just that I wont use them that much.
Mattbatt in the title: I will NEVER EVER touch one of these things...
"mattbatt" i like it
But hey, thats just a clickbait. A GA-
@@ibrahimali3192Matthew Batthew
@@sariarosegoldthis is mattbait
@@EchoesFromCorn mathew battirck
suggestion: build "wireless" data transmission by sending a flying machine with copper bulbs storing data and then receiving them at the other end
That's stretching the definition of "wireless" lmao (I love it)!
That's actually so clever
lmao
youtube moment
My guy got hit by the gold experience requiem
"Use the right tool for the job." In this case the tool in question is basically a T-flip-flop, so don't try to use it where you need a different logic component. Personally, I will probably only use bulbs where I need a TFF
me and a friend developed an instant 0 ticking rom feed tape, so I think the copper built would be great for fast r/w memory
before or after the change?
I understand the point of the video, but I feel like you're somewhat missing the point. You take the bulb, try to replace the lamp in circuits that were designed for lamps and wondering why it's worse. The circuits were originally made for active displays and not toggles, so of course it will be worse. I feel that people just haven't yet discovered the ways that the bulb is better, since it's so new. I like the video, but I'd like if it could show that this is only an opinion considering the things thus far, but the future could show more uses for them when they're discovered
It’s still new, think of when it’s as old as lamps
Not just the fact that it has different mechanics and that's is the main reason it's harder to use in existing redstone like they said building with the new block in mind is needed plus like 90% of the actual purpose of the block seems more so for design and ambiance because it's a light source we can control the level of light put off by the block now if they update observers so that they can register the amount of light being put off like actual light not the signal put off measuring in redstone strength but that's probably the only way to actually do that since when it boils down that's what the code to the game is actually doing anyway
i do really like the rotating storage at 9:27, if it was on a piston, you could switch data sets, meaning you could even make a select screen, and if you use your extendable piston logic, you could have a virtually infinite amount of data sets.
Thats pretty much how hdds work irl!
2:36 if the user knows the slightest bit about the copper bulb then they know it can only exist in 2 states. Even if they didn't know that, they'd realize it after clicking it once makes it stay on
Right? What about a floor display with buttons on the front? Levers could be placed either way, which is infinitely more confusing than having a button that lights up a lamp. Who the hell would use a toggle light to send a single pulse?
@@eli334-1 Even with levers on walls, it can still get confusing because many people are used to the idea that up is on, and levers are the opposite. Even if someone is used to the way levers work, the person building the circuit could still have inverted the signal to make them work like light switches.
There's also nothing preventing a lever from being used as a pulsed input, they're actually better at it than buttons are because buttons give a long signal but lever+observer gives a 1 tick signal.
it's not about Minecraft knowledge, it's about user experience design. Everyone on the computer knows by experience that little things going side to side is a yes or no choice. That's because it follows an unspoken standard you'd notice everywhere, like the settings app on your phone.
While both options work fine if the player is focused on the lamp, the lever option is more clear about the purpose, and a button that toggles (unlike normal buttons) is ambiguous.
@@erich_ika And then there are checkboxes.
The idea that a button + lamp that stays on is less intuitive than a lever is nonsense. The only possible argument there that isn't garbage is that the button might be harder to see than the lever, except the lever being disconnected from the light actually makes it harder for people to make the connection between the two.
@@SirSpence99 well hold on, no need to get heated. I'm not here to argue, I'm here to argue, just showing a different perspective.
Let's put it this way: All I'm saying is that if there's a lever, I know it's a toggle. If there's a button, it might do anything. And this property is valuable.
9:51 drum memory was one of the older methods of storage as was magnetic tape so this might actually be pretty useful .
T latches are actually somewhat popular for real life memory. the advantage is that it reduces the number of i/o lines. SR and gated D each require 2 inputs, T only needs 1. of course that means you now have to read every time you write, and writing is rather slow. so it's only useful if you plan to read a lot more than you write. if you don't have to write fast, why dedicate more wires to writing?
main uses i have planned for the bulb are cases where you need a toggle state but the state itself doesn't actually matter (mainly observer tech), and off pulses (also observer stuff).
one other nice thing is that bulb -> comparator -> observer makes a very simple monostable. which actually makes me kinda annoyed that observers can detect the little red dot changing. if observers could only detect the lit state, it'd be the ultimate monostable.
Thanks (again) for featuring my build. Now that I watch the full context, I can say more. I'm researching copper bulb as RGB screen and I don't really thing resetting is a problem for copper bulb screen. Well, we can just use observer to observe redstone torch behind them. This is actually not very useful and inefficient because we can just use redstone lamp which is faster and smaller. But it's very useful if you want to make RGB screen using copper bulb.
The actual problem is RGB screen only work if it is big enough and you are far enough. So for fellow redstoner who want to research this block as RGB screen, good luck.
Having made one copper bulb computer and working on a second, I have to say that copper bulbs can be used for really interesting data storage and computation systems, it requires a very different non traditional kind of architecture. I used the bulbs to make a really interesting hybrid 16x16 screen with 8x8 inputs, but then in order reset it without command blocks I have to give it much longer input pulses and might need to limit how often the screen updates. I also made a better rippling up/down binary counter, I should probably make that it's own video soon.
Lots of really weird trade offs, some of the UI stuff is up to preference but it is disappointing how many things have a clear and final answer.
5:39 I immediately asked myself, why wouldn't you just use a copper bulb in this design to make it look better?
There's no point in replacing the note blocks with copper bulbs because then you need to add an input like buttons which will then dilute the image anyway. Might as well just use note blocks because those are already player-interactible
@@nichard101 Replacing the note block might not make much sense (just slap a button on a bulb though, it still looks nicer than janky pixels) but you could replace the lamps with bulbs so you don't need to store and repeatedly send the current state, which should make for a more compact screen.
@@GremlinSciencesthat is pretty ironic that his example against copper bulbs could’ve been improved with copper bulbs.
One bulb with a button and 3 bulbs that get toggled with the button as well and voila, a readable 2x2 light-up display without constant observer ticks
Actually what about reading(/write) a sequence of data? Because a copper bulb can be pushed it might be better.
The pushing mechanic makes me think of old turing machines. Like the simple sequence of 0's and 1's moved back and forth. I wonder if anyone has made it yet
@zelioz848 several people in CraftyMasterman's discord have made copper-based Turing machines, and my latest video is a demo of my own design.
"Wow, we really like this thing you added! Thanks!"
"No."
"What?"
"It's gone."
mojang doesn't fail to disappoint
3:00 i think that by using copper bulbs you are signifying to the user that you are using a toggle
for reset, you may be able to make it small by just running its output back into itself (if you did that i’m sorry i missed it)
Alternate title to this video " The copper bulb is not the same as the redstone lamp, and that makes me sad." They are not interchangeable. They are 2 very different components.
Ultimately I feel like copper bulbs are never the perfect fit for a lot of computational redstone stuff because they are stateful. The standard in computational redstone is to work with direct values of 1 and 0 to avoid state, and generally to work with copper bulbs you want pulses and observers and stuff.
For memory, I'm guessing the copper bulb will overall not be good for making the standard type of memory more compact, but the piston based stuff would be really cool for making a slower but vastly more compact memory (like a hard drive compared with RAM). If reading things sequentially, it probably wouldn't even be slower, given the bulbs would arrive in order. So, perhaps good for large files that are processed sequentially but can be modified? Or could be used to store large amounts of memory that are bulk-loaded into a cache by spinning one full slice of the disk.
There are plenty of cases where you want state, even if it isn't the majority of cases, I see them coming in very handy in those special cases!
@@Takyodor2 i just know you dont for basic gates. one person was like "yeah you can make a tiny xor with these" and its like you *can*, but its a terrible idea, will fail on bad input timing, overall not the right move
@electra_ There are cases where you know two values to be XOR'ed will arrive at different times, though. Copper bulbs aren't an obvious replacement for something existing in all situations, but they are better under some circumstances.
you know the copper bulb is bad when they nerfed it AND it's not even that great as a t flip flop
see last chapter of the video?
why isnt it a good t flip flop, i thought it was great as it made t flip flops 1 block
@@MenaVoldey you still need a comparator output lol. and you could already make tiny tffs with a comp reading a dispenser with powder snow
I feel ya dude. :(
CRAFTY PLEASE JUST WATCH BEFORE YOU SPEAK YOU SAY THIS EVERYWHERE, UNDER EVERY DEVS TWEET, AND UA-cam?
i think youre limiting yourself to using copper bulbs for things that are already in the game instead of thinking of what you could do with copper bulbs that you cant do with the other things.
I know I made an 3x5x3 Full added with them and observers
he's in denial
I agree with your point, but they can be used for one thing: screenshotting a redstone display. You just write the data to a blank copper bulb sheet and it'll stay there.
ram memory with copper bulbs are smaller because the xor is commun at the end , you don't need a xor for each bit , treat it like a destrictive write xored although speed get a little hit because of the write back if the bit doesn't change
Terraria's wiring (its version of redstone) actually works similar to copper bulbs - in the way that power works in pulses so everything gets toggled instead of constant power like redstone does it.
My first thought when the copper bulbs came out was a read-write memory tape haha
9:50 makes it possible to have video storage without massive data modules - and I'm sooo going to test this
Friendly reminder that Kingbdogz said on Twitter that the 1gt tick delay was intentional from the very beginning
"1gt tick" is redundant
11:50 Incrementing with lamps changes the number from 7 to 15 to 8.
12:01 Incrementing with bulbs changes the number from 7 to 8.
I like the bulb version better because it lacks the awkward moment of having a rogue output of 15.
I feel like copper bulb feedtapes are just begging to be made into a Turing machine
Hold up. If you can move copper bulbs without them clearing what is stored, could you make something like a magnetic tape that can store info.
Not sure how plausible it would be to build because of solid lamps, but what if you combined the display at 5:40 with the copper bulb approach, allowing you to press a button on the bulb to get instant feedback as well as pressing directly on the screen, but it doesn't remove one block per screen pixel like the noteblock would?
Maybe due to the input? With noteblocks it's a pulse, but with bulbs, it's a constant output. Maybe the redstone was a little more difficult? But i dont know for sure, it does sound like a good solution though
@@zelioz848 I doubt it, since the only block that can read the playing of a note block to activate redstone signal is an observer, which would react to seeing the block state of a copper bulb change just the same as it would react to a note block. But, depending on how the other 3 lights get powered, one may need to worry about the solid lamp blocks causing the bulb to get powered again, turning it off. But that's but a best guess based on the hunch that it's for some other reason than "I didn't think of it".
could maybe do the 1x1 pixel version with normal lamps by using skulk sensors at max distance from the buttons
Instead of a Xor latch, it's easier if you just use the signal to wipe the cell and then one tick later write the new value. Repeater latches already have a tick of delay for write so it doesn't even change the timings. And the wiping circuit is easy and can be done in 0 ticks now that the bulb has no delay. Just connect the output to the input for one tick, then connect the input for one tick. You can even create a massive memory array and using a timing circuit to wipe one row of memory and then write to only that row, allowing for a single input bus that writes to an entire array as long as you time your inputs to match the clock circuit.
"Because having a lever makes it immediately clear to the user that it is a toggle" How did the user learn to identify what a lever is in minecraft? Won't this familiarity with game objects not apply to the copper-bulb? "Oh look, a copper-bulb ergo a toggle".
So no, I don't agree with the statement.
Using T-latches in RAM can be a bit annoying, since you have to read the register before writing to it. But I think it's worthwhile tradeoff if it makes the RAM highly compact, especially if you're using it as a large secondary storage. I can easily see this sort of thing being used to store kilobytes of data.
But using T-latches also means that you can do inversions directly in-memory, with no data transfer. You can perform these operations during both read and write. This would allow you to perform some of the ALU logic in memory, and do the rest in a simplified near-memory ALU. You can also do XOR and XNOR in-memory in certain cases.
The whole “levers signify toggles better” thing is very overstated, contextually you can almost always tell if it’s a toggle or not, like if it’s a binary input you can assume it’s a toggle. Plus buttons look better.
"Actually, one of your personal reasons for not using them is very overstated and I can with context tell if something is a toggle therefore you must too; following that my opinion (which as stated, is correct) - which is that buttons look better"
If you can't tell what I'm getting at: this is somebody's own opinion about why THEY are not going to use it. Not only does it not really not affect you in the slightest but also also you are telling them your opinion as a counter to theirs because you have a bias to it thinking it's correct, AKA Get a life.
@@hellvet3 It's almost as if Mattbat asked for opinions in the comments. Imagine whining over someone explaining their take in the comments as a response... 🤦
@@hellvet3 yes well you see, the point of the comment section is to tell people your opinion for no fucking reason with very little chance of it ever being seen. (Also mattbat says in the pinned comment that he wants to hear what we agree/disagree with)
Reset lines for the bulbs are super easy and expandable when dealing with feed tapes, and while the circuit isn't super small you can read out thru it.
Very interesting take on these blocks!
The 1gt delay was really nice because of the limited ways to make a delay that short without making a difference 4/6gt - 5gt circuit
really a shame Microsoft removed it
Copper bulbs can be used for:
-Ram
-XOR Gate
-displays
and more
What if they made a redstone lamp with 16 different states? give it redstone signal of 0 being off, and 15 signal being full brightness. So you could have displays with shading.
You could also use a small bulb tape that cycles as the RAM is supposed to update, so it writes a 1 and pushes it into the read position when it's supposed to write a 1, and just pushes a 0 into the read position when it's supposed to write a 0. If you run this tape vertically, you can stack 4~5 bits vertically on one tape if you wipe the tape right after it gets read and before it gets written, and if you invert the read/write positions then a single vertical loop could handle 8~10 bits. This design would limit the ability to update any single bit on it's own and would require all bits on the tape to update at once, but it should still give a smaller footprint, and each bit could also be made to use its own smaller bulb tape if independent updates are required.
EDIT: found a more compact way to write and wipe the bulb data, you can stack up to 14 bits on each leg of the tape without issues on that front, just need a _lot_ more pistons and a good timing circuit.
TLDR: Copper bulbs are not redstone lamps, and copper bulbs don't behave like redstone lamps.
I needed a non glowstone (non nether) solid light block that looked…well not blue and ugly like the sea lantern. Something logical and preferably with the ability to turn on and off.
After years the core game is giving me exactly what my build needed, so I am very happy.
woke up literally 2 minutes ago and i’m blessed with a mattbat video 🙏
*i'm in bed next to you*
same
One use I've found for copper bulbs is that you can make a 2 tick downwards vertical infinite one-way or/and gate with them, if you use wallstone. You can use trapdoors to pillarize a tower of walls, and read the change in wall state with an observer. Hook that observer up to a copper bulb and boom, you just turned an observer pulse into an on/off toggle. Could be very useful in reduction operations for more than 8 bits.
Much of your argument could be summarized quite simply with "Lamps do [this job] better", and in your examples, you're right! But this isn't the purpose of copper bulbs. They're not trying (and failing) to be "lamps but better", they're a stateful alternative and a simple T-flip flop.
I think your dismissal of the application for memory is disappointing, since it's mostly done on the basis of not being able to transplant bulbs into previous designs 1:1.
And for user input? Levers don't intrinsically communicate toggles better. Assuming your user won't understand "lamp stay on = lamp toggle" is nearly insulting.
Wow, this is pretty much exactly my reaction, I second ^
The very nanosecond I saw the spinning memory setup, my first thought was "somebody is going to make a music box with an actual song scroll now"
And I'm already impatient to see that happen.
This video was made in really bad faith and although I enjoy this channel I can’t help but to feel angry at it
As someone who deals with UX design frequently, I disagree about the lever feeling more like a toggle. It feels the same. Most toggles online are checkboxes, so just a small button, and everyone intuitively knows how that works.
bro just made a cd in minecraft
levers are more intuitive than buttons only for the first time though, after every time you see a button on the copper bulbs you'll be aware
5:36
Would be cool to have connectable lamps and copper bulbs
The thing I think you need to realize is that the copper bulb isn’t a redstone lamp. So don’t expect them to replace them.
Can we make this the top comment for no reason?
Lets do it
ok
So far, yes
Yes💪🏻💪🏻
yas
Genuinely even if it's completely impractical, the visual look of a spinning memory disk is so cool.
For the reset problem, couldn't you store the data on another array of copper bulbs, and then read from that onto the original screen?
i also thought about it; if you had 2 sets of copper bulbs, flushed the data to the "buffer", and then flushed the data to the actual screen, then it would automatically store current state and xor everything properly. i'm not much of a redstone person tho, so i don't know if there are hidden problems with that
edit: okay i'm stupid, it only works for 2 writes 💀
edit2: you could do that with some "classic" redstone, but then it becomes kinda like reading the copper bulb state, you just have more convienient access to it
Now i can remember how to make a xor gate
🟧🟥
🔼🔼
🟧=copper bulb
🔼=observer
🟥=solid block
It works in any position
The spinning memory can be used to make brainfuck in minecraft
Done a month ago, it was a fun project for my first redstone computer
@@inequalmeasure3103 Really nice !
my immediate thought with the feed tape memory is I wonder if we could use that to make a CD? Find a way to use various signal strengths to output to noteblocks
Hello matt :D I love ur vids!
“Why I’ll never Use Copper Bulbs”
But i will use copper bulbs for the thumbnail
It would be cool if we had colored red stone bulb
The only think i've thought about that wasn't covered here is an "infinite" storage system using 0tick piston extenders to push a byte of data to and from the read/write head, but haha that's way beyond me. Good video! Really insightful.
Levers don't work on copper bulbs? Some of your arguments against copper bulbs seem to apply more to levers vs buttons.
There's no reason to use a lever on a copper bulb instead of a button, and would make it more annoying since you would have to flip it twice.
The spinning RW memory thing is basicaly a hard drive.
you could probably make a sd card or flash disk or cd that way lol and you can also have multiple saves, but who actually needs that
If it's possible, someone will want one...
Copper bulb is a awesome decoration.
copper bulb can be useful is some areas
A spinning read/write design is basically a rudimentary type of disk. We already are getting disk writing capabilities inside of minecraft
I know nothing about red stone but this item does look pretty cool, just gonna need to watch you to figure out wtf it does 😂😂
For the record, the entire debate about whether the copper bulb should be reverted or not just shows how poor the tech community is at providing feedback. The real problem is that we would like a more convenient way to get odd gt delays. The fact that copper bulbs happened to offer this for a couple of weeks is not a good enough reason to hammer this functionality there, especially since it makes it worse for T flip-flops and binary counters, which are the more common use case by far, since a lot of the time some synchronization would be needed. Had this functionality been present in the copper trapdoor instead, people would be arguing about trapdoors now, meaning the feedback is entirely arbitrary and relies on an accident of history. I feel like people cannot think clearly.
i just have a couple things to not: in you video you talk alot about how there annoying to reset where infact there not. if you just want to reset its literally a and gate not xor and if you pair that with a input and you can get a much smaller copper bulb counter/ register or any other thing. also it isnt that hard to make 1 by 1 screens. with the copper bulb its a much better improvement as people before have made hex to 1x1 pixels so with copper bulbs it wouldn't be hard to do the inverse and wit would be even easier. either way whatever works and is better for you i approve of and ill probably forget about them anyway :P
i made read-write memory using copper bulbs, but to solve the issue of not being able to set a 1 or a 0 easily, i just attached a bitwise xor to the start of the unit. so to write a byte to an address it reads the address, does XOR with the value on the main bus, then writes to the address.
it's called a cop flop
I hope your college tuition is free because redstone masters are a different breed that deserves some recognition.Ya'll out here making games within games and color TVs of all things.
Hi. When you design your games in python, why do you use classes? I mean, doesn’t that add more abstraction that you need to resolve back when building it on redstone in the end?
He's not replicating python with redstone, he's repicating redstone with python.
The 1 thing where I found the copper bulb really handy was where I had to triple pulse a crafter, so I used a copper bulb with it's state changing as one of the 3 pulses that come from 1 observer, and the other 2 from another observer looking at the observer pushed in to turn the copper bulb on/off and than being retracted. The thing turned out pretty reliable, and worked really well, the only issue was that it wasn't tileable, as one of the observers hard powered the crafter, meaning it'd cause problems to have more of these right next to one another. They were part of a cirquit to automate mosaic blocks from bamboo input.
mojang wants 0 ticks to activate it because bedrock doesn't support 1 tick delay like it is on java and that's actually fucked up. No actually the whole parity shit is the dumbest thing they set to to.
I have an amazing suggestion for you, before making any contraption on minecraft, try using the digital logic sim by sebastian league to map it out, it really helps!
9:50 brainfuck tape in minecraft?
Done, it was a fun project for my first redstone computer
As a general redstoner, I really like the bulb, and it's really fun to experiment with. What you're saying makes a lot of sense though. It's surprising, because I thought this would be one of the fields where the copper bulb would shine, but you explained very well why it won't. Oh well, maybe in the future people will find uses in this type of redstone too. I remember people being disappointed about the observer when it came out because it seemed useless xD
Yeah I think he drastically underestimated the usefulness of piston feed tape based memory. It can function amazingly as a highly dense storage disk because they don’t need to be powered to store. They’re not a replacement for lamps, they’re their own thing.
10/10 for explaining why you gave the video that title in the first 30 seconds. Bravo.
“Ooh, (grumble grumble grumble) but levers are clearly On/Off: no confusion… how tf is a user supposed to know when it’s a button”
It’s definitely that it’s instantly clear from the fact the button is on a COPPER BULB that it’s a toggle 🙃
[Edit]: (corrected a typo)
I find this very similar to coding. Adding more features doesn’t necessarily mean better code, often in means more complicated and confusing code. The copper block will definitely see use in bit storage, however I don’t see it as a target block 2.0 or any other big game changer.
I may not know too much about redstone, but I will say, this video did such a good job of honestly covering a lot of the strengths and weaknesses of the copper bulb I feel like, obviously you did a great job showing how it's not going to be optimal for your set ups, but it just makes me excited to see what does get made with them! Whether that being interesting use cases that are found with redstone, or just really compact nice setups that can be used in builds!
> It uses dust and it's easier to understand
Dustless redstoners screaming rn
A possible workaround for knowing the state and being able to reset it is to use droppers to pulse an item, a comparator off it lets you pull both the signal or inversion as outputs and you can pulse all the items to one or the other to reset them all. The feed tapes are cool too because you can encode or read whole bit sets. Small easy counters are nice crafty did one. I like the copper bulbs because it will get more people into computational redstone. With screens though I think any lamp behind swapping stained glass would work best, swapping which copper bulbs are light up behind the glass would allow for standard color display coding where yellow is both the red and green lights and blue is it's own.
Great video! I just came back to Minecraft after 4 years off (and it had nothing to do with the movie trailer just released, oh and I hated it!). One of the new things I found was the copper light bulb, so I needed this explanation. I'm not a hardcore redstoner (yet), but I like building counters to automate my farms and I really want to learn more on electronics, signals and redstone to be able to do greater things like the stuff you and other youtubers like Mumbo Jumbo post.
Anyway I love your channel! Take care!
they should add stained glass bulbs so you can have multi color displays not that it's really needed cause it's possible to use pistons and stained glass already but it would be simple to use when building them next to each other making 16 by 16 screens or it could be possible to use lightning rods on copperbulbs to have a red green blue screen
so, its not that you wont be using them, its that you wont use them in place of features that are already implemented
Right tool for the right job. It's not a redstone lantern and shouldn't be treated as one.
Like, the whole point is that it does something different. Ignoring it rather than trying to find ways to enhance or augment your current knowledge is just being obstinate.
I like using buttons for my toggles because I can toggle them from multiple locations. I also don't like levers because it's ambiguous whether up or down is "on."