An armor stand which is Marker:1b doesn't collide with a block

Just to be clear, non-marker armor stand (i.e. ones available without commands) are unchanged (still have physics).

@unknown Yes, of course! I wouldn't have thought that would have been changed, as they are used in Survival after all.

Marker-true-AS have always been special and strange (e.g. Marker-true-AS rendered their equipment invisible, sometime in the beginning, which I personally liked though, as then they were not counted towards the entity count, which was rgeat reagrding entity-induced lag).
And there are still a bunch of AS-related bugs (e.g. rendering their equipment dark in solid blocks, creating bubbles underwater etc.).

One can also give oneself a Marker-true-AS and place it manually onto blocks, I checked that as first thing, so it really only seems to apply to AS with Motion.

The appealing thing of armor stands vs. AEC is that AS can carry equipment, so my initial thought was that there could be mapmaking contraptions which involve AS and Motion, especially AS with equipment, but I can't think right off the bat of anything which cannot be solved command-wise.

But like I said, if anyone shows me a contraption which breaks with that change, I'll let you know 🙂

If there is irreplaceable functionality, then don't revert the fixes that were made here, leave it as it was intended to be, and instead come up with an alternative or a different tag to replace old functionality.

@unknown Of course priorities have to be made, benefitting "the greater good", so in no way I personally would ever suggest to revert this or similar changes which seem to affect one group of the community barely, if at all.

I personally favour for the community Survival gameplay over mapmaking, even more so considering that the latter got a vaster amount of tools to play with, and Survival (especially its tech community) fall currently a bit short from my perspective, despite all the new blocks and mechanics added in the past versions.

If there are any serious irreplaceable functionalities for mapmakers, I'm sure there can be other solutions found, and the mapmaking community can deal with that in the meantime.

Regardless, it's always good to ask that question - I did the same also when there were changes affecting solely the Survival community.

Bok, I had a specific use in 1.13.2 that required marker armor stands to have gravity. From what I have tested, forcing the stand to include NoGravity:0b doesn’t revert back to have physics. I used marker stands because falling blocks ride on the armor stand’s feet instead of the head. So this change definitely breaks some mechanics in my Diversity 3 map.

Are we able to take another look at this. Even just allow the ability to alter the NoGravity tag?

Can you describe what exactly are you doing? In 1.14 marker stands with gravity will fall through world, so behavior would still be different.

@unknown I asked mapmakers 2.5 months ago here: https://twitter.com/LapisDemon/status/1093504900603015171 and you as well as ColdFusionMaps from Diversity 3 were tagged by Jigarbov here: https://twitter.com/Jigarbov/status/1093946168579510272 but there was no reaction from any of you two.

As stated before, I'm always an advocate for having the most of possibilities available for mapmakers, it was just not an option to keep this in the game (after collision changes entities can no longer have a zero-sized collision box, yet still collided with terrain), and as no mapmaker gave a negative feedback about that change, I thought it was okay for everyone.

But maybe Mr. Bok can indeed find a way to re-add this for Creative/mapmakers, without breaking the necessary fix.
For example with the addition of another tag.

Two issues currently. I had a minecart riding a marker armor stand (same idea with falling blocks). The armor stand needed gravity to be launched and I used marker stands because the minecart and falling blocks gets summoned at the feet and the minecart doesn't move. Currently in 1.14, the player rides above the armostand when it's not a marker. I cannot get it to work without the gravity on it. I could post a video demo if need be. But you can see what i mean in Diversity 3 map if you download it.

Boq wrote: "It seems that main idea behind marker blocks was to, well, marker block positions, which implies that they should not move"

It seems that people used moving markers to make minecarts or boats that are uncontrollable by player, but controllable by mapmaker. So marker armorstand are not only to mark position, but also motion and collision.

Solution would be adding isColliding NBT tag to armorstands - this way player decides if collision is needed or not.

"After recent collision changes entities can no longer have zero-sized collision box yet still collide with terrain." This might be a problem though. Collision box should stay zero-sized, but collision with terrain also should be available.

Just to re-iterate: we can't restore collisions for marker armor stands without giving them noticeable hitbox - but then they would no longer be markers (and also that would have side effect of riding entities hovering about ground). It's not behavior that can be controlled by flag, it's how collision calculation works in this versions.

Linear or accelerated motion without collisions can be simulated by storing scoreboard operation in 'Pos' vector. While cumbersome, it works exactly as "intrinsic" movement - adding special flag for no collisions + motion would not achieve anything else. I guess for some more complicated setups position can also be copied (with some offset) from other entities.

Normally velocity decays by 0.98 every tick. Storing that value in 'Motion' tag will make it work automatically.
So to simulate gravity, every tick add -0.04 to 'Motion[1]', then add 'Motion[1]' to 'Pos[1]'.

This is unfortunate. There's no entity now that can be used as a guide to force a player to move with gravity but also can't be interacted with. A non-marker armor stand still can be "thumped". I had another mechanic that had the player constantly being teleported to its position while it fell. Now the player can punch the armor stand and there is sound, hitting the invisible armor stand - breaking immersion. I really don't understand this decision because we already had a NoGravity tag that created what this change is, but it was optional. We also have area effect clouds which are much better option for actual markers, unfortunately they do not have any gravity. We used marker stands specifically for gravity and other features related to how other entities rode them. And now, if marker stands do not have gravity, and considering you can disable slots with regular armor stand, I don't see any use for them.

I have had 4 different mechanics in Diversity 3 so far that required the gravity on a marker armor stand. All no longer working.

Is there another gravity entity that can't be interacted with we could use? Or perhaps a tag that could be added to create the previous physics on a armor stand that could not be interacted with?

Also Bok, just to let you know, in the map making community, the vast majority of mechanics people do not use armor stands as markers. They haven't since area effect clouds came out.

I'm still not sure what exactly you mean by "gravity" - is it just movement (which can be replicated with commands) or movement with collisions.

If it's about collisions, then let me repeat again: if world can't interact with something, that something can't interact with world. Zero-sized bounding boxes worked by accident. And that was broken this release - it wasn't out conscious decision to disable it and not something that can be fixed by adding flag.

If simulating movement is a problem, we can consider re-adding simple movement (nothing more than pos += velocity every tick), but again: no collisions.

EDIT: As for why we've chosen to disable motion for marker armor stands: it's less confusing then letting then fall through world and disappear.