While checking if the bug MC-98146 still persists, I found that MC-98146 is fixed - apparently.
I don't know if that was intended and has anything to do with e.g. changes made for MC-86164 but I wanted to state it, so that the fix for MC-98146 could be kept (even if it was not intentional), and any changes to Armor Stands, e.g. due to MC-86164, that still have to be made, would not cause the apparent bugfix for MC-98146 to vanish again, as Marker-true-AS rendering their equipment from ALL angles (like Marker:false AS) is very benefitting for the mapmaker-community.
Before 16w38a, the name of AS with Marker-tag set to true is at the BOTTOM of the AS - now when I entered my bugpost-testworld, I found all my Marker-true-AS got their name changed to at the top, like also Marker-false-AS.
Apparently this is caused by Marker-true-AS also now having a hitbox, unlike before 16w38a, and apparently this hitbox was needed in order to fix other AS bugs.
(Pics attached).
I summoned another Marker-true-AS in 16w38a to confirm that the name will appear also at the top, not feet anymore and checked that it is indeed a Marker-true-AS after summoning via
/entitydata @e[type=armor_stand,r=2] {}Summon command:
/summon armor_stand ~ ~1 ~ {CustomName:"Marker True",CustomNameVisible:1,Marker:1b,ArmorItems:[{},{},{},{id:skull,Damage:3,Count:1,tag:{display:{Name:"Meri"},SkullOwner:Meri}}]}If more issues occur due to the AS change, I'll add them of course.
Relates to MC-108008 "Hitbox of Marker:1 Armor Stands lets Passengers appear now ABOVE them"
As for MC-98146: Please do not mark it as "Resolved", until it's sure that the above mentioned change is wanted or why it changed at all.
(Edit: Marked as fixed now, but I really really would love to have a confirmation it was an intentional fix which got simply forgotten to be resolved as fixed by the fixing Dev.)
Suggestion As stated already in MC-108008
A possible solution would be to give us an offset-possibility, e.g. also for/including the displayed custom names on AS.
In MC-108008 the offset-possiblity would apply to the positioning of a passenger-entity as well.
Linked issues
relates to
Attachments
Comments
migrated
migrated
No it did not for Marker-true-AS, if you look at it from certain angles. That's why MC-98146 got entered as bugpost (I already mentioned it in my resolved as WaI-bugpost MC-96853, I quote:
Do not test with ArmorStands that have their Marker-tag set to true |
and that's when Onnowhere made a bugpost out of it, which is MC-98146
migrated
Was just about to edit my comment.
Yes it did render, but mot under every angle.
SunCat
Actually, this is because Marker armor stands now have hitbox (can be seen via F3+b)
migrated
Whatever the reason is, the question remains whether that change was intentional, as well as whether MC-98146 was an intentional fix (and if not, please figure what it fixed and keep it), and if mapmakers could have a problem with the changed display of a custom name if it's visible (which I doubt, as they are most likely to use the Tags tag for targetting the AS nowadays, like already mentioned, and they could use an additional entity for a name display at AS-feet height, if they have to).
Also, if Marker-true-AS having a hitbox now could cause a problem in any way, as being "interactable" which they shouldn't be. I couldn't get them to e.g. being pushed yet by pistons (MC-100398), but I'll keep an eye on it when I got more time 🙂
migrated
Linked a few tickets that were fixed by the change that caused this issue.
migrated
@unknown Thank you!
Also, thanks to the email update notification I got reminded I have to update this bugpost with a bit of new info };]
New issues, apparently caused by the now existing hitbox (which was needed to fix other bugpost(s ) as far as I saw).
migrated
Perhaps it's better to split the issues:
1. Now render dark in a block.
2. Show their name above the armor stand, rather than at the feet.
migrated
@unknown Okay, will do so, but not before I tested it myself in a few hours!
While I do very much trust in what my professional-CBer-colleagues tell me, I don't want to add a bugpost without having confirmed it myself.
Maybe there'll be the next snapshot today as well, so I could directly test there, too, which would save me testing once for today.
This evening then. For now I'll change the title back, but leave in for now the text with the other issue so I can simply copy&paste it later }=)
migrated
Copied my reply from the other bug report, since it's relevant here as well:
Seems intentional. It just relies on the visual appearance of the entity, instead of the collision hitbox. If people need a zero-height marker entity for labeling, they can always use an AreaEffectCloud. If anything, this adds an extra useful feature without taking anything away. It might break some old stuff, but so will the rest of 1.11.
...That is, of course, assuming the new hitbox doesn't interact with things. I'm not in a position to test right now but I'll give it a go tomorrow.
EDIT: Did some more research. It doesn't interact with things. I didn't realize that AECs don't actually do zero-height stacking, though.
migrated
There is a way to solve this,but I hope this bug can be fixed in the next snapshot.
https://youtu.be/XrOXFPy55UU
violine1101
Yes, changing the NoBasePlate tag seems to update the armor stand's name tag position.
michael
The equipment rendered before as well, at least, that I recall.