Blocks like tallgrass are randomly offset within their occupying block. This offset is consistent along the Y-Axis when using the default resource pack. Once a resource pack artist has flowers or double-plants reference a new block model, the consistent offset is broken.
This means double-plants do not line up with each other, and resource pack creators have no control over the random offset of any blocks.
Attachments
Comments 18
Not an intended feature, nor dependent on random orientation implemented by the resource pack. This "feature" means resource packs can't change the model of double tall plants without the upper half appearing to float.
Again, it is not a bug, it has intentionally be implemented that the blocks get random x y and z location on every block, and you specify it should do that.
Why do you think double plants don't use it by default?
Again, for feature/change requests, go to the reddit.
Again, random block offset is hardcoded. I can't do anything to change it. Can't make it a bigger range, smaller range, nothing.
If you use your models for blocks that are not offset by the engine, do they line up correctly? We really can't troubleshoot without all the relevant files. Once again, I've found several resource packs with 3D models for double plants, and they have no problems lining up the top and the bottom. You're apparently doing something differently, but we have no way to tell what, or whether it should work, without being able to examine your model and texture files. You're welcome to set the issue to private if you don't want the files to be publicly available.
The parent file attached is referenced by several files, with one texture each. They would all be very boring to upload. The images being referenced are 8x8 and that's about the only thing out of the ordinary. I've noticed this same error over a year ago, so I really question that this is non-reproducible, since I've reproduced it on accident twice by myself. I did make a mistake in saying they don't line up on the Y-Axis though, they have been consistent in that regard.
Alright, after throwing together a test resource pack, and performing a variety of tests, I've identified the problem: You're parenting off a model that doesn't define any elements, and that apparently messes with the renderer, at least when it comes to calculating offsets. Remove the "parent": "block/block" line, and everything works fine. If you need the display tags from block.json, copy them into your double_plant.json. I'll have to find out whether it is WAI or a bug, but it's easy to work around.
This is great news! Thank you for going through the trouble to troubleshoot for me and others with the potential same issue! I've always been a big proponent of customizable block offset, but all that matters is this consistency.
Who knew the mother "block" was the route of all our problems ¯_(ツ)_/¯
How it now works is how it should, double plants are 2 blocks above each other, not 1 big block, changing this would be a feature request, for that, go here.