The Meaning of Life, the Universe, and Everything.
Location:
Texas/Candy Land
Join Date:
5/27/2014
Posts:
49
Location:
Texas/Candyland
Minecraft:
glorywarrior
Member Details
So, I'm (Surprise, surprise) trying to set up an adventure map. Of course, I hit a glitch first thing.
Here's the problem: I have a repeat command block testing for anyone nearby. It is pointing into the next command block, which I want to say something. However, the only time it works is when I set the 2nd command block to "chain" but then it spams the chat. I want it to say it once, but I can't figure out how.
Assuming this is a one time said chat that you won't need said again, you could add another chain conditional block after the say block and have it setblock the say block to air(delete). Of course, if you want it said each time someone enters this won't work...
What if you keep it the way it is now, but have comparators coming out of both command blocks. They will go into aN AND-gate that will lock the say block on so it won't keep activating. I think that should work because when then when there isn't anyone left in range the detect will turn off re-enabling the say block...
So, I'm (Surprise, surprise) trying to set up an adventure map. Of course, I hit a glitch first thing.
Here's the problem: I have a repeat command block testing for anyone nearby. It is pointing into the next command block, which I want to say something. However, the only time it works is when I set the 2nd command block to "chain" but then it spams the chat. I want it to say it once, but I can't figure out how.
This is the command I have in the first block.
This is the command I have in the 2nd block.
This is what it looks like outside.
Help? Thanks
Twitch: Glorywarrior
Youtube: glorywarrior
Twitter: _GloryWarrior_
My favorite color is black.
Assuming this is a one time said chat that you won't need said again, you could add another chain conditional block after the say block and have it setblock the say block to air(delete). Of course, if you want it said each time someone enters this won't work...
What if you keep it the way it is now, but have comparators coming out of both command blocks. They will go into aN AND-gate that will lock the say block on so it won't keep activating. I think that should work because when then when there isn't anyone left in range the detect will turn off re-enabling the say block...