[MC-791] Rails are not placed in the direction the player is looking

As it stands, the current behaviour of rail placement has always been using this mechanic. This report is indicating that the placement should not follow this, but work differently. For that reason, it is a feature request. I believe there are other bug reports outlining how the current placement method is problematic, and as such could be a bug, but this report does not.

14 more comments

Vexor64 2016-12-12T18:46:00Z

The fact that it has always been this way is no excuse. Making things work differently is the very essence of bugfixing. As for this report not outlining how this could be problematic, that's because it's already indirectly implied.

So please reopen this perfectly good report on an utterly nonsensical and outright inconvenient bug within Minecraft. (Don't forget to update the affected versions if you do so.)

user-f2760 2016-12-12T21:08:26Z

Try looking at the status; it says postponed (meaning "will be fixed later") not resolved.

Vexor64 2016-12-21T22:05:00Z

Could you please just update the status to "reopened"? Don't postpone any longer.

SunCat 2016-12-21T22:20:44Z

@unknown, postponed means "it will be fixed in the future, not now". Do you have any info about it being fixed soon?

Vexor64 2016-12-23T02:54:03Z

I give up in trying to persuade you. How do I become a moderator?

CubeTheThird 2016-12-23T03:09:26Z

The developers use Postponed to indicate an issue will have the fix applied in a later version that does not yet exist. It differs from the Fixed status as this one is given a version number with which it is associated. Once the version in question is added to the bug tracker, at that time the developers can change the status accordingly. And just to clarify, resolution statuses are first and foremost intended for the developers and their internal systems. Regardless which status is publicly displayed, the developers are indicating that this issue is one which will be corrected in a later release.

Kraif 2018-08-24T20:03:56Z

Confirmed for 1.13.1.

Jack McKalling 2018-11-29T16:12:46Z

Confirmed for 18w48a

Jack McKalling 2018-11-30T16:42:16Z

Confirmed for 18w48b

Jack McKalling 2018-12-05T15:57:00Z

Confirmed for 18w49a

Jack McKalling 2018-12-12T15:39:56Z

Confirmed for 18w50a

FaRo1 2018-12-25T18:28:34Z

What i bug here? The description isnt very clear. When I place rails next to others, they just connect.

ProblemsSender 2018-12-25T19:29:19Z

That's technically a rail's function itself, stop spamming a problem that someone would never complain it

FaRo1 2018-12-25T22:44:43Z

I don't know what you mean. I asked for clarification what this report is about, since I see no bug with rail placement. The report claims:

If you place rails not next to another rail of any type, it always faces north-south instead of the way you're facing.

But that is not true, it does neither of those. Instead, it faces in the direction of the other rail. Or a curve towards two rails if there are two next to it.

SuperGeniusZeb 2018-12-28T00:50:58Z

@unknown Read the description very carefully:

"If you place rails not next to another rail of any type, it always faces north-south instead of the way you're facing."

The issue is that when any type of rail is placed by itself, it always faces the same direction. The description is definitely confusing, though. I have updated the description to be more clear.

Jack McKalling 2019-01-09T16:45:16Z

Confirmed for 19w02a

Fabrizio Cantero 2019-09-27T23:02:38Z

It seems that the newest update didn't completely fix this bug, their is still some issues, I have recorded those issues I encountered and I uploaded it here: https://youtu.be/ONDwbzwAfH0
It very interesting, it seemingly breaks at random.

violine1101 2019-09-27T23:08:44Z

In that case, please create a new ticket.

Fabrizio Cantero 2019-09-27T23:21:11Z

Thank you, I have now made a separate ticket linking the video as evidence.