1
Today I was playing on my server and some of my command blocks were broken.
I remember finding this bug a little while ago but forgot about it until now. All of the command blocks what had the command "kill @p" wouldn't kill the nearest player when activated by Redstone. I first started trying to fix it by using the command "/kill @p" instead of "kill @p", but that didn't work. I tried some different configurations of Redstone connections to the block but none worked. I do not know that is causing the glitch because of the fact that the command blocks were working fine a few days ago. If anybody knows how to fix this problem, please let me know! I've tried looking up how to fix this problem but I couldn't find anything that mentioned this bug. My server is a Bukkit server. I think the bug might be happening due to a plugin, but it didn't start happening right after getting a plugin. And yes, I made sure command blocks were enabled in the configuration file and that commandBlockOutput was enabled. If this bug is happening to anyone else, please leave a comment on this forum, I really would like some help!
In case anybody was wondering, only "kill @p" was broken. All my other command blocks worked, even the ones with non-vanilla commands like "warp @p [warp]". I hope this gets fixed soon!
I remember finding this bug a little while ago but forgot about it until now. All of the command blocks what had the command "kill @p" wouldn't kill the nearest player when activated by Redstone. I first started trying to fix it by using the command "/kill @p" instead of "kill @p", but that didn't work. I tried some different configurations of Redstone connections to the block but none worked. I do not know that is causing the glitch because of the fact that the command blocks were working fine a few days ago. If anybody knows how to fix this problem, please let me know! I've tried looking up how to fix this problem but I couldn't find anything that mentioned this bug. My server is a Bukkit server. I think the bug might be happening due to a plugin, but it didn't start happening right after getting a plugin. And yes, I made sure command blocks were enabled in the configuration file and that commandBlockOutput was enabled. If this bug is happening to anyone else, please leave a comment on this forum, I really would like some help!
In case anybody was wondering, only "kill @p" was broken. All my other command blocks worked, even the ones with non-vanilla commands like "warp @p [warp]". I hope this gets fixed soon!
9
I've had a different problem with bukkit and command blocks. The /clear command, when set to clear specific pieces of armor, will not clear them if you are wearing them. But if these items are in your inventory and not being worn then they will be cleared fine. The only worn armor that is cleared with the /clear command are the boots. It was pretty annoying but that bug does not happen in vanilla.
Remove the / . That migt work.
[deleted]
Were You Using Essentials Because Essentials Allows That Command To Be Used?
Ya. I was on the server with him. Im Co-Owner on his server. After a test I tried to see if Essentials was enabled. It was. I checked with the /plugins. It said Essentials So green meant it was enabled was enabled.
/kill is disabled in command blocks, it is only executable by a player, try teleporting the person into the void or something
It says it here: http://www.minecraftwiki.net/wiki/Comma ... e_Commands
It says it here: http://www.minecraftwiki.net/wiki/Comma ... e_Commands
Thanks for the advice atomic, but the command blocks were working earlier, and I haven't changed them since they broke. Have any idea as to why they broke?
Hmm
I honestly have no idea why it was actually working, if you have any mods installed, like single player commands, try uninstalling that.
I honestly have no idea why it was actually working, if you have any mods installed, like single player commands, try uninstalling that.
Nope. We were Skyping and we proved that we didnt have any mods installed. I'm a Co-Owner on his server. :/
