| Type: | Bug | ||
| Reporter: | [Helper] Jack McKalling | Assignee: | [Mojang] slicedlime |
| Resolution: | Fixed | Votes: | 36 |
| Labels: | direction, placement, rail | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Category: |
Block states
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Mojang Priority: | Normal | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Fabrizio Cantero [ 27/Sep/19 ] |
|
Thank you, I have now made a separate ticket linking the video as evidence. |
| Comment by [Mod] violine1101 [ 27/Sep/19 ] |
|
In that case, please create a new ticket. |
| Comment by Fabrizio Cantero [ 27/Sep/19 ] |
|
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 |
| Comment by [Helper] Jack McKalling [ 09/Jan/19 ] |
|
Confirmed for 19w02a |
| Comment by Zeb [ 28/Dec/18 ] |
|
FaRo1 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. |
| Comment by Fabian Röling [ 25/Dec/18 ] |
|
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:
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. |
| Comment by ProblemsSender [ 25/Dec/18 ] |
|
That's technically a rail's function itself, stop spamming a problem that someone would never complain it |
| Comment by Fabian Röling [ 25/Dec/18 ] |
|
What i bug here? The description isnt very clear. When I place rails next to others, they just connect. |
| Comment by [Helper] Jack McKalling [ 12/Dec/18 ] |
|
Confirmed for 18w50a |
| Comment by [Helper] Jack McKalling [ 05/Dec/18 ] |
|
Confirmed for 18w49a |
| Comment by [Helper] Jack McKalling [ 30/Nov/18 ] |
|
Confirmed for 18w48b |
| Comment by [Helper] Jack McKalling [ 29/Nov/18 ] |
|
Confirmed for 18w48a |
| Comment by Kraif [ 24/Aug/18 ] |
|
Confirmed for 1.13.1. |
| Comment by [Mod] CubeTheThird [ 23/Dec/16 ] |
|
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. |
| Comment by Vexor64 (Inactive) [ 23/Dec/16 ] |
|
I give up in trying to persuade you. How do I become a moderator? |
| Comment by SunCat [ 21/Dec/16 ] |
|
Vexor64, postponed means "it will be fixed in the future, not now". Do you have any info about it being fixed soon? |
| Comment by Vexor64 (Inactive) [ 21/Dec/16 ] |
|
Could you please just update the status to "reopened"? Don't postpone any longer. |
| Comment by user-f2760 (Inactive) [ 12/Dec/16 ] |
|
Try looking at the status; it says postponed (meaning "will be fixed later") not resolved. |
| Comment by Vexor64 (Inactive) [ 12/Dec/16 ] |
|
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.) |
| Comment by [Mod] CubeTheThird [ 24/Feb/15 ] |
|
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. |
| Comment by Lucas Ignacio Morrison Osorio [ 23/Feb/15 ] |
|
How is this a feature request? I can only see this being a bug. |
| Comment by [Mod] CubeTheThird [ 27/Nov/12 ] |
|
This is not a bug, but a feature request, and should be posted on the MC forums here. |
| Comment by DiEvAl [ 26/Oct/12 ] |
|
It's a feature request, not a bug report. |
| Comment by Vit Musienko [ 26/Oct/12 ] |
|
its a common feature, since there are rails in minecraft |