lennart van hirtum

Updated for 15w47c & updated tellraws to strict JSON

Before you make a bugreport, please first make sure that your command is indeed correct, remove the quote behind the first selector

The whole point of the /trigger comand is to allow a non OP player to set certain scores to trigger other systems through books/chat. Also there is no security risk as in order for a player to be able to run the command, the scoreboard must be of the type trigger and the player must also first be enabled.

Still an issue in minecraft 1.8.3

Still an issue in the current version of minecraft: 1.8.2-pre6

Still an issue in the current version of minecraft: 1.8.2-pre4

I have the same problem, but only if i put my render distance to 6 or higher

Still an issue in the current version of minecraft: Minecraft 1.8.2-pre1

Not yet fixed, dupe of MC-50166

Confirmed for minecraft 1.8.1

Please reopen as this is still an issue in the current version of minecraft: 1.8.1

confirmed for MC 1.8.1

The How to reproduce is incorrect, it should be:

Create a flat world, preferably redstoneready so that no animals can spawn
Spawn a Pig

/scoreboard objectives add temp dummy
/scoreboard players set @e[type=Pig] temp 5
/scoreboard players set @p temp 5
/tellraw @a {score:{name:'@p',objective:'temp'}}
/tellraw @a {score:{name:'@e[type=Pig,c=1]',objective:'temp'}}

The first tellraw outputs the number 5

The second tellraw outputs an empty line

As you can see it works with selectors, but it just works for players and not for other entity's
Also, this is still an issue in the latest version of minecraft: (Minecraft-1.8.1)

reproduced in Minecraft 1.8.1

reproduced in 1.8.1-pre5

reproduced in 1.8.1-pre4

have been able to reproduce with other entity's

confirmed

make sure you use the correct syntax, i usually just edit the part in the middle were it sais "minecraft:bedrock,2*minecraft:dirt,minecraft:grass" also, before leaving the screen where you input your preset, make sure you copy your preset first, as it gets reset when you come back to the page

a * in a command targets all listed objects with a score value, score:{} parameter can only accept a single player, it will result in an error, after some testing i discovered that just using a selector causes the said bug, when using a direct name the problem is resolved, so to get around this you would just copy @p's score to a dummy player and use it instead