What I did:
Using “minecraft:corner_and_cardinal_direction” and the “minecraft:cornerable_stairs” block tag, placed a number of permutations utilizing both custom and vanilla stairs.
What Happened:
When a cornerable_stairs custom block is placed beside another that would normally causes it to take on the “outer_left” or “outer_right” block state, placing an additional block (to complete a 3-piece corner) causes the outer_left or outer_right corner block’s block state to change to “none”, prioritizing the straight connection over the corner connection.
What I Expect to Happen:
The corner stair should retain the “outer_left” or “outer_right” corner block state.
Review:
I have attached the mcaddon file I created to test/debug issues with these stairs (excluding some debugging scripts revealing block states), and can verify that the issue is with the corner block state reverting to “none” when one adjacent block shares its cardinal direction while a perpendicular block does not in a way that should result in an “outer_*” corner block state.
Addition:
I believe this can be addressed by including the “minecraft:connection” cardinal_connections states, but I’m not entirely sure that is expected, intended, or communicated functionality.
Attachments
Comments 0
No comments.