Firstly I'd just like to make it clear I do not like bud switches at all.
I really don't know how to make you understand why I feel this way. I wish I could. I'm not trying to come across as arrogant or anything like that but something about BUD switches just doesn't feel right to me. At least not in survival singleplayer or multiplayer.
I was disappointed when the BUD switch bug was not removed in the redstone update.
The quote below is from the Minecraft wiki.
The Block Update Detector, or "BUD switch", is a redstone mechanism that exploits bugs and quirks in the game in order to detect changes in nearby blocks. There are many different designs, but they are all based on the same general idea: a redstone circuit is put in a state that should be unstable, but is stable due to some block within not being notified of changes in the circuit that would otherwise affect it. This lazy block then functions as the "sensor". When an adjacent block changes state in some way, it sends a notification to the sensor block and "wakes it up". The circuit then performs some other action and goes back into the sleeping state.
BUD switches are a bug. Bugs in any game are unreliable; and could be/should be removed.
BEFORE YOU ATTACK ME AND SAY "Well this will ruin all my redstone inventions." keep in mind you are defending a bug. And don't forget I'm providing my own solution.
The actual idea - I propose that bud switches be fixed/removed, and in there place create a command for the command block that would /test for blockupdate/redstoneupdate {coordinates of search area here}
For this to work the command block would need to be hooked up to a clock that would cause it to look for changes in the environment. If the command block finds a difference in the environment after one signal that hadn't changed in the previous signal it will send out a signal of its own through a comparator.
Uses -
Obviously it could be used for anything the previous bud switches have been used for. But this would be much more compact as it could search whole areas while previous bud switches would only detect the blocks directly adjacent to them.
Except that comparators perform most of the functions BUD switches used to do, plus more, such as:
Jukeboxes outputting a redstone signal when a disc is inserted; Hypixel used this in his adventure maps using BUD switches, he had the boss drop a disc and have that disc trigger the next sequence of events. Comparators do this, and can even tell the difference between one music disc and another.
Ender portal frames when you place an eye in them; I tried to use this right before the redstone update came out. It's very useful.
Many other useful features
The only thing comparators can't do is determine if a block itself has been placed or removed, which I admit is a disappointing.
Except that comparators perform most of the functions BUD switches used to do, plus more, such as:
Jukeboxes outputting a redstone signal when a disc is inserted; Hypixel used this in his adventure maps using BUD switches, he had the boss drop a disc and have that disc trigger the next sequence of events. Comparators do this, and can even tell the difference between one music disc and another.
Ender portal frames when you place an eye in them; I tried to use this right before the redstone update came out. It's very useful.
Many other useful features
The only thing comparators can't do is determine if a block itself has been placed or removed, which I admit is a disappointing.
I'm not sure if you're supporting my idea or saying that its unnecessary...
Or if people just waste their time making BUD switches at all?
While this suggestion is undoubtedly useful the ability to detect blocks being placed or removed in SURVIVAL is the most important use of BUD switches (as most of the stuff that can be done with BUD switched can be done with worldedit). Your suggestion fails to accommodate that.
No support.
Players were never meant to be able to detect the placing or breaking of blocks in the first place - unless you count seeing someone else do it in person or hear the sounds of a placed or breaking block.
No matter how much people love their BUD switches they are a bug and do not belong in Minecraft at all. Using the command block to replace BUD switches is the only logical explanation.
But there isn't much use to detecting block updates in the first place.
However I think there would be a problem with your idea. Currently to use the /testfor command on a command block you provide a redstone signal and the comparator provides the output according to what the /testfor command was looking for. All of the current arguments check if something is true/how much of something. This "blockupdate" command would be checking for "change" this is currently impossible with the current setup as this would be checking the area specified every tick and comparing it to the area specified in the last tick and this would be getting very laggy unusually fast.
Then explain how a bud switch doesn't create a lot of lag since it is also searching for updates around it?
The bud switch is not a bug. Bugs are extremely unpredictable but the bud is reliable and stable. Plus you can't get command blocks in survival. Please don't suggest things to be removed only to make it creative only. And if you are really concerned with bugs, go to the bug tracker.
So, basically we should remove one of the most useful redstone creations and replace it with a creative-only and super laggy substitute just because you, only you, and you only, do not feel they fit with Minecraft? MAKES SENSE!
The bud switch is not a bug. Bugs are extremely unpredictable but the bud is reliable and stable. Plus you can't get command blocks in survival. Please don't suggest things to be removed only to make it creative only. And if you are really concerned with bugs, go to the bug tracker.
The Minecraft wiki page states that it is a bug.
Plus the main concept of a budswitch is a piston stuck in a powered state or an unpowered state when it should be the exact opposite, which is a bug.
If you don't like BUD switches, no one's forcing you to use them :/
Some people are fine with it being there, some people utilize it. I understand some people wouldn't like it, so just ignore it :l
I think they prove useful in both creative and survival. I've used a couple in my time.
Rollback Post to RevisionRollBack
Much signature. Wow.
:3
To post a comment, please login or register a new account.
I really don't know how to make you understand why I feel this way. I wish I could. I'm not trying to come across as arrogant or anything like that but something about BUD switches just doesn't feel right to me. At least not in survival singleplayer or multiplayer.
I was disappointed when the BUD switch bug was not removed in the redstone update.
The quote below is from the Minecraft wiki.
BUD switches are a bug. Bugs in any game are unreliable; and could be/should be removed.
BEFORE YOU ATTACK ME AND SAY "Well this will ruin all my redstone inventions." keep in mind you are defending a bug. And don't forget I'm providing my own solution.
The actual idea -
I propose that bud switches be fixed/removed, and in there place create a command for the command block that would /test for blockupdate/redstoneupdate {coordinates of search area here}
For this to work the command block would need to be hooked up to a clock that would cause it to look for changes in the environment. If the command block finds a difference in the environment after one signal that hadn't changed in the previous signal it will send out a signal of its own through a comparator.
Uses -
Obviously it could be used for anything the previous bud switches have been used for. But this would be much more compact as it could search whole areas while previous bud switches would only detect the blocks directly adjacent to them.
- Jukeboxes outputting a redstone signal when a disc is inserted; Hypixel used this in his adventure maps using BUD switches, he had the boss drop a disc and have that disc trigger the next sequence of events. Comparators do this, and can even tell the difference between one music disc and another.
- Ender portal frames when you place an eye in them; I tried to use this right before the redstone update came out. It's very useful.
- Many other useful features
The only thing comparators can't do is determine if a block itself has been placed or removed, which I admit is a disappointing.[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
I'm not sure if you're supporting my idea or saying that its unnecessary...
Or if people just waste their time making BUD switches at all?
Players were never meant to be able to detect the placing or breaking of blocks in the first place - unless you count seeing someone else do it in person or hear the sounds of a placed or breaking block.
No matter how much people love their BUD switches they are a bug and do not belong in Minecraft at all. Using the command block to replace BUD switches is the only logical explanation.
But there isn't much use to detecting block updates in the first place.
Then explain how a bud switch doesn't create a lot of lag since it is also searching for updates around it?
The Minecraft wiki page states that it is a bug.
Plus the main concept of a budswitch is a piston stuck in a powered state or an unpowered state when it should be the exact opposite, which is a bug.
Some people are fine with it being there, some people utilize it. I understand some people wouldn't like it, so just ignore it :l
I think they prove useful in both creative and survival. I've used a couple in my time.
:3