MC-88038Furnace minecart go backwards when throught the corner
Description by Marcono1234:
PushX and PushZ
First of all this fields are very strange as setting them to a value does not actually cause them to get this value. Instead the game sees the number as percentage:
Estimated codePushX = PushX / (PushX + PushZ) * 5 PushZ = PushZ/ (PushX + PushZ) * 5This also results to values that are in total higher than 5 (maybe 5 is not the value).
You can also clearly see that when one value is 0, the other one becomes (if it is not 0) 5. This will be important in the next paragraph.Moving in corners
Apparently a value for the other variable (not 0) is needed to make the MinecartFurnace to drive on a corner rail.
Reproducing this bug
You can easily reproduce this bug by summoning a MinecartFurnace with either PushX or PushZ 0 and have it drive in circles:
/summon MinecartFurnace ~ ~ ~ {PushX:1d,PushZ:0d,Fuel:32767s}Side note
Powering a MinecartFurnace also results in strange Push values as it takes the position of the player relative to the MinecartFurnace. This results in a PushX and PushZ value which is not 0. However it would make more sense to only store one PushMain as this might be the underlying problem of
MC-51053
It seems like the Motion is then set based on the Push values. A Push value of 5 will always result in a Motion close to 2.5
Linked Issues
Created Issue:
Furnace minecart go backwards when throught the corner
1.8.3 works right.So I think it is not a feature.
Attachments1
1.8.3
works right.SoI think it is not a feature.1.8.3 happened but cannot reproduce.I am finding the way to reproduce.I think it is not a feature.
1.8.3 happened but cannot reproduce.
I am finding the way to reproduce.I think it is not a feature.1.8.3 happened but cannot reproduce.36c is easy to reproduce.I think it is not a feature.
relates to
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
1.8.3 happened but cannot reproduce.36c is easy to reproduce.I think it is not a feature.
Description by Marcono1234 :
PushX and PushZ
First of all this fields are very strange as setting them to a value does not actually cause them to get this value. Instead the game sees the number as percentage:
Estimated codePushX = PushX / (PushX + PushZ) * 5 PushZ = PushZ/ (PushX + PushZ) * 5This also results to values that are in total higher than 5 (maybe 5 is not the value).
You can also clearly see that when one value is 0, the other one becomes (if it is not 0) 5. This will be important in the next paragraph.Moving in corners
Apparently a value for the other variable (not 0) is needed to make the MinecartFurnace to drive on a corner rail.
Reproducing this bug
You can easily reproduce this bug by summoning a MinecartFurnace with either PushX or PushZ 0 and have it drive in circles:
/summon MinecartFurnace ~ ~ ~ {PushX:1d,PushZ:0d,Fuel:32767s}Side note
Powering a MinecartFurnace also results in strange Push values as it takes the position of the player relative to the MinecartFurnace. This results in a PushX and PushZ value which is not 0. However it would make more sense to only store one PushMain as this might be the underlying problem of
MC-51053
It seems like the Motion is then set based on the Push values. A Push value of 5 will always result in a Motion close to 2.5
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
Relates to:
Confirmed for
- 15w36c The problem seems to be with PushX and PushZ. These are the as you called them vectors that determine the Motion of a MinecartFurnace (see comment on MC-88038). However these values are most of the time set to 0 when a MinecartFurnace navigates through a corner. This normally only happens when Fuel is 0, however for corners it does not matter.
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Apologies if I misunderstood your ticket. The title of it led me to believe that you were talking about the issue that we're tracking in MC-51053.
I just took a look at this and the issue that you're describing seems to be that the furnace minecart does not "drag" the normal minecart along. However, the following behaviour seems to be different depending on whether there's someone sitting inside of the minecart or not: if someone's sitting in it, the furnace minecart will continue to bounce (which is described in MC-88038), if nobody is sitting in it, it will stop after 10 blocks (wich is described in MC-51053).
As we don't seem to have a ticket about the fact that passager minecarts are bounced away when the furnace minecart travels around a corner, I have reopened this ticket.
On an unrelated note, I would recommend using powered rails instead of furnace minecarts if you want something reliable to use in your rail system. Furnace minecarts are the maybe most unreliable feature of the game, and it is said that they will be removed from the game in the future.
Confirmed for
PushX and PushZ
First of all this fields are very strange as setting them to a value does not actually cause them to get this value. Instead the game sees the number as percentage:
This also results to values that are in total higher than 5 (maybe 5 is not the value).
You can also clearly see that when one value is 0, the other one becomes (if it is not 0) 5. This will be important in the next paragraph.
Moving in corners
Apparently a value for the other variable (not 0) is needed to make the MinecartFurnace to drive on a corner rail.
Reproducing this bug
You can easily reproduce this bug by summoning a MinecartFurnace with either PushX or PushZ 0 and have it drive in circles:
/summon MinecartFurnace ~ ~ ~ {PushX:1d,PushZ:0d,Fuel:32767s}Side note
Powering a MinecartFurnace also results in strange Push values as it takes the position of the player relative to the MinecartFurnace. This results in a PushX and PushZ value which is not 0. However it would make more sense to only store one PushMain as this might be the underlying problem of
MC-51053It seems like the Motion is then set based on the Push values. A Push value of 5 will always result in a Motion close to 2.5
Confirmed.
Still Broken in 1.11
Is this still an issue in the most recent versions (currently that is 1.12.2, or the latest 1.13 development snapshot 18w21b) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
Cannot reproduce anymore in 1.15.2 Pre-Release 1. Might be fixed along with
MC-51053.