一张截图,记分板在屏幕右边。
记分板(scoreboard)系统是一套复杂的游戏机制,由命令进行控制。记分板主要是给地图制作者和服务器管理员使用的,它能用多种方式追踪、设置和列举玩家的分数。
译名分歧
由于记分板中的一些组件缺少对应的标准译名,在不同的地方可能会对某些组件有不同的翻译,但它们所指的都是同样的东西。本文全部采用游戏内翻译。以下是常见的译名分歧:
| 原文 | 游戏内译名 | 游戏曾用译名 | 社区常见译名 |
|---|---|---|---|
| Objective | 目标 | 对象 | 变量 |
| Criteria | 准则 | 判据 | |
| Trigger | 触发器/触发型 | ||
| (Display) Slot | (显示)位置 | 显示区 |
目标
目标包括三个主要的参数:名称 (name)、显示名称(display name)、准则(criteria)。目标从多种方面追踪玩家的分数,并以整数显示,分数范围为-2,147,483,648至2,147,483,647。
目标的名称在内部使用,用于在命令、目标参数、文件格式中进行引用。目标区分大小写并且只能为单个的单词。
与之相反,目标的显示名称可以由多个单词组成,用于在不同场合中进行外部的显示。显示名称也区分大小写,且可以重复。
目标的准则决定了其行为,首要的影响在于追踪的事物。可用的准则列表见下。
玩家的在任意目标上的分数可由命令修改,除非该分数为只读的(即不可改变)。分数可以增加或减少特定的数值,或者设置为一个特定的数值。对于基于统计和成就的目标来说,目标本身是可以修改的;然而,真实的统计或成就数据并不会改变——目标会在统计或成就改变时继续更新。
命令也能用于检测玩家在任意目标上的分数,其中需要用到参数score_name和score_name_min。在这些参数中,name是要检测的目标的内部名称。score_name选择出分数小于等于特定值的玩家,而score_name选择出分数大于等于特定值的玩家。
举例来说,在命令方块中输入“testfor @p[score_deaths=5,score_deaths_min=1]”即制作一个可以当如下情况方能输出的红石比较器: 设目标deaths的准则为“deathCount(死亡数量)”,则deaths会选择死亡次数至少为1次,最多为5次的玩家。
准则
| 准则 | 描述 | 可否编辑 |
|---|---|---|
| dummy(虚拟型) | 只能通过命令修改分数,诸如死亡等游戏行为并不能修改分数。这可以被用来制作事件的标记、映射和货币。 | 是 |
| trigger(触发器) | 只能通过命令修改分数,诸如死亡等游戏行为并不能修改分数。 一个使用trigger作为准则的目标可以被玩家利用命令/trigger来设置/增加/减少分数。如果/trigger命令没有对玩家“启用”,则使用/trigger命令会失败,并且成功使用过一次此命令后该命令将重新被关闭。应当指出/trigger命令可以在作弊被关闭的情况下被非管理员的普通玩家使用。这在玩家经由/tellraw进行输入时会非常有用。
|
是 |
| deathCount(死亡次数) | 当玩家死亡时,分数会自动增加。 | 是 |
| playerKillCount(杀人数量) | 当玩家杀死其他玩家时分数会自动增加。 | 是 |
| totalKillCount(杀怪数量) | 当玩家杀死其他生物时分数会自动增加。 | 是 |
| health(生命值) | 普通玩家会在0~20之间。代表玩家拥有红心数量的两倍。在玩家的血量第一次改变前会显示为0。额外的血或者伤害吸收的血也会计算在血量中,也就是说当获得了伤害吸收或者生命提升的信标效果后生命值可以超过20。 | 否 |
| xp(经验值) | 对应玩家拥有的经验值。 | 否 |
| level(等级) | 对应玩家当前的经验等级. | 否 |
| food(饱和度) | 在0~20之间,代表玩家拥有的饱和度。在玩家的饱和度第一次改变前会显示为0。 | 否 |
| air(空气值) | 在0~300之间;代表潜水的玩家所存余的空气,对应玩家的空气NBT标签。 | 否 |
| armor(盔甲值) | 在0~20之间;代表玩家拥有的盔甲值。在玩家第一次更换盔甲前会显示为0 | 否 |
有些准则使用了统计和成就系统来组成混合准则。[1]不同于上面的简单准则,混合准则有多个部分,使用点号来分隔(".")。例如 "stat.entityKilledBy.Zombie"是一种混合准则,当玩家被僵尸杀死的时候才会增加。[2]
下面是已知的混合准则:
| 基础准则 | 描述 | 可否编辑 | 次级准则数量 | ||||
|---|---|---|---|---|---|---|---|
| achievement(成就) | 可用的次级准则如下:"acquireIron", "bakeCake", "blazeRod", "bookcase", "breedCow", "buildBetterPickaxe", "buildFurnace", "buildHoe", "buildPickaxe", "buildSword", "buildWorkBench", "cookFish", "diamonds", "diamondsToYou", "enchantments", "exploreAllBiomes", "flyPig", "fullBeacon", "ghast", "killCow", "killEnemy", "killWither", "makeBread", "mineWood", "onARail", "openInventory", "overkill", "overpowered", "portal", "potion", "snipeSkeleton", "spawnWither", "theEnd"和"theEnd2"。数量取决于玩家获得此成就的次数(例如,当一个玩家捡起3块木头,他在使用"achievement.mineWood"准则的目标上的分数会变成3。) | 是 | 34 | ||||
| stat(统计) | 基于玩家的统计来计数,可用的次级准则有:"animalsBred", "armorCleaned", "aviateOneCm", "bannerCleaned", "beaconInteraction", "boatOneCm", "brewingstandInteraction", "cakeSlicesEaten", "cauldronFilled", "cauldronUsed", "chestOpened", "climbOneCm", "craftingTableInteraction", "crouchOneCm", "damageDealt", "damageTaken", "deaths", "dispenserInspected", "diveOneCm", "drop", "dropperInspected", "enderchestOpened", "fallOneCm", "fishCaught", "flowerPotted", "flyOneCm", "furnaceInteraction", "hopperInspected", "horseOneCm", "itemEnchanted", "jump", "leaveGame", "minecartOneCm", "mobKills", "noteblockPlayed", "noteblockTuned", "pigOneCm","playOneMinute", "sleepInBed", "sprintOneCm"和"walkOneCm"。 当一个玩家完成次级准则中的行为,分数会自动增加。 | 是 | 40 | ||||
| stat.craftItem(统计.物品合成) | 次级准则是合成物品或方块的ID(例如"stat.craftItem.1")或者ID名(例如"stat.craftItem.minecraft.stone",注意使用ID名时必须要加"minecraft." )。只有可合成或可熔炼的方块和物品名才会被接受。这个数据会在被合成物品移出熔炉, 合成台或者物品栏中的合成区域时增加。点击拿走物品会使数据加1,但是使用shift来拿走只会使数据加2。
|
是 | 199 (398)[note 1] | ||||
| stat.useItem(统计.使用物品) | 次级准则是方块或物品的ID数和ID名(如"stat.useItem.1"和"stat.useItem.minecraft.stone")。大部分方块和物品都被接受,除了某些不存在物品形式的方块。
物品的使用次数会随着玩家使用的方块或物品的次数增加而增加。"使用"的定义是:
然而,分数值在以下情况不会增长:将物品用于生物上,无论是命名,驯服,喂养,繁殖,上鞍,套绳,剪羊毛,挤奶,或是通过哞菇取得蘑菇煲;或直接穿上盔甲;或皮革盔甲经由炼药锅染色;以及以上提到的具体例子。 |
是 | 318 (636)[note 1] | ||||
| stat.breakItem(统计.用坏物品) | 次级准则是有耐久度的物品ID (比如 "stat.breakItem.256") 或 ID名 (比如 "stat.breakItem.minecraft.bow")。
当耐久度耗尽时数值增加。耐久度在物品损耗耐久的条件满足时耗尽,且耐久为0时的第一次使用后耐久度变为负数。 |
是 | 50 (100)[note 1] | ||||
| stat.mineBlock(统计.挖掘物品) | 次级准则为方块的ID (比如 "stat.mineBlock.1") 或ID名(比如 "stat.mineBlock.minecraft.stone")。大多数方块都可接受,不可开采的或技术性方块除外。
玩家挖掘方块时数值增加。 "挖掘" 定义为玩家能使方块掉落物品的破坏方式,除非方块不会掉落,比如 玻璃,或是会创造出另外一个方块,比如 冰。创造模式下该数值不会增加,且 doTileDrops 为false时也会计数。 |
是 | 135 (270)[note 1] | ||||
| stat.pickup | 次级准则为方块或物品的ID (比如 "stat.pickup.1") 或ID名(比如 "stat.pickup.minecraft.stone")。Increments when a player picks up a dropped item. | 是 | 392 | ||||
| stat.drop | 次级准则为方块的ID (比如 "stat.drop.1") 或ID名(比如 "stat.drop.minecraft.stone")。当玩家使用丢弃键丢弃物品时分数值增加。 | 是 | 392 | ||||
| stat.killEntity(统计.杀死实体) | 次级准则为实体的名字。合法的名字为:"Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "Endermite", "EntityHorse", "Ghast", "Guardian", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "PolarBear", "Rabbit", "Sheep", "Shulker", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf"和"Zombie"。在玩家杀死特定的实体时增加。 | 是 | 29 | ||||
| stat.entityKilledBy(统计.被实体杀死) | 次级准则为实体的名字。合法的名字为: "Bat", "Blaze", "CaveSpider", "Chicken", "Cow", "Creeper", "Enderman", "Endermite", "EntityHorse", "Ghast", "Guardian", "LavaSlime", "MushroomCow", "Ozelot", "Pig", "PigZombie", "PolarBear", "Rabbit", "Sheep", "Shulker", "Silverfish", "Skeleton", "Slime", "Spider", "Squid", "Villager", "Witch", "Wolf"和"Zombie"。在玩家被特定的实体杀死时增加。 需要注意的是,如果使用被动型生物的名称,数值永远不会增加,因为它们无法伤害拥有记分板的实体。然而当兔子和鸡分别属于“杀手兔”和“鸡骑士”时,它们可以造成伤害。 |
是 | 29 | ||||
| teamkill(团队击杀数) | 次级准则是队伍的颜色。合法的颜色名为: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". 在玩家杀死特定颜色的队伍成员时增加。 | 是 | 16 | ||||
| killedByTeam(团队被击杀数) | The sub-criteria are the color of a team. Valid colors are: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". 在玩家被特定颜色的队伍成员杀死时增加。 | 是 | 16 |
以"列表"形式显示的某一玩家在这一目标下获得了2点分数,同时在"侧边栏"模式中则为某一显示名称为"Quest Points"的目标,其中该玩家没有获得分数。
显示位置
通过命令/scoreboard objectives setdisplay(参见记分板命令),实体关于某个目标的分数能在游戏中特定的“位置”显示出来。每个“显示位置(Display Slot)”可以显示一个目标,而多个显示位置可以被用于相同或不同的目标。
| 位置 | 描述 |
|---|---|
| list(列表) | 在tab键菜单(显示在线玩家)中显示分数,数字颜色为黄色。分数的目标名称是不可见的。这个数字在单人模式下也会显示出来。 |
| sidebar(侧边栏) | 在屏幕的右侧显示。显示内容为玩家高分排行榜,最上方显示目标的显示名称(display name)。应当指出,如果在该目标下存在一定分数,玩家即使离线,也会在"侧边栏"中进行显示,而没有被追踪的玩家不会被显示。除此之外,名称以#开头的虚拟玩家在任何情况下都不会在侧边栏显示。 |
| sidebar.team.<color>(侧边栏.队伍.<颜色>) | 专用于队伍的侧边栏显示位置,共有16种。这类侧边栏的相关操作与一般侧边栏相同,但只会显示给指定队伍颜色的玩家。(例如,"sidebar.team.green"只显示给绿队的玩家)。可用的颜色有: "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow"和"white"。 |
| belowName(名称下方) | 在玩家的名称之下,头部之上显示分数,并在其后显示目标的显示名称。在10格之外或玩家潜行时会隐藏。单人模式下不可见。 |
Tags
Scoreboard tags are a simple list of single-word strings stored directly in the Tags data tag of an entity. As with objectives, tags are case-sensitive.
Target selectors can be used to check whether an entity has a tag with the "tag" argument; the "!" character may be placed before a name to check for entities that do not have the tag. For example, inputting /testfor @p[tag=banana] into a command block will provide comparator output if a player is tagged with "banana". Similarly, /testfor @p[tag=!banana] will provide output for players who are not tagged "banana".
To test for multiple tags, use the data tag "Tags". For example, /testfor @p {Tags:["banana","apple"]} will check for a player that has both the "apple" and "banana" tags.
Teams
Teams are a combination of name, display name, prefix, suffix, friendly fire options, and a list of players who are on the team.
A team's name is used internally, for referencing in commands, target arguments, and in the file format. It is case-sensitive and must be a single word.
Conversely, the display name of a team can be multiple words, and is displayed publicly in various situations. It is also case-sensitive, and does not have to be unique.
A team's prefix and suffix are inserted before and after the names of players on the team, respectively. Without using external editors, the only possible prefixes are formatting codes for team colors, and the only possible suffix is the reset code (so characters after a player's name aren't formatted). Prefixes and suffixes will be added to the names of players in chat, the active players list, the sidebar, and above their heads. Without an in-game option, third-party software may be required to edit them.
The friendly fire option allows control of whether or not members of a team are able to harm each other. Its default mode, true, makes no changes to PvP mechanics - ergo, players can harm their teammates. When set to false, however, it prevents players on the same team from causing damage to each other with melee attacks, bows, and Splash Potions of Harming. Note that players on the same team may still inflict negative status effects on each other with potions, even if friendly fire is false.
It is important to note that each individual player can only be on one team; teams cannot share players.
Commands can be used to check whether a player is on a team with the "team" argument; the "!" character may be placed before a name to check for players not on the team. For example, inputting /testfor @p[team=red] into a command block will provide comparator output if a player is on the "red" team. Similarly, /testfor @p[team=!red] will provide output for players who are not on "red". Also, /testfor @p[team=!] will check for all players on a team, while /testfor @p[team=] will check for those without a team.
Command reference
Objectives commands
| Command | Description | Success Conditions[note 1] |
|---|---|---|
| scoreboard objectives list | Lists all existing objectives, with their display name and criteria. | The scoreboard must have at least one objective. |
| scoreboard objectives add <name> <criteria> [display name...] | Creates a new objective with the internal name name, specified criteria, and the optional display name. Without a specified display name, it will default to name. See above section for the meaning of these properties. All arguments are case-sensitive. | name must not be used by an existing objective, and must be at most 16 characters. criteria must be a valid criteria type. display name must be at most 32 characters. |
| scoreboard objectives remove <name> | Deletes all references to the objective with name in the scoreboard system. Data is deleted from the objectives list, player scores, and if it was on a display list, it will no longer be displayed. | name must be an existing objective. |
| scoreboard objectives setdisplay <slot> [objective] | Displays score info for objective in the specified slot. Valid slots are listed and described in Display Slots. Note that the objective parameter is optional: if no objective is provided, this display slot is cleared (returned to its default state). | objective must exist, if it is specified. slot must also exist. Note that clearing an empty slot will still succeed. |
Players commands
| Command | Description | Success Conditions[note 1] |
|---|---|---|
| scoreboard players list [playername] | Displays all players who are tracked, in some way, by the scoreboard system. The optional playername parameter can be used to display all scores of a particular player, and "*" (an asterisk) in place of playername will display all scores for all players tracked by the scoreboard system. | playername must have recorded scores, if specified. If no playername is specified, there must be at least one tracked player on the scoreboard. |
| scoreboard players set <player> <objective> <score> [dataTag] | Sets the player's score in objective to score, overwriting the previous score if it exists. "*" may be used in place of player to represent every player tracked by the scoreboard. | objective must exist and cannot be read-only, and score must be between -2,147,483,648 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist. If player exists and a dataTag is specified, player must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers. |
| scoreboard players add <player> <objective> <count> [dataTag] | Increments the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard. | objective must exist and cannot be read-only, and count must be between 1 and 2,147,483,647, inclusive. Note that player does not need to be online or even exist. If player exists and a dataTag is specified, player must match dataTag. Note that dataTag must define the type of tag such as {powered:1b} if looking for powered creepers. |
| scoreboard players remove <player> <objective> <count> [dataTag] | Decrements the player's score in objective by count. "*" may be used to represent all players tracked by the scoreboard. | |
| scoreboard players reset <player> [objective] | Deletes score or all scores for player. If objective is specified, only that objective is cleared; otherwise this applies to all objectives. Note this does not merely set the score(s) to 0: it removes the player from the scoreboard altogether (or for the given objective). "*" may be used to represent all players tracked by the scoreboard. | Always succeeds, even on players who are not on the scoreboard. |
| scoreboard players enable <player> <trigger> | Enables player to use the /trigger command on the specified trigger objective. Until this has been done, player's attempts to /trigger that objective will fail. Once they have used the /trigger command on it, it will be disabled again. "*" may be used to represent all players tracked by the scoreboard. | trigger must be an objective of the criteria "trigger". |
| scoreboard players test <player> <objective> <min> [max] | Outputs whether or not player's score in objective is within the range min to max (inclusive). If not specified or if "*" is used, max defaults to 2,147,483,647. Using a "*" for min means -2,147,483,648. "*" may be used to represent all players tracked by the scoreboard. | objective must exist, and player's score in it must exist and be at least min and no greater than max. Note that player does not need to be online or even exist. |
| scoreboard players operation <targetName> <targetObjective> <operation> <selector> <objective> | Applies an arithmetic operation altering targetName's score in targetObjective, using selector's score in objective as input.
<operation> may be:
In all cases except "><", selector's score in objective will remain unchanged. "*" may be used in place of either targetName or selector (but not both) to represent all players tracked by the scoreboard. |
objective and targetObjective must exist, targetObjective cannot be read-only, and all requested targets/selectors must have scores in the specified objectives (if some do and some do not, the operation will succeed only for the combinations where both the target and the selector have a score). Note that targetName does not need to be online or even exist. |
Tags commands
| Command | Description | Success Conditions[note 1] |
|---|---|---|
| scoreboard players tag <player> add <tagName> [dataTag] | Adds a tag - tagName which can be based on a certain dataTag to/from a player. "*" may be used in place of player to represent all players tracked by the scoreboard, provided the players exist and are online. | |
| scoreboard players tag <player> remove <tagName> [dataTag] | Removes a tag - tagName which can be based on a certain dataTag to/from a player. "*" may be used in place of player to represent all players tracked by the scoreboard, provided the players exist and are online. | Tags that are to be removed must exist. |
| scoreboard players tag <player> list | Lists all tags the player has. "*" may be used in place of player to represent all players tracked by the scoreboard, provided the players exist and are online. |
Teams commands
| Command | Description | Success Conditions[note 1] |
|---|---|---|
| scoreboard teams list [teamname] | Lists all teams, with their display names and the amount of players in them. The optional teamname parameter can be used to display all players on a particular team. | If teamname is specified, it must exist and must have players. If no teamname is specified, there must be at least one registered team on the scoreboard. |
| scoreboard teams add <name> [display name...] | Creates a team with the given name and optional display name. | name must not be used by an existing team, and must be at most 16 characters. display name must be at most 32 characters. |
| scoreboard teams remove <name> | Deletes the named team from the scoreboard system. | name must be an existing team. |
| scoreboard teams empty <name> | Removes all players from the named team. | name must be an existing team, and the team must have at least one player. |
| scoreboard teams join <team> [players...] | Assigns the specified players to the specified team. If no player is specified, the player running the command joins the team. "*" may be used to represent all players tracked by the scoreboard. | team must exist. Note that the named players do not need to be online or even exist, and can even already be on the team. |
| scoreboard teams leave [players...][note 2] | Makes the specified players leave their teams. If no player is specified, the player running the command leaves their team. "*" may be used to represent all players tracked by the scoreboard. | Each player must be on a team - it is possible to get a partial success and partial failure, but a command block will report only the failure. |
| scoreboard teams option <team> color <value> | Will color the name of all players on this team in chat, above their head, on the Tab menu, and on the sidebar. Also changes the color of the outline of the players caused by the Glowing effect. Valid color values are "black", "dark_blue", "dark_green", "dark_aqua", "dark_red", "dark_purple", "gold", "gray", "dark_gray", "blue", "green", "aqua", "red", "light_purple", "yellow", and "white". Another valid value is "reset" (names show in default color and formatting). | team must exist, and value must be a valid value. |
| scoreboard teams option <team> friendlyfire <true|false> | The default setting, true, has no impact on PvP mechanics. When set to false, players on this team cannot harm each other with melee, bow, or Splash Potion of Harming attacks, but may still inflict negative status effects on each other. Does not affect non-player entities on a team. | team must exist, and the setting must be "true" or "false". |
| scoreboard teams option <team> seeFriendlyInvisibles <true|false> | When set to true, players on this team will see invisible teammates (and themselves) as semi-transparent instead of completely invisible. Defaults to true. | team must exist, and the setting must be "true" or "false". |
| scoreboard teams option <team> nametagVisibility <never|hideForOtherTeams|hideForOwnTeam|always> | Controls the visibility of nametags for players on the given team, and defaults to "always". When set to "never", no nametags will show above any player on the given team. When set to "hideForOtherTeams", the nametags of players on the given team will be hidden to other players not on the team. When set to "hideForOwnTeam", only nametags of other players on one's own team will be hidden. When set to "always", all nametags will be visible. | team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always". |
| scoreboard teams option <team> deathMessageVisibility <never|hideForOtherTeams|hideForOwnTeam|always> | Controls the visibility of death messages for players on the given team, and defaults to "always". When set to "never", no death messages will appear in chat for any player on the given team. When set to "hideForOtherTeams", only the death messages of players on other teams will be hidden. When set to "hideForOwnTeam", only death messages of other players on one's own team will be hidden. When set to "always", all death messages will appear in chat. | team must exist, and the setting must be "never", "hideForOtherTeams", "hideForOwnTeam", or "always". |
| scoreboard teams option <team> collisionRule <always|never|pushOwnTeam|pushOtherTeams> | Controls the way the players on the team collide, defaults to "always". When set to "never", players on that team will never collide with players or mobs. When set to "pushOwnTeam", players will only push other players on their team and mobs. When set to "pushOtherTeams", players will only push players on opposing teams. When set to "always", all players and mobs will be pushed. | team must exist, and the setting must be "never", "pushOwnTeam", "pushOtherTeams", or "always". |
NBT format
The file scoreboard.dat in the 'data' folder of a Minecraft world stores the scoreboard data for that world as a GZip'd NBT file:
- The root tag.
- data: The scoreboard data.
- Objectives: A list of compound tags representing objectives.
- An objective.
- CriteriaName: The criteria of this objective.
- DisplayName: The display name of this objective. If none was specified during the objective's creation, this will be identical to the Name tag below.
- Name: The internal name of this objective.
- RenderType: The type of data to store. Defaults to "integer".
- An objective.
- PlayerScores: A list of compound tags representing scores tracked by the scoreboard system.
- A tracked player/objective pair with a score.
- Score: The score this player has in this objective.
- Name: The name of the player who has this score in this objective.
- Objective: The internal name of the objective which this player has this score in.
- Locked: 1 or 0 (true/false) - false if this objective is "enabled". Only meaningful for objectives with the criteria "trigger", where this must be false before a player can use the /trigger command on it.
- A tracked player/objective pair with a score.
- Teams: A list of compound tags representing teams.
- A Team.
- AllowFriendlyFire: 1 or 0 (true/false) - true if players on this team can harm each other.
- SeeFriendlyInvisibles: 1 or 0 (true/false) - true if players on this team can see invisible teammates.
- NameTagVisibility: The value of the nametagVisibility option of this team.
- DeathMessageVisibility: The value of the deathMessageVisibility option of this team. Valid options are: never, hideForOtherTeams, hideForOwnTeam, always
- CollisionRule: The value of the collisionrule option of this team. Valid options are: always, pushOwnTeam, never, pushOtherTeams
- DisplayName: The display name of this team. If none was specified during the team's creation, this will be identical to the Name tag below.
- Name: The internal name of this team.
- Prefix: The prefix prepended to names of players on this team. Ordinarily, it is a Formatting Code.
- Suffix: The suffix appended to names of players on this team. Ordinarily, it is the reset code, "§r", to prevent formatting from spilling over, but it may be blank if prefix is also blank.
- TeamColor: The text-based color ("black", "dark_blue", etc.) given to the team. Does not exist if no color is set.
- Players: A list of names of players on this team.
- The name of a player on this team.
- A Team.
- DisplaySlots: A set of slots which are displaying specific objectives. If a slot is empty, its tag is not present.
- slot_0: The internal name of the objective displayed in the "list" slot.
- slot_1: The internal name of the objective displayed in the "sidebar" slot.
- slot_2: The internal name of the objective displayed in the "belowName" slot.
- slot_3: The internal name of the objective displayed in the "sidebar.team.black" slot.
- slot_4: The internal name of the objective displayed in the "sidebar.team.dark_blue" slot.
- slot_5: The internal name of the objective displayed in the "sidebar.team.dark_green" slot.
- slot_6: The internal name of the objective displayed in the "sidebar.team.dark_aqua" slot.
- slot_7: The internal name of the objective displayed in the "sidebar.team.dark_red" slot.
- slot_8: The internal name of the objective displayed in the "sidebar.team.dark_purple" slot.
- slot_9: The internal name of the objective displayed in the "sidebar.team.gold" slot.
- slot_10: The internal name of the objective displayed in the "sidebar.team.gray" slot.
- slot_11: The internal name of the objective displayed in the "sidebar.team.dark_gray" slot.
- slot_12: The internal name of the objective displayed in the "sidebar.team.blue" slot.
- slot_13: The internal name of the objective displayed in the "sidebar.team.green" slot.
- slot_14: The internal name of the objective displayed in the "sidebar.team.aqua" slot.
- slot_15: The internal name of the objective displayed in the "sidebar.team.red" slot.
- slot_16: The internal name of the objective displayed in the "sidebar.team.light_purple" slot.
- slot_17: The internal name of the objective displayed in the "sidebar.team.yellow" slot.
- slot_18: The internal name of the objective displayed in the "sidebar.team.white" slot.
- Objectives: A list of compound tags representing objectives.
- data: The scoreboard data.
History
| release | |||||
|---|---|---|---|---|---|
| 1.5 | 13w04a | Added scoreboard. | |||
| 13w05a | Added team-based functionality. | ||||
| 1.7.2 | 13w36a | Added statistic-based objective criteria. | |||
| 1.8 | 14w02a | Entities other than players can now be part of teams and have objective scores. | |||
| 14w06a | Added the trigger and team kill-based objective criteria. | ||||
Added /scoreboard players enable. | |||||
| "*" can be used in a player name argument to represent all players tracked by the scoreboard. | |||||
Added the "objective" argument to /scoreboard players reset. | |||||
| Statistic objective criteria now use named IDs instead of numerical IDs. | |||||
Added the achievement.overpowered objective criterion. | |||||
| 14w07a | Added /scoreboard players operation and /scoreboard players test. | ||||
| Scores for fake players that have a name beginning with "#" won't appear in the sidebar. | |||||
| Added team-specific sidebar display slots. | |||||
Added the nametagVisibility team option. | |||||
| 14w10a | Added the deathMessageVisibility team option. | ||||
Added a dataTag argument to /scoreboard players set, /scoreboard players add, and /scoreboard players remove. | |||||
Added the stat.crouchOneCm, stat.sprintOneCm, and stat.timeSinceDeath objective criteria. | |||||
| 14w25a | Added =, <, and > to /scoreboard players operation. | ||||
| 14w29a | Player/entity names in the sidebar are now secondarily sorted by alphabetical order. | ||||
| 14w30a | Added the stat.talkedToVillager and stat.tradedWithVillager objective criteria. | ||||
| ? | Added >< to /scoreboard players operation. | ||||
| 1.8.2 | Added the cauldronFilled, stat.cauldronUsed, stat.armorCleaned, stat.bannerCleaned, stat.brewingstandInteraction, stat.beaconInteraction, stat.dropperInspected, stat.hopperInspected, stat.dispenserInspected, stat.noteblockPlayed, stat.noteblockTuned, stat.flowerPotted, stat.trappedChestTriggered, stat.enderchestOpened, stat.itemEnchanted, stat.recordPlayed, stat.furnaceInteraction, stat.craftingTableInteraction, stat.chestOpened objective criteria. | ||||
| 1.9 | 15w32a | Added the stat.sneakTime objective criteria. | |||
| 15w32b | Added /scoreboard players tag. | ||||
Added the xp, food, and air objective types. | |||||
| 15w33a | Added the stat.pickup and stat.drop objective criteria.
| ||||
Added the armor, level objective types. | |||||
| 15w36a | Added collisionRule. | ||||
| 15w49a | Added the stat.aviateOneCm objective criteria. | ||||
Issues
Template:Issue list
References
引用错误:组名为“note”的<ref>标签存在,但没有找到相应的<references group="note"/>标签