Minecraft – tellraw command with selector command doesnt’ work

minecraft-commandsminecraft-java-edition

Can someone help me by adding a selector into this command? I want @p[score_quits_min=1] to be added into this:

/execute @a[score_quits_min=1] ~ ~ ~ tellraw @a [{"text":"WELCOME", "color":"gold"} *added right here* {"text":"TO THE REALM", "color":"gold"}]

I have the command connected to a clock and another command block with this command connected into the /execute command:

/scoreboard players set @a[score_quits_min=1] quits 0

I have been searching for an answer for a long time but never found one.

Best Answer

The selector string holds a selector to be parsed. It is exclusive with the the text, translate, and score tags, so it must not be mixed with them. Small example:

/tellraw @a ["Closest player to command block: ",{"selector":"@p"}]

Inserting into your command:

/execute @a[score_quits_min=1] ~ ~ ~ tellraw @a [{"text":"WELCOME", "color":"gold"},{"selector":"@p[score_quits_min=1]"},{"text":"TO THE REALM", "color":"gold"}]

Related Solutions

Minecraft – Why won’t this redstone and command block setup work like the other one

There is this one character (I don't know what it is yet, either), that sometimes, somehow, makes its way into commands. Try going to the beginning of your /testfor command, and holding -> until you reach the end. There may be a spot where your cursor stops moving, and there should be a zero-width invisible character there. It shows up in regular editing software, I always check if my commands aren't working.

Minecraft – Different commands select different entities (with the same target selector)

In the source there are couple functions that attempt to obtain a target: one that selects players first (and if it fails, falls back to the other function), and one that does not have a bias towards any type. Every command must choose which one to use when it has a selector.

However, player bias will only occur if the selector itself is @p or @r (without c being changed) or the c parameter is set to value of exactly "1". If so, the selector won't be processed yet and the command class itself will use one of those functions to process it. Otherwise, the selector is processed first with no bias and then the command is processed for each target found, being handed the already-obtained target (and not a selector to process).

Almost all /scoreboard commands use the player bias function, except for /scoreboard players tag ... and /scoreboard teams join .... The stored selector for CommandStats also uses it.

The only way to prevent it from targeting players is to exclude players from selection:

/execute @e[type=ArmorStand] ~ ~ ~ detect ~ ~-1 ~ stone 0 scoreboard players set @e[type=!Player,c=1] myObj 1

This does mean that if you want a nested /scoreboard command or CommandStats to still target all entities including players, you'd have to create two copies: one for players and one for non-player entities:

/execute @e[type=!Player] ~ ~ ~ /scoreboard players set @e[type=!Player,c=1] OBJ 1
/execute @a ~ ~ ~ /scoreboard players set @a[c=1] OBJ 1

Or:

/stats entity @e[type=!Player] set SuccessCount @e[type=!Player,c=1] OBJ
/stats entity @a set SuccessCount @a[c=1] OBJ

Best Answer

Related Solutions

Minecraft – Why won’t this redstone and command block setup work like the other one

Minecraft – Different commands select different entities (with the same target selector)

Related Topic