The page is at https://www.minecraftjson.com.
With this tool, you can:
- Create complex chat messages, full-screen text alerts, custom signs, and books.
- Add fully formatted hover text, click actions, and more
- Show NBT data, scoreboard values, custom user keybinds
- Save and restore your commands
1
Features:
Also, if you like what you see, please consider leaving a like on the youtube video, or a diamond on the PlanetMinecraft project (here). It really helps me a lot, and it makes me happy
1
2
1
The c= parameter sets a maximum player count for the command to check for. What it does is it checks until it finds 1 person (since c=1), and then it simply stops. It doesn't simply check to see if only 1 person is left. To do that, use the output strength of the comparator. If you run this command: Then the comparator you use as the output will output a signal strength for every player it finds. So if it finds 2 players, it will output a signal strength of 2. Therefore if it only finds one person, it will output a signal strength of 1. So to do what you want, you'll want to put this command on your clock and then take an output when the output signal is one. This can be done with the following circuit:
(I kinda took that image from Skylinerw, because it was good and I didn't want to make my own. He won't mind. I think.) Just put two items in the left hopper, and use the torch as the output. It will only turn on when 1 player has a score of 1. If 2 or more players have that score, it will turn off.
1
As for testing for multiple people, the comparator will output a signal strength that shows how many people it found. So to test for exactly 2 people, hook up a signal strength detector to detect when the comparator outputs a signal strength of 2. If you'd like pictures I can probably find some somewhere, but there are also videos and things can probably show you specific circuits if you need them.
1
As for testing for scores, you put the name of the objective in the brackets, not the criteria type. For example:
1
Just put the command on a clock, like a hopper clock or a fill clock. Since you're adding a score of 0, having it running constantly will not interfere with any other scores you might be using.
1
Comparators will stay on until the SuccessCount of the command block they are hooked up to turns to 0. This can be done with the blockdata command, simply run it when the comparator gets powered: Just replace x y z with the coordinates (absolute or relative) of the command block you want to reset, and you should be good to go.
1
1
Just a small correction here, comparators technically can output a signal strength higher than 15, but since any dust or repeaters will then reset it down to 15 it's pretty much pointless. But you still can perform subtraction and comparisons with comparators, even if the signal strengths go far above 15.