The behavior in 1.8 was: No score-update nor selector-update on chunk update or reload. The savegame and blockdata contains a field "value" with the value at the creation time. Therefore for loading the sign, the scoreboard is not required. The "value"-field is simply showen.
Please fix this to the way it works in 1.8. I want to hold "old" scores in signs. These should be persistent, because the objective will change during playing the map, and the old score should be displayed.
Also, in 1.9 the value-data is updated while cloning a sign. In 1.8, the data remains the old score (from "value").
If you want so - to force reload the displayed score - you could send a blockdata-update (like in 1.8). Or add a tag like "resolved" for books to get both behaviors.
warco311
I've tried the following:
In *.mca-Savegame and as result of an empty blockdata request (/blockdata x y z {}), I've got in 1.8 and 1.9:
Text1:{"extra":["hi"],"text":""}
Text2:{"extra":[{"score":{"name":"playername","objective":"hi","value":"100"}}],"text":""}
The behavior in 1.8 was: No score-update nor selector-update on chunk update or reload.
The savegame and blockdata contains a field "value" with the value at the creation time.
Therefore for loading the sign, the scoreboard is not required. The "value"-field is simply showen.
Please fix this to the way it works in 1.8. I want to hold "old" scores in signs. These should be persistent, because the objective will change during playing the map, and the old score should be displayed.
Also, in 1.9 the value-data is updated while cloning a sign. In 1.8, the data remains the old score (from "value").
If you want so - to force reload the displayed score - you could send a blockdata-update (like in 1.8). Or add a tag like "resolved" for books to get both behaviors.