Minecraft /scoreboard Command
Tracks, modifies, and displays custom objectives, player scores, timers, and statistics for game logic, economy, and leaderboard systems.
Version Compatibility
Command Syntax
/scoreboard objectives (add|remove|list|setdisplay|modify) ... | /scoreboard players (add|set|remove|reset|get|list|operation|enable) .../scoreboard objectives (add|remove|list|setdisplay) ... | /scoreboard players (add|set|remove|reset|list|operation|random) ...Arguments Explained
categoryobjectives / playersRequiredSpecify whether managing objective definitions or player score values.
actionadd / set / remove / setdisplay / operationRequiredThe score operation to perform.
objectiveStringRequiredObjective name identifier (e.g. Coins, Deaths, Timer).
criteria (Java/Bedrock)Criteria StringTracking metric: dummy (manual score), deathCount, health, or playerKillCount.
Practical Examples
/scoreboard objectives add Coins dummy "Gold Coins"Creates a custom money currency objective called "Coins".
Setting up economy.
/scoreboard objectives setdisplay sidebar CoinsDisplays the Coins leaderboard on the right sidebar of the screen.
HUD leaderboard display.
/scoreboard players add @a Coins 50Gives 50 coins to every online player.
Quest rewards.
/scoreboard objectives add Deaths deathCount "Total Deaths"Java: Automatically tracks and displays player deaths.
Survival death counters.
/scoreboard players operation @p Balance += @p RewardAdds the value of the Reward score directly into the Balance score.
Arithmetic score operations.
Common Mistakes
Mistake:
Forgetting to set a display slot with /scoreboard objectives setdisplay
Fix:
The objective tracks scores in the background, but will not appear on screen until you set the display slot: /scoreboard objectives setdisplay sidebar <name>
Mistake:
Using non-dummy criteria on Bedrock Edition
Fix:
Bedrock only supports "dummy". You must increment scores using command blocks instead.
Mistake:
Using real player names for system variables instead of fake players like #timer
Fix:
Names starting with # never appear on sidebars or tab lists, keeping leaderboards clean.
Java vs Bedrock Differences
Java Edition supports dozens of built-in criteria (e.g. deathCount, health, custom mined item statistics). Bedrock Edition only supports the "dummy" criteria, requiring manual command block increments for stats.
Command Block Usage & Automation
The heart of Minecraft logic engines. To build a game timer, create a dummy objective "/scoreboard objectives add Timer dummy", run a Repeating Command Block with "/scoreboard players add #global Timer 1", and test it with "/execute if score #global Timer matches 200.. run say 10 Seconds Elapsed!".
Useful Tips
Target selectors can test scores directly: @a[scores={Coins=100..}] targets players with 100 or more coins.
Use fake player names (like #global or #timer) as global memory registers for map logic.
Important Notes
In Bedrock Edition, the only supported criteria is `dummy`. Java Edition supports dozens of automatic criteria including `deathCount`, `playerKillCount`, `health`, and item craft/mine statistics.
Frequently Asked Questions
Can I reset all scores for an objective?
Yes! Run /scoreboard players reset * <objective> to clear scores for all players.
How do I hide scores from the sidebar?
Run /scoreboard objectives setdisplay sidebar without specifying an objective to clear the slot.
Ready to build your command?
Use our interactive generator to create error-free /scoreboard commands with a visual interface.
Open Command Generator