inspectortalon
- inspectortalon
- JIRAUSER735367
- Europe/Stockholm
- Yes
- No
MC-256057
Important
Whenmoving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be consideredonthebottom rail as well, causing acceleration.Steps To Reproduce:
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to me impacted by the rail below it while floating above said rail.
Steps To Reproduce:
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to me impacted by the rail below it while floating above said rail.
Steps To Reproduce:
- Set up any of the shown rail configurations (this may be directional or require specific rail placement techniques to set up)
- Place a cart on the top left sloped rail
- Allow the minecart to move forward into range above the lower rail (the range is dependent upon the center of the minecart bounding box being above the rail)
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration. This leads to the cart being both OnGround and considered on the rail below it, which can subsequently provide acceleration without being in contact. This also means the cart does not snap down through carpet in this set up, unlike when being dropped from above.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to me impacted by the rail below it while floating above said rail.
Steps To Reproduce:
- Set up any of the shown rail configurations (this may be directional or require specific rail placement techniques to set up. Using a debug stick is an easy alternative if configuring the rails properly is found to be difficult)
- Place a cart on the top left sloped rail
- Allow the minecart to move forward into range above the lower rail (the range is dependent upon the center of the minecart bounding box being above the rail)
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration. This leads to the cart being both OnGround and considered on the rail below it, which can subsequently provide acceleration without being in contact. This also means the cart does not snap down through carpet in this set up, unlike when being dropped from above.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to me impacted by the rail below it while floating above said rail.
Steps To Reproduce:
- Set up any of the shown rail configurations (this may be directional or require specific rail placement techniques to set up. Using a debug stick is an easy alternative if configuring the rails properly is found to be difficult)
- Place a cart on the top left sloped rail
- Allow the minecart to move forward into range above the lower rail (the range is dependent upon the center of the minecart bounding box being above the rail)
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration. This leads to the cart being both OnGround and considered on the rail below it, which can subsequently provide acceleration without being in contact. This also means the cart does not snap down through carpet in this set up, unlike when being dropped from above.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to
me impacted by the rail below it while floating above said rail.Steps To Reproduce:
- Set up any of the shown rail configurations (this may be directional or require specific rail placement techniques to set up. Using a debug stick is an easy alternative if configuring the rails properly is found to be difficult)
- Place a cart on the top left sloped rail
- Allow the minecart to move forward into range above the lower rail (the range is dependent upon the center of the minecart bounding box being above the rail)
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration. This leads to the cart being both OnGround and considered on the rail below it, which can subsequently provide acceleration without being in contact. This also means the cart does not snap down through carpet in this set up, unlike when being dropped from above.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to be impacted by the rail below it while floating above said rail.
Steps To Reproduce:
- Enable the Experimental Minecarts features
- Set up any of the shown rail configurations (this may be directional or require specific rail placement techniques to set up. Using a debug stick is an easy alternative if configuring the rails properly is found to be difficult)
- Place a cart on the top left sloped rail
- Allow the minecart to move forward into range above the lower rail (the range is dependent upon the center of the minecart bounding box being above the rail)
Observed Results:
When moving to a rail where it needs to snap down to the next rail, it does not update the OnGround tag to initiate it to snap to the next rail, however the cart can still be considered on the bottom rail as well, causing acceleration. This leads to the cart being both OnGround and considered on the rail below it, which can subsequently provide acceleration without being in contact. This also means the cart does not snap down through carpet in this set up, unlike when being dropped from above.
Expected Results:
The minecart should snap down to the rail when it is in vertical range do so. The minecart should not float, nor should it be able to be impacted by the rail below it while floating above said rail.
image-2024-08-29-00-16-46-304.png
Steps to Reproduce:
1. Enable Minecart Improvements Experimental Features2. Dispense a stack of carts (18 shown in example)
3. Ride one of the Minecarts
4. Propel the stack forward into a wall
Observed Results:
Game goes kaboom when the stack hits the wall. Upon reloading, the carts (presumably with NaN or motion greater than the 32 bit integer) are removed from the world.
Expected Results:
The stack of carts should stop against the wall, and not instantly crash the game.
Note: May be related to the bug shown by Phoenix SC where the cart teleports the player to a NaN location, however it is currently resulting in a crash for me instead.
Please fix this, it makes creating reliable parallel lines with minecarts a chore to potentially impossible in some cases. It is an inconvenience that in turn has extremely negative consequences when beginning or trying to work with minecarts.