60

Using the Scoreboard 1.8

Collectable

Enjoy reading!

Get Embed Code

Forum:
HTML:
Link:
avatar
Headaxe
Level 50 : Grandmaster Unicorn
USING THE SCOREBOARD 1.8
-a complete guide on all commands of the Scoreboard
There are several reasons for not using the scoreboard.
Some don't get what individual commands do while others couldn't find a good list with senseful explenations of all the commands.
But both these issues are no problem after reading this blog.
Even though it's hard work to learn all the tricks, working with the scoreboard gives you unbelievable new possibilities as a map creator and therefore it's more than worth it to invest time into the studies.


Instructions on reading this blog
I used a couple of color codes and other techniques in this blog, which you should better understand before reading.

(round brackets)A part of the command, you have to add to perform it
[square brackets]A part of the command, you can add if you want to

Blue
A scoreboard command
OrangeA list of options in a command, you can choose between
GreenAn example for the usage of the scoreboard



Full Guide
/scoreboard objectives
/scoreboard objectives list
Using this command allows you to see a detailed list of all objectives you added to the world.
/scoreboard objectives list

/scoreboard objectives add/remove
This command allows you to add objectives or to remove them.
When you are creating an objective, you'll have to add a criteriaType.
You can choose between 5 different types.
You can only remove objectives that already exist.
The internal name is always the name used in operations and more, while the display name only appears on lists and more.
Objective types
dummy: If somebody has an objective value/score with a criteria type named dummy, he won't be able to change the value by hand. The only way to change the value then, is to use a /scoreboard players command.
health: This type reflects your hearts. If you have 10 hearts, the score is 20.
totalKillCount: You get 1 point for killing any player, mob or animal.
playerKillCount: You get 1 point for killing any player.
deathCount: You get 1 point for each respawn.
achievement.(internal achievement name): Checks if you have earned a certain achievement
stat.(internal stat name): Tests for several actions like walking, being hit, falling and much more
stat.craftItem.(Item ID): Tests for crafting a certain item or block
stat.useItem.(Item ID): Tests for using an item (placing blocks, throwing eggs...)
stat.breakItem.(Item ID): Tests for breaking an Item (Mining with tools)
stat.mineBlock.(Block ID): Tests for amount of one type of blocks mined
stat.killEntity.(Mob ID): Tests for amount of one type of mobs killed by the player
stat.entityKilledBy.(Mob ID): Tests how often the player was killed by one type of entities
stat.teamkill.(team color): Checks how many team members with a certain team color were killed by the player
stat.killedByTeam.(team color): Checks how often the player was killed by team members with a certain team color
You can add a custom name for your brand new objective too.
/scoreboard objectives add (internal objective name) (objective type) [display objective name]
/scoreboard objectives remove (internal objective name)

/scoreboard objectives setdisplay
People want to see their score, money, values or other people's hearts.
If you want to add this function, you can choose between three different display slots.
Remember that you can only put existing objectives into a setdisplay slot.
Display Slots
sidebar: Your score will be displayed at the right side of the screen.
Scores of players who aren't online get displayed too, so you can use this as a highscore list.
sidebar.team.(team color): The sidebar is only visible to players that are member of a team with a certain team color
belowname: If you are in a distance of 20 blocks to an other player, you will be able to see his score below the player name.
list: Press tab and the score will be displayed next to the name of a player.
If you don't add a name after the display slot, the slot will get cleared.
/scoreboard objectives setdisplay (display slot) [internal objective name]

/scoreboard players
/scoreboard players add/remove/set
This is the most essential command for interacting with player scores.
By using it you are able to modify a players score.
You can even add scores to nonexistant players, so they just exist for counting or multiplying scores etc.
Player names that are not supposed to appear in the sidebar or other lists, have to start with a ''#''.
Also, in 1.8 the option of selecting players with data tags in this command was added, so you are able to modifiy the value of entities and players, who have a specific tag.
This makes it possible to translate Data Tags into scoreboard values, which also makes a lot more things possible.
/scoreboard players remove (player) (internal objective name) (amount) {Data Tag}
/scoreboard players add (player) (internal objective name) (amount) {Data Tag}
/scoreboard players set (player) (internal objective name) (amount) {Data Tag}
/scoreboard players set #(player) (internal objective name) (amount)
Please remember, that you have to add extra charakters to the Data Tag Parts depending on the type of of the Part, you are trying to involve.
/scoreboard players set @e air 1 {Air:20s}


/scoreboard players reset
By using this command, you can reset all scores a player reached or reset one objective score a player reached.
''*'' is a new 1.8 selector which targets everyone tracked by the scoreboard.
Using it will reset everyone's score, even if they are not online, which is helpful when your sidebar is spammed with
player scores that are not even online and you don't want that.
/scoreboard players reset (player) [internal objective name]
/scoreboard players reset *


/scoreboard players list
Use this command to see the scores of different players or to see all players tracked by the scoreboard.
Without using a name, you can list all players tracked by the scoreboard.
By adding a name you can see all scores somebody has.
''*'' is a new 1.8 selector which targets everyone tracked by the scoreboard.
By using it as a player in this command you get every score of everyone tracked.
/scoreboard players list [player]
/scoreboard players list *

/scoreboard players test
Tests if a player has a score in a certain objective that's between a minimum score and an optional maximum score.
The command is much easier to use than the old /testfor way of testing.
Besides that, the player you are testing for mustn't be online or even existing, you can test for anything and anyone you want.
/scoreboard players test (player) (internal objective name) (min player score) [max player score]

/scoreboard players operation
That command is actually working like a calculator and helps you adding scores to each other, multiplying scores and much more.
The player you are calculating with, doesn't even has to be online, so you can use ''ghost'' players aswell.
Operation types
+= Adds the source player's source score to the target player's target score

-= Removes the source player's source score from the target player's target score

*= Multiplies the source player's source score with the target player's target score

/= Divides the target player's target score through the source player's source score

%=Modular Division: takes the target player's score and divides it by the source player's score, and then saves the remainder into the target players score.

=   The target players' score is being turned into the source players' score.

>< Swaps the score of the target player and the source player

<  Checks for the target player's score and the source player's score and turns the target player's score into the lowest value

>  Checks for the target player's score and the source player's score and turns the target player's score into the highest value

/scoreboard players operation (target player) (internal target objective name) (operation type)
(source player) (internal source objective name)

Advanced operation tutorial
Percentage Operations
By combining operation types, you can get interesting effects.
By first multiplying something by 120, and then dividing a value through 100, you add 20% to the existing score.
Also, by multiplying something by 3965 and then dividing it through 1000, you could set a score to precisely 396.5%
This is useful when you want to have a system that adds or removes a certain percentage to the score.
And that is really useful when having to use high precision calculation with comparably low, full numbers.

/scoreboard players operation (selector) (internal objective name) *= (selector) a
/scoreboard players operation (selector) (internal objective name) *= (selector) b
Δx%=a-b


This command is the most complicated part of the scoreboard, so I will explain you it a bit further.

The target player is always the player who's score will get affected in the end.
Whatever what operation you perform, the source players' score will not be modified.
The target objective is the objective which is going to be affected by the operation.

The operation type defines how source player and target player interact in the operation.

The source player is the player who's score is being added, removed, synchronnized etc. from/to/with the target player's score.
The source objective selects the objective that the source player is adding/removing etc. from/to/with the target player.

Here comes an extremely stupid example ^^: 
SethBling's coolness: 100 | Minecraft's redstone: 50
/scoreboard players operation SethBling coolness += Minecraft redstone
In this example Minecraft's 50 redstone would be added to SethBling's 100 coolness, which would mean that SethBling's coolness score is now 150.

/scoreboard teams
/scoreboard teams list
Use it to list all teams you created without adding a team name or check which players are in a certain team.
/scoreboard teams list [internal team name]

/scoreboard teams add/remove
Create or remove teams.
When you are creating a team you can type the system name first and then add a display name.
/scoreboard teams add (internal team name) [display team name]
/scoreboard teams remove (internal team name)

/scoreboard teams join/leave
You can join/leave a team, you created or let other people join/leave the team. If you use the command without a player, you will get selected as the person to join/leave the team.
/scoreboard teams join (internal team name) [player]
/scoreboard teams leave [player]

/scoreboard teams option
Use this command to customize a team.
There are several things you can change in a team, that affect it's appeareance or  the interaction between the players within a team.
Options
color: Select a display color for your team. The nametags of players will change their color to the team color you selected. Choose between "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white".

friendlyfire: Tells if players in one team can attack each other. The option does not effect lava, potions, tnt, or other indirect attack sources. Choose between ''true and ''false''.

seeFriendlyInvisibles: Allows you to see a transparent player model of your team members, while they are invisible. Choose between ''true'' and ''false''.

nametagVisibility: Affects which people are able too see you team's nametag.
Choose between:
''never'': No one see's your nametag
''hideForOtherTeams'': Other teams can't see your nametag
''hideForOwnTeam'': Your own team can't see your nametag.
''always'': Everyone can see your nametag.

/scoreboard teams option (internal team name) (option) (value)

/trigger
Adding triggers
Triggers are nothing but a very special type of scorebaord objectives.
Unlike other objectives, you can let players that aren't even operators use a trigger command.
In order to create such an objective, use:
/scoreboard objectives add (internal objective name) trigger (display objective name)

Enableing triggers
A player has no right or permission to activate a trigger, unless you enable the trigger for the player.
This way you can define at which point a player is permitted to activate a mechanism, how often, how, etc.
/scoreboard players enable (selector) (internal objective name)

Using triggers
A player that is able to use a trigger can activate it in all kinds of ways.
They can simply use the command for triggering themselves or use it in a tellraw command in books, on signs, in chat etc.
/trigger (internal objective name) add (value)
/trigger (internal objective name) set (value)

/stats
/stats ... clear
With this setting you can reset, what stat type is being transformed into a scoreboard value after the command has been executed.
Normally, all command blocks or entities don't have any set type of stats, being transformed into a scoreboard value.
/stats entity (selector) clear (stat type)
/stats block x y z clear (stat type)

/stats ... set
Allows you to transform a statistic into a scoreboard value of a specified entity or player.
Statistics are being gathered by letting a command block execute a command or by using /execute on an entity.
The entity which executed the command will save several types of results.
The first part of the command always specifies, where you gather the information while the second part always specifies where you save the information.
Obviously, you can only gather information from command blocks and existing entities.
You can't gather information from other blocks or from nonexistant players, saved in the scoreboard.
However,

1.  You can save information on nonexistant players, saved in the scoreboard, but they have to have an existing score before you do so already
2. A /stat command is not taking existing information from a command block, but telling a command block/entity to save the information somewhere.
You can only track one stat type at a time and once you have told a command block/entity to save a stat, it will always do so until you use /stats...clear on it.
3. Your command does not have to change something in order to save information in "Affected" stat types.
You can also use commands that gather information, such as /clear...0, /time query, /worldborder get, /testfor and many, many more.

(Warning: Using fast clocks on command blocks can lead to not fully storing the stats)
Stat Types
SuccessCount: Shows, wether the last command has been successful or not in most cases.
Defines the signal strength that is being output by comparators which means that only a couple of commands like /testfor can set the SuccessCount to something higher than 1

AffectedBlocks: Shows, how many blocks the last command affected

AffectedEntities: Shows, how many entities the last command affected

AffectedItems: Shows, how many items the last command affected. (Not Items on the ground, but items in a player's inventory that are being affected by commands like /replaceitem or /clear

QueryResult: A stat, that tracks the result of a command. This can be the result of an operation, or of commands that gather information such as "/time" query gametime or "/worldborder get"

/stats entity (selector) set (stat type) (target selector) (internal objective name)
/stats block x y z (stat type) (target selector) (internal objective name)

Player selection
If you want to interact with command blocks, you can add some scoreboard based arguments.
As you know, you can use @p @a and @r to select different players.
You can add special arguments to this players-selections.
In 1.8 you are able to select all entities using @e.
@a[score_money=100,score_money_min=100]
Will select all people who have a minimum score of 100 and a maximum score of 100.
@r[team=red]
Will select a random player, who is member of team red
@p[team=]
Will select the nearest player, who is member of no team.

Read the wiki article about Command Blocks, if you want to find out all about arguments.



Solutions for common problems
Autocomplete in commands
The scoreboard contains a lot of different types of objectives, different options for teams and much more which you would normally have to remember in order to use them.

It's obvious, that no one can remember all these different settings, however there is one button which saves your day.
Pressing tab automatically completes the part of the command, you are currently working on.
So before actually asking for support on this blog or searching the wiki for lists of objectives and more, simply try to find things out yourself by using the autocomplete function.

/scoreboard objectives add coins d -> *presses tab* ->  /scoreboard objectives add coins dummy

Negative testing
Negative testing
If you want to test for something negative, for instance if a player does not have an item, if a player is not inside an area, if a player is not holding an item in their hands, then you have to use at least two command blocks.

Command blocks that are connected to a /fill clock or to the same redstone wire seem to be activated in the same moment, but they get activated in a certain order.

To test for something negative, enter the following command in the first command block:
/scoreboard players set selector objective 0
Then enter:
/scoreboard players set selector[...] objective 1 {...}

By using this method, the score will never fall to 0 unless you don't have the item or unless you aren't in the area etc.
To then select people who fulfill the negative requirement, simply use
@a[score_objective=0]
By replacing "set" with "remove" or "add" in the commands, you can also test how many ticks the player doesn't/does fulfill the requirements already.

Displaying several objectives in the sidebar
Displaying several objectives in the sidebar
On singleplayer or coop maps it is not very senseful to display just one objective in the sidebar for several players.
To change the function of the sidebar, create a new objective called "stats" and let it be displayed in the sidebar.
/scoreboard objectives add stats dummy
/scoreboard objectives setdisplay sidebar stats

Then use operations to get your own scores into the sidebar, using operations. You shall use nonexistant players for displaying your scores.
/scoreboard players operation Money stats = @a money
/scoreboard players operation Health stats = @a health
/scoreboard players operation Level stats = @a level

To make the sidebar even fancier, add these nonexistant players to a team, which uses a certain color.
/scoreboard teams add yellow
/scoreboard teams option yellow color yellow
/scoreboard teams join yellow Money

Precise Time measuring
Precise time measuring
To measure time, many people use clocks that add 1 scoreboard value per second to a certain player.
However, this method is comparably inaccurate, because every single bit of lag caused by tnt, redstone and more already slows this process down.
When you have a parkour map or a map that includes speedrun features, it is highly recommended to use this method.

What you can do is measuring time, usng the worldborder.
First, add a new objective called "time"
/scoreboard objectives add time dummy

Then create an armor stand or something else, that will save the scoreboard value inside your spawn chunks.
Start by setting the world border to a comparably high value.
/worldborder set 1000000 (1 Million)
Continue by letting the worldborder expand by one block per second.
/worldborder set 2000000 1000000 or
/worldborder set 60000000 59000000
Unlike a clock powered by ticks the worldborder expands using an external process.
No matter how much lag is being caused, the world border will progress normally.

All you have to do now is getting the value of the worldborder (in a command block).
/worldborder get
The command block has saved the value as a QueryResult (result of a command) now.
All you have to do now is transforming this result into a scoreboard value.
/stats block x y z set QueryResult Time time
Remember, the x y z coordinates hace to be the coordinates of the command block with the saved QueryResult.

The last two commands have to be connected to a comparably fast clock.
The last command block, which has to be triggered as last will now remove the initial 1M blocks from the value.
/scoreboard players remove Time time 1000000

To display the time in the sidebar, use the previous method.
/scoreboard objectives add stats dummy
/scoreboard players operation Time stats = Time time

/scoreboard objectives setdisplay sidebar stats

Adding new gamerules
Adding new gamerules
Sometimes doing this is worth the effort.
Certain multiplayer maps or even singleplayer maps allow the operator to change the map's experience.
/gamerule commands are the most obvious way to do so.
/gamerule (gamerule name) [value]
You can create new gamerules by giving a gamerule a value.
/gamerule respawntime 100

You can enter anything you want as a value, but only if it is a number, you'll be able to save it as a scoreboard value.
Continue by making an armor stand with a custom name, that you can use to save results.
(The following steps are not possible with /stats block)
/summon ArmorStand x y z {CustomName:"respawntime"}
Also remember that the ArmorStand has to be loaded, so it has to be near a player or inside the spawn chunks.

The following command should be connected to a comparably fast clock.
/execute @e[name=respawntime] ~ ~ ~ /gamerule respawntime

The value, the ArmorStand returns will be the current number, saved as the setting for "respawntime".
To now transform the armor stand's result into a scoreboard value, use:
/scoreboard objectives add gamerule dummy
/stats entity @e[name=respawntime] set QueryResult @e[name=respawntime] gamerule


What this entire setup does, is transforming the current setting for "respawntime" into the gamerule-score of the armor stand "respawntime".
This system allows you to use any kind of system to change the gamerule.
You can adjust settings by using /tellraw data in books, on signs, in chat etc.
But you can also set the gamerule by hand at any given time or by using a command block, connected to a button.
All that possibilities make this gamerule system extremely convenient and an easy way to allow players to modify settings on your map.

Combining scores
Combining scores
This method helps you create statistics for groups of players, for an entire server and for teams.
Let's say, you have a basic PVP map with two teams.
The gamemode is "Team Deathmatch", the team with the most kills in total wins.
The problem at this point would be, that all players save their scoreboard values individually instead of directly sending them to a team.

First, create an objective to track teamkills.
/scoreboard objectives add killsRed teamkill.blue
/scoreboard objectives add killsBlue teamkill.red

(the color at the end of the objective type specifies the team's current color, not the internal team name)

To combine those scores, place to command blocks, connected to a clock.
The order in which the command blocks are being activated is important.
/scoreboard players set RED killsRed 0
/scoreboard players operation RED killsRed += * killsRed
/scoreboard players set BLUE killsBlue 0
/scoreboard players operation BLUE killsBlue += * killsBlue
The reason, you're using the selector "*" is simply the fact that you could reduce the amount of kills, your team made by logging out during the match which wouldn't be realistic.

You can combine all kinds of different scores this way.
Instead of using it for competitive maps you could also use the system for adding a "total amount of money gathered" on a server or other global statistics that might be worth keeping.



Toolbox
OCTAFONT C5: Charakter Highlighting (Resource Pack)
Sometimes commands can become extremely long and complex.
Especially brackets in data tags can be hard to see through after entering one or two lists, 10 data values and more.
To give the user a bit more overview, this resource pack (which comes in various colors) gives brackets a certain color, but also colors all charakters, involved into commands such as "~ , ! + ="  and more.

undefined

Command Syntax Mod: Syntax Highlighting (Mod for 1.8+)
Zx5ZKqIaVMU

The is mod is way more advanced than the previous resource pack as you ca see.
However, it requires forge and mod installation.
Due to more and more additions such as Autocomplete in Command Blocks and most likely adding color codes to command blocks IN THE GAME soon, it is a modification that should be just as part of your routine installation like NBT-Edit, MC-Edit, NEI/TMI and more.

undefined















~THE END~

















If you want to read more nice tutorials:



                                 undefined 
Tags:Tutorial, How To, Scoreboard, Commands, Cheats, Command Blocks, Score, Display, Players, Minecraft, Objectives, Teams, PVP
Credit:Headaxe

Toolbox : 01/03/2015 8:51:58 am1/03/15

+added section: Toolbox
 ->added "OCTAFONT C5"
 ->added "Command Syntax Mod"
+improved and re-color coded the section "advanced operation types"
+smaller fixes

+More, More, More : 12/31/2014 11:27:18 am12/31/14

+full guide on /stats
+full guide on /trigger

+added "Adding new gamerules"
+added "Combining scores"
+improved "Precise time measuring"

Improvements, Additions, Layout Changes : 12/30/2014 11:09:09 am12/30/14

+added: "Precise Time Measuring" solutions and improved it
+changed layout of Solutions for common problems

Solutions for common problems : 12/29/2014 7:43:24 am12/29/14

+added section: Solutions for common problems

Fixes, Support, Operations : 12/05/2014 5:32:27 pm12/05/14

+fixed and updated operation types
+added subsection "Alternative operation types"

Additions and Improvements : 09/14/2014 4:42:34 am9/14/14

+Added several parts like "Instructions on reading this blog"
+Added a couple of "forgotten" parts in the blog
+Improved the explenation for commands such as "scoreboard players operation and /scoreboard players set/add/remove
+Edited introduction and the top of the blog

Smaller Improvements and Fixes : 02/24/2014 5:34:40 am2/24/14

+Edited some command descriptions
+Fixed some grammar
+Fixed /teams option mistakes --> ''(option)'' and ''(player)'' switched
                                                         --> description of teams option nametagVisibility was false

Layout Fix : 02/19/2014 12:42:52 pm2/19/14

+Fixed all removed spoiler titles, colors and much more problems that occured in the new PMC text version.

Up-To-Date Update : 02/18/2014 10:17:03 pm2/18/14

+adding the 1.8 features one after another and giving the whole blog a new look

Reboot : 02/18/2014 9:34:22 pm2/18/14

+Fixed the formatting errors after a PMC update
+''Examples'' are now general command instructions
+Edited a few text parts

Optical Update : 06/22/2013 5:03:09 am6/22/13

+Fixed some grammar
+Edited the Highlight color of some things
+Changed the font size of the Headers

Smaller Improvements : 06/21/2013 12:07:53 pm6/21/13

+Fixed the bad spelling of scoreboard...ON THE COVER!
+Fixed some grammar
+Added some details about the new tutorial collection.

Comments : 77

Join us to post comments.

Show Comments

1 - 50 of 77

  • Veritas025
  • Level 28
  • Expert Engineer
  • July 20, 2015, 8:28 am
This is very useful but you should also mention stuff about using scoreboards in testfor lik /execute @a[score_killZombie_min=1000] /give @a diamond_block. Like you can give a diamond block to whoever kills 1000 zombies when you have /scoreboard objectives add killZombie stat.killEntity.Zombie or /testfor @a[score_killZombie_min=1000] then have a comparator doing /give @a[score_killZombie_min=1000] diamond_block
Edit Reply Delete
  • Ustinich
  • Level 1
  • New Miner
  • July 16, 2015, 7:39 am
I need help.
I want to make a mechanism that will check the sameness of Points players.
For example a player has 10 points and the other player has 10 points in the Scoreboard. It is checked, and then run the command. Please, help!
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • July 17, 2015, 12:01 pm
So basically, first you put the score of player #1 into a new temporary objective using an execute operation.
Afterwards, you subtract the second player's score from that temporary score.

If the temporary score is now 0, the two scores are equal and you can use an execute off the first player if they have a score of 0 in the temporary objective.
Edit Reply Delete
I'm setting up health under the tablist on my server but it seems terrible at updating. When someone holds an item with an increase health attribute, the health goes up under tab and stays there even when they aren't holding the item.

Also, when anyone changes their gamemode it doesn't update it then either. For example, if someone was in survival it would be displaying the hearts, then when they went into creative it would still display the hearts. Only after relogging would it update. Is there a way to fix this?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • July 9, 2015, 5:14 am
First of all, when you hold an item to increase your health, you will keep the health you might have gained by that even after the item is gone.
So say, you double the health of a player for a while and after the effect is gone they will still keep this extra health.
And Minecraft only displays this current real health without caring about your maximum health at all.

Second of all, the way health gets displayed in the tablist is fixed and hardcoded into Minecraft.
There is no way to change that.
However, you can make a custom health tracker using a fast clock with 20 command blocks.

/scoreboard players set @a Hearts 1 {Health:1s}
/scoreboard players set @a Hearts 2 {Health:2s}
/scoreboard players set @a Hearts 3 {Health:3s}
...

This way you translate the amount of hearts a player has into a score, then display it in the tablist.
Edit Reply Delete
Ah, nevermind I figured it out. I thought you were talking about the health objective but I used the dummy objective instead to just display it as a number instead of hearts, which I actually like better because it saved space under the tablist. Thanks for your help.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • July 11, 2015, 7:26 am
No problem ;)
Edit Reply Delete
One thing that I realized is that every single health level that doesn't match any player's current health is reported to the console as "[Server] INFO [@: The dataTag does not match for 357]" and on the other hand, every health level that does find a match is also reported to the console as "[Server] INFO [357: Set score of Hearts for player 357 to 20]"


Is there a way to remove this? Because although the health machine is working like a charm I don't think it's worth having 900GB of server logs to delete every single day. On my server, I have special armor and powerups that increase a player's max health, not to mention enchanted apples, so I made the max health level go all the way up to 52. This sends thousands of messages to the console every second the machine is on.

I've looked everywhere for a solution to this and tried many as well, and I haven't found anything that works. Thanks again for your help. Perhaps this discussion will help other players in the future.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • July 12, 2015, 4:16 am
Typically you can deactivate logging every command to the console with the gamerule "logAdminCommands" I think.
Maybe it was "reducedDebugInfo".

What I know for certain is that you can avoid log spam using gamerules.
Edit Reply Delete
Okay, I made an objective by the name of "Hearts" in order to use this. (/scoreboard objectives add Hearts health)

Whenever I try to execute it in a command block, it returns "[@:The objective 'Hearts' is read-only and cannot be set]"

Is there a way to get around this or am I doing something incorrectly?
Edit Reply Delete
  • Hoboneer
  • Level 5
  • Apprentice Engineer
  • May 19, 2015, 12:22 am
How do i send a message to someone of a specific team with command blocks?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • May 19, 2015, 5:55 am
/tell @a[team=...] message
Edit Reply Delete
  • Hoboneer
  • Level 5
  • Apprentice Engineer
  • May 21, 2015, 12:37 am
It seems to send me the message even though I'm not on that team, strange :/
Edit Reply Delete
  • Jemrada
  • Level 1
  • New Miner
  • April 9, 2015, 8:53 am
I am trying to add current players xp total to scoreboard.

I have the following command in a command block. To start with...

scoreboard players add @a currentxp 0

It resets the players to 0 instead of adding to currentxp

currentxp is a dummy objective I setup.
Edit Reply Delete
  • Cyrotos
  • Level 1
  • New Miner
  • January 3, 2015, 3:23 am
Is there a way to do a top 5 or top 10 on the scoreboard?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • January 3, 2015, 3:54 am
Not really.
You could only check for the player with THE highest score, but besides that, there isn't really a way to do so.
However, the display slot "sidebar" automatically creates a list that lists the players/entities with the highest scores.
Edit Reply Delete
  • discOtter
  • Level 45
  • Master Giraffe
  • December 30, 2014, 6:17 am
THANK YOU!
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 30, 2014, 6:18 am
np
Edit Reply Delete
So I want to do this thing where it shows ALL mobs that you've killed. Anyway I can do that?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 30, 2014, 3:46 pm
The objective type "totalKillCount" should do it.
Edit Reply Delete
TY and 1 more thing:

On /scoreboard objectives setdisplay sidebar (name) when it goes up the title is always white (On mineplex the title is bold). How do I make that a color? And what does sidebar.team.(color) do?

And on my server we're doing this thing called Diamond Bucks. Anyway when 1 person is on it only shows 1 person on the sidebar, not all players?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • January 1, 2015, 6:40 am
You can modify scoreboard objective names, scoreboard entry names and more, using an "NBT-Editor".
These programms allow you to access .dat files such as the level.dat or the scoreboard.dat inside your minecraft world folder.
One of the most user friendly one's is NBT Explorer.
The way servers like Mineplex do it is fundamentally different though,
Servers like that are running on Bukkit which allows them to modify mechanics and color codes with plugins.
Edit Reply Delete
  • Digin4Ever
  • Level 3
  • Apprentice Artist
  • December 5, 2014, 2:56 pm
Nice thanks for updating it. :D
Edit Reply Delete
  • Jmal116
  • Level 22
  • Expert Engineer
  • December 5, 2014, 12:00 pm
Looks pretty nice overall, and extremely detailed and complete. But I did notice a couple little things wrong with the operations section that you might want to fix :P

- %= does not actually do a percent, it does something called modular division. It essentially take the target players score and divides it by the source player's score, and then saves the remainder into the target players score. So for example, 10 % 4 = 2, since the remainder is two. This also means any number % 0 = the same number, and any  number % 1 =0.

- You have the players swapped on the = operation. The target turns into the source, rather than the source turning into the target.

- They're recently added a few new operations, <, >, and ><. the < operation will make the target players score less than or equal to the source players score, so 5 < 3 = 3, but 2 < 3 = 2.
- The > operation does the same thing, but it make the target player's score greater than or equal to the source players score. So 5 > 3 =5, but 2 > 3 = 3.

- Finally, the >< operation swaps the scores of the target and source player. So it the target's score = 5 and the source's score = 7, the >< operation will make the target = 7 and the source = 5.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 5, 2014, 12:35 pm
Thanks a lot for your help.
I adjusted everything and updated the operation list to the latest hot 1.8 stuff.

/)
Edit Reply Delete
I'm having trouble with the stat.killedEntity.(MobID) thing. I entered Hex, ID, and Savegame ID of Skeleton but it reutrns with "Usage: Invalid objective criteria type: "stat.killedEntity.51".", "Usage: Invalid objective criteria type: "stat.killedEntity.33".", and Usage: Invalid objective criteria type: "stat.killedEntity.Skeleton".".
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • November 28, 2014, 1:15 pm
It is not "stat.killedEntity.Skeleton", but "stat.killEntity.Skeleton".
The difference is very minor and the mistake is in fact hard to see.

Seems like they changed the objective, so my list in here isn't as up to date as expected.
If you have trouble with objective types in the future, use "TAB" to autocomplete it, which will give you the correct objective type.
Edit Reply Delete
Thank you. I am not on the same computer, so I will try it when I get on the one that I need it for.
Edit Reply Delete
Another thing, however, on a different map I'm making, I want a currency type thing. I figured out the set and remove part, however how do I make it so if it's below the needed price it won't work?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • November 29, 2014, 11:32 pm
/scoreboard players remove @p[score_money_min=100] money 100

Or eventually just test for someone's score with /testfor.
Not sure how your mechanism works.
Edit Reply Delete
Thanks for the help!
Edit Reply Delete
  • Jagged007
  • Level 4
  • Apprentice Architect
  • November 25, 2014, 4:14 pm
Is there a way to do this for xp? I'm making a plugin that at different levels u unlock the ability to enchant your stuff with something and it never takes away xp so I want a top player xp scoreboard.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • November 25, 2014, 11:02 pm
You can transform xp levels into scoreboard values, but it takes one command block per possible level.
/scoreboard players set @a[l=0] level 0
/scoreboard players set @a[lm=1,l=1] level 1
/scoreboard players set @a[lm=2,l=2] level 2
...
Of course, this is all command blocks, I don't really know how it would work with plugins.
Edit Reply Delete
  • Seames39
  • Level 45
  • Master Sailor
  • November 22, 2014, 6:45 pm
Hey Im trying to make a PvP map with two teams and I want to make it so that when a player on one team kills a player on an enemy team, his/her kill counts towards a total team kill count. how do you do this?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • November 22, 2014, 11:59 pm
First, you add an objective called "kills" with the type playerKillCount in order to track the kills of players.
/scoreboard objectives add kills playerKillCount

After that, you have to use a nonexistant player, who receives all the points.
Execute the following command repeatedly with a fast clock:
/scoreboard players operation redkills kills = @a[team=red] kills

I hope, that was helpful ;D
Edit Reply Delete
  • Seames39
  • Level 45
  • Master Sailor
  • November 23, 2014, 8:32 am
Uh I don't see anything change. Is there a command to display it?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • November 23, 2014, 9:16 am
Use /scoreboard objectives setdisplay sidebar kills.
The player with the name "redkills" should then have the score of every player in the read team.
Edit Reply Delete
  • Seames39
  • Level 45
  • Master Sailor
  • November 23, 2014, 9:25 am
I am officially impressed :D Count me as a subscriber ;)
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 30, 2014, 3:48 pm
The initial solution I gave you didn't work as expected.
The operation type "=" doesn't select all players.
If you want to fix your system up (assuming, you haven't found a solution yet), you should now check the section Solutions for common problems.
Edit Reply Delete
  • Arcaniax
  • Level 66
  • High Grandmaster Senpai
  • October 31, 2014, 5:45 am
Someone i know uses dummy a lot because it's a placeholder for everything you want :)
he even made a working signshop with the trigger on signs now :P
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 30, 2014, 3:48 pm
Did he?
Edit Reply Delete
  • Arcaniax
  • Level 66
  • High Grandmaster Senpai
  • December 31, 2014, 4:09 am
who? :P
Edit Reply Delete
  • DuckHD
  • Level 2
  • Apprentice Explorer
  • October 24, 2014, 4:47 am
Im making a minecraft map and im trying to every person have 5 lives, i used the dummy command and death commands, but it still wont remove points when i die, help?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • October 24, 2014, 5:50 am
There is no type of objective that removes your lifes if you die.
However, there is an objective type called deathCount which will add one point every time you die to itself.

What you have to make is a translator.
Set up a clock which triggers two command blocks at once, but make sure they get activated in the correct order.
1. "/scoreboard players remove @a[score_deaths_min=1] lifes 1"
2. "/scoreboard players remove @a[score_deaths_min=1] deaths 1"

This way the deaths are being translated into a loss of lifes.
In order to make a reaction after someone lost all lifes simply add another one saying:
3. "/kill @a[score_lifes=0]" (only an example, doesn't have to kill players)

To add lifes simply add "/scoreboard players set player lifes 5"

Two most known sources of bugs are:
1. Command blocks being activated in the same tick, but not in the correct order
2. Testing for player's scores doesn't work if they never had a score in an objective

I hope I could help you with this, have a nice day!
Edit Reply Delete
  • xin8
  • Level 13
  • Journeyman Architect
  • October 2, 2014, 3:20 pm
I'm making an adventure map and theres a part where when you step on a pressure plate, and your dummy variable is 1 (which I already set)  you get an item, which can be used multiple times. I put your /scoreboard players test command (which works fine) and it sends out a signal via comparator. The problem is, I want a pulse signal, like a button, not a full signal because I want this pressure plate to be reusable. Do you know how to make it so that it only sends a pulse signal? thanks
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • October 2, 2014, 4:02 pm
Make something which updates the command block which outputs the comparator signal.
Everytime a command block is being updated by redstone or by recreating/modifying the block, it resets it's score.

In theory /blockdata x y z {SuccessCount:0} should reset the output of the command block.
If it does not work, try /setblock x y z minecraft:command_block 0 replace {Command:...} to recreate the block.
If it still doesn't work, use a /clone command to recreate the command block and the comparator.

All three methods should work in theory.
Edit Reply Delete
  • xin8
  • Level 13
  • Journeyman Architect
  • October 3, 2014, 1:09 pm
Thanks dude!
Edit Reply Delete
  • ToadieOdie
  • Level 40
  • Master Goblin
  • September 14, 2014, 3:05 am
The dummy objective is really handy for tracking story/quest progression on an adventure map and for making vanilla starter kits for server maps. Both are handled by command blocks.

I'm sure there are many more creative ways to use the scoreboard. It would be great if readers would share what they used the scoreboard for to help inspire new map makers.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • December 30, 2014, 3:50 pm
I started gathering such things in the new section Solutions for common problems.
You might wanna check it out ^^
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • September 14, 2014, 3:12 am
Well I am actually quite sure that there are forums posts which handle that quite well.
In the end, using the scoreboard is always a thing for solving problems, tracking stuff, adding custom ai, items, entity behavior and more.

There is always a problem to solve which you have to have before thinking about how to solve it.
However, some inspiration could help indeed ;D
Edit Reply Delete
  • ToadieOdie
  • Level 40
  • Master Goblin
  • September 14, 2014, 3:17 am
Ah, I hadn't thought to check the forums for that. I was just thinking about the people coming here wanting to know what the scoreboard is and have never used it before.

All the technical information in here is great though. :3
Edit Reply Delete
  • huge_chomper
  • Level 16
  • Journeyman Pig
  • September 14, 2014, 1:07 am
I think you have a problem spelling the word "certain"? you keep writing cercaint. 

In-depth information, well done.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • September 14, 2014, 1:36 am
Yeah this blog is quite old and with every update I forgot to fix those issues.
Time for that now ;D
Edit Reply Delete
sorry im a noob trying to make a map. What's the command to add a dummy score?
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 30, 2014, 4:12 am
/scoreboard objectives add (internal name) dummy (display name)
Edit Reply Delete
  • iCraZzMC
  • Level 38
  • Artisan Cake
  • August 27, 2014, 3:20 am
question! what about entities? I heard that Entities can have scoreboards too
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 27, 2014, 4:20 am
You can assign scoreboard values to entities using
/scoreboard players set @e[type=Creeper] score 1
for example.

They basically act exactly like a normal player in the scoreboard.
Edit Reply Delete
  • Moose
  • Level 1
  • New Network
  • August 4, 2014, 10:25 am
I'm pretty sure this has so many views and so few diamonds because anybody without an account can google "how to use scoreboard 1.8" and this will pop up pretty near to the top.  It happened with one of my blogs too.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 4, 2014, 10:47 am
That might be true.
Well, still a good xp-farm.
Holy crap, my blog is actually 1st place on google! 
http://gyazo.com/464743074991c10956619a7f76b78aa2
Edit Reply Delete
  • Moose
  • Level 1
  • New Network
  • August 4, 2014, 11:20 am
Edit Reply Delete
  • Moose
  • Level 1
  • New Network
  • August 4, 2014, 11:14 am
Yeah, man.  It's great.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 4, 2014, 11:22 am
Still not 1st place ;D
Edit Reply Delete
  • Moose
  • Level 1
  • New Network
  • August 4, 2014, 11:41 am
Hard to beat the wiki, lol.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 4, 2014, 11:48 am
Well, I did beat the wiki....with higher quality and information...and ease to use.
Edit Reply Delete
  • Moose
  • Level 1
  • New Network
  • August 4, 2014, 12:02 pm
The wiki didn't have a specific page dedicated towards only the scoreboard though, lol.
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • August 4, 2014, 12:05 pm
Yes, it has actually.
There is a list, just like mine, with all commands n' stuff, but of course it is not as good as mine... ;D
Edit Reply Delete
man this is so useful. I was so confused with /scoreboard players operation...
Edit Reply Delete
  • GalePlay
  • Level 14
  • Journeyman Dragonborn
  • March 11, 2014, 5:16 am
Hi,
I'm doing some stuff with the scoreboard objective "stat.mineBlock.stained_glass" but I don't know how to set the color of the stained glass. Do you know how I can do this? Would be nice :)
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • March 11, 2014, 7:25 am
I'm sorry, but it is not possible to specify the damage value in this case.
Edit Reply Delete
  • GooDGrounD
  • Level 10
  • Journeyman Princess
  • March 4, 2014, 6:17 am
Omg Thnx Diamond For You!
Edit Reply Delete
  • DragonhuntIII
  • Level 19
  • Journeyman Dragonborn
  • March 4, 2014, 5:55 am
Looks good
Edit Reply Delete
Thx for helping me make my pvp map!
Edit Reply Delete
  • Headaxe
  • Level 50
  • Grandmaster Unicorn
  • July 14, 2013, 11:39 am
No problem ;)
Edit Reply Delete
Oh btw, your english wasn't that bad.
Edit Reply Delete

1 - 50 of 77

Show Comments