Charlie Miller

In addition to the custom name not being able to be defined by a scoreboard, lore is also affected by this bug.  (1.14.3 pre-1)

consider a written book with the following pages JSON: 

/give @p written_book{/give @p written_book{pages:[

 "[ {\"text\":\"partA\"}, {\"color\":\"red\",\"text\":\"Redtext\"} ]", "{\"score\":    {\"name\":\"@p\",\"objective\":\"usemap\"}}", "[ {\"score\":{\"name\":\"@p\",\"objective\":\"usemap\"}}, {\"text\":\"Score works properly\"} ]" 

 ], title:Bugtest,author:never2fear,display:{Lore:["{\"text\":\"MC-124008\"}"]}}

and an item spawned with the following identical JSON in its lore field: 

/give @p minecraft:experience_bottle{display:{/give @p minecraft:experience_bottle{display:{ Lore:[

 "[ {\"text\":\"partA\"}, {\"color\":\"red\",\"text\":\"Redtext\"} ]", "{\"score\":{\"name\":\"@p\",\"objective\":\"usemap\"}}", "[ {\"score\":{\"name\":\"@p\",\"objective\":\"usemap\"}}, {\"text\":\"Score is empty string\"} ]" 

]}}

 The book pages' JSON works as intended, where the score, whatever it was when the book was generated, is inserted inline. However, the same expectation does not work with the item lore JSON. An empty string is returned. But no errors. 

Also, This bug entry is out of date - Apparently the armor stand would flat out go through blocks. (in Minecraft 1.10.2) The bug has changed (in minecraft 1.13) such that it will NOT go through the first block that it hits, but any subsequent motion afterwards will ignore all collisions. 

If it's intended, then there is still a bug:

the marker armor stand does not go through a wall until it makes an initial collision

https://www.youtube.com/watch?v=nd2kKTopjdQ&feature=youtu.be

It could be argued that this is intended behavior, because if you're normally comparing scores, and there are no scores, then you don't want the thing to happen anyway.

for instance
/execute unless score @e[type=cows] numSpots >= @e[type=ocelot] numSpots run say "Cats have the most spots!"

in this case, if cows happened to have more spots than ocelots, you wouldnt want the message to run, since it's hard coded that cats have the most spots. Also, in the case that there are no ocelots, you would also not want the command to run since there are no cats to compare to cows.

I suppose that the behavior you hope to produce may be done another way than detecting the null entity

Confirmed - issue resolved in 14w11b