I just encountered a serious issue where I was messing around with a command block, hit a wrong button, and was
repeatedly hurled into the void. I manged to stop it (after five minutes of teleporting myself thousands of blocks into the air and guessing on the exact location of the command block to destroy it), but realized a better solution might be to have a game rule command that disables command blocks. Even further, lets say someone has the command /kill @e put into a repeating command block where they wouldn't be able to do what I was able to do, maybe add in a button on the "death menu" to disable it. Just an idea. I could have lost the entire creative world, and I'm 100% certain someone has lost theirs.
This will be really good because as of now you have to shutdown the server, disable command blocks, start the server, find the command block, break it or change it, shutdown the server, enable command blocks and start the server again.
Another nice feature would be a F3 + [something] to disable command blocks targeting yourself. This would only work if OPed.
Also would be nice to get command block locations somehow so you know where these commands are taking place. When working with a big team there can be bugs and like most programming IDEs, you are given the location of the bugs.(at least the ones the IDE's debugger can find)
I often work with teams to build and sometimes you get these people who for some reason TP @a 0 500 0 on a repeating command block.
So your idea of adding the command disable and/or a F3 + [insert key here] to disable such commands from targeting you would be priceless.
I too have done something like this in the past. Had to use a third-party tool to get rid of all command blocks. It would be nice to have a key or something that ops could use to disable command blocks.
This is a very great Idea, And I actually love the sound of this. I've had issues like you before, Where I do a little wrong command and It messes up my game where I have to try to use commands to find it very, Very slowly. I've had to be very careful with certain commands because of this and it would make it so much more easy if we could just simply use the, "disableCommandBlocks" Command.
Sometimes I made mistakes in command blocks which causes me to teleport to a coordinate forever. I had to use MCEdit to delete that command block. I hate to switch between two programs, even if there is only a small issue to fix. So,
Support!
Edit: You can just use MCEdit or something to fix your world. That is kinda complicated but you don't have to delete the world right away.
repeatedly hurled into the void. I manged to stop it (after five minutes of teleporting myself thousands of blocks into the air and guessing on the exact location of the command block to destroy it), but realized a better solution might be to have a game rule command that disables command blocks. Even further, lets say someone has the command /kill @e put into a repeating command block where they wouldn't be able to do what I was able to do, maybe add in a button on the "death menu" to disable it. Just an idea. I could have lost the entire creative world, and I'm 100% certain someone has lost theirs.
This will be really good because as of now you have to shutdown the server, disable command blocks, start the server, find the command block, break it or change it, shutdown the server, enable command blocks and start the server again.
Another nice feature would be a F3 + [something] to disable command blocks targeting yourself. This would only work if OPed.
Also would be nice to get command block locations somehow so you know where these commands are taking place. When working with a big team there can be bugs and like most programming IDEs, you are given the location of the bugs.(at least the ones the IDE's debugger can find)
I often work with teams to build and sometimes you get these people who for some reason TP @a 0 500 0 on a repeating command block.
So your idea of adding the command disable and/or a F3 + [insert key here] to disable such commands from targeting you would be priceless.
95% support
I too have done something like this in the past. Had to use a third-party tool to get rid of all command blocks. It would be nice to have a key or something that ops could use to disable command blocks.
This has my support.
If you are planning to make a suggestion, please read this.
If you want to know more, you can read this.
For those who complain about post-Beta generation, you might want to see this.
This is a very great Idea, And I actually love the sound of this. I've had issues like you before, Where I do a little wrong command and It messes up my game where I have to try to use commands to find it very, Very slowly. I've had to be very careful with certain commands because of this and it would make it so much more easy if we could just simply use the, "disableCommandBlocks" Command.
Full Support.
Edgy lad
But for what? In MInecraft Bukkit/Vanilla you can modify server.properties.
But I support dis, because in some sort of problems I need it:D
Sometimes I made mistakes in command blocks which causes me to teleport to a coordinate forever. I had to use MCEdit to delete that command block. I hate to switch between two programs, even if there is only a small issue to fix. So,
Support!
Edit: You can just use MCEdit or something to fix your world. That is kinda complicated but you don't have to delete the world right away.
I've personally had this happen before, so I can support this.
Watch out for the crabocalypse. Some say the day will never come. But it will.
Feel free to drop by for a chat whenever.
If you'd like to talk with me about other games, here are a few I play.
Team Fortress 2
Borderlands series (Borderlands 2 is my favorite game, ever. TPS combat is a lot of fun and makes up for the lower-quality story, in my opinion)
Elder Scrolls series
Warframe (IGN is something like That_One_Flesh_Atronach)
Pokémon series (HGSS forever)
Rocket League
Fallout series
Left 4 Dead 2 (Boomer files always corrupt though)
SUPERHOT (SUPERHOT is the most innovative shooter I've played in years!)
Dead Rising series (Dead Rising 2 is one of my favorite games, and the 3rd was a lot of fun. 1st has poor survivor AI and the 4th is bad)
Just Cause series
Come to think of it, I mainly play fighting-based games.