[MC-194722] Changing shape property of rails to ascending using Debug Stick makes rail drop

When using the Debug Stick to change the shape property of any rail type to one of the ascending_ values, the rail drops as item if there is no supporting block.

The Debug Stick is supposed to change block states without updating the block to allow placing invalid states, however here this is not possible. Therefore the general rules "block states created using Debug Stick not working as intended" does not apply here because the Debug Stick is not able to create the block state in the first place.

Steps to Reproduce:

Place down any type of rail block on flat ground, without other blocks nearby
Use the Debug Stick to change the shape property to any of the ascending_ values

Expected & Experienced Results:

→ ❌ The rail breaks, and drops as item.
→ ✔ The rail would be set properly to the state value you are changing, and not break.

Video(s):

[media]

Notes

Linked issues

is duplicated by 1

MC-268771 Debug stick makes rails dissapear Resolved

Attachments

2023-11-28_21-04-56.mp4

rail_debug_stick.webm

Comments 20

kurikuri 2020-11-25T10:54:55Z

It does not fix the debug stick issue. Please check this out for details
https://www.reddit.com/r/Minecraft/comments/7es23r/

Skaijie 2020-11-25T11:49:30Z

The report was reopened likely because it would affect/is an issue with a game mechanic that does not require involving debug sticks

Avoma 2020-12-03T09:15:52Z

Can confirm in 20w49a.

Avoma 2021-01-31T19:47:07Z

Can confirm in 21w03a.

Marty McFly 2021-05-30T22:06:27Z

Affects 1.17 Pre-release 1

10 more comments

SamtheBKBoss 2021-06-05T20:47:55Z

Can confirm for 1.17 Release Candidate 1.

Marty McFly 2021-06-09T13:42:21Z

Affects 1.17

Oog 2022-03-04T21:45:03Z

Can confirm affects 1.18.1

SamtheBKBoss 2022-04-19T04:06:36Z

Can confirm for 1.18.2 and 22w15a.

Avoma 2022-07-01T14:25:52Z

Can confirm in 1.19.

Avoma 2022-09-09T13:37:32Z

Can confirm in 1.19.2.

[Mod] Jingy 2023-09-10T23:27:39Z

Can confirm in 1.20.1

[media]

[Mod] Jingy 2023-11-26T05:44:41Z

Requesting ownership of this issue as the original poster has been inactive for 3 years now.

edl411 2023-11-27T19:55:34Z

Have I been inactive that long? Oops.

I apologize for having been so inactive. While I haven't made any bug reports in years, I do occasionally check on this issue in the hopes that it will eventually be fixed.

Reply from @unknown:
The reporter is expected to keep the ticket up to date. This also includes adding new affected versions. Simply checking to see if it has been resolved is not sufficient, especially since unmaintained issues are less likely to be picked up and ultimately fixed.

edl411 2023-11-27T20:18:19Z

Aye, that's understandable. It's unfortunate for me that I didn't realize I was being held up to such high expectations. But oh well. I appreciate everyone keeping this alive, it means a lot. If I make any more bug reports in the future I'll try to be more proactive.

edl411 2023-11-28T16:13:44Z

Can confirm this affects 1.20.3 Pre-Release 4.

https://streamable.com/lojiqv

edl411 2023-11-30T16:49:54Z

Can confirm this affects 1.20.3 Release Candidate 1.

https://streamable.com/m6t8bl

edl411 2023-12-05T18:10:26Z

Can confirm this affects 1.20.3.

https://streamable.com/evzyh1

edl411 2023-12-06T18:14:12Z

No fix announced for 1.20.4 Release Candidate 1. Do I still have to confirm?

[Mod] Jingy 2023-12-06T18:21:03Z

It's not really needed, 1.20.4 rc 1 is a hotfix update.