Thank you @Greymagic27 for your reply. I've go thru all issues related to "minecart" (JQL was: `project = MC AND resolution = Unresolved AND text ~ "minecart" ORDER BY votes DESC`) (this took me more than 2 hours). This issue seemed most relevant to my problem, so I've decided to comment this. I've found MC-148604 first, but it does not seem to fullfil my requirements. It only refers about issue when minecart gets "blocked" on powered rails.
My problem is, better to say, with minecarts' push force (which is so low it sometimes stop minecart from moving completely when pressing W).
I've already voted for this issue and MC-148604, I will alco copy my comment from here to that issue, so it will be better visible.
This is one issue and along with MC-169854 it caused a lot of problems for me. I'm thus forced to stay with 1.12.2.
I have a large train system and I used to rely on minecart mechanics. I was able to composit "trains" from up to 5 minecarts (optimal 4) and one rideable minecart for pushing the other minecarts. On 1.12.2 (my previous version), it behaves correctly. Now I facing this issues:
I cannot move with singe rideable minecart
I'm no longer able to push other minecarts on unpowered rails (I need those in stations, because of kick-off glitch when two minecarts colide)
Behaviour of minecarts from 1.12.2 and previous versions was just fine. My question is: will new behaviour become new standard (then I will stay with 1.12.2) or its a bug that will be resolved later on (thus I can upgrade)?
(copied comment from MC-169854)
I have a large train system and I used to rely on minecart mechanics. I was able to composit "trains" from up to 5 minecarts (optimal 4) and one rideable minecart for pushing the other minecarts. On 1.12.2 (my previous version), it behaves correctly. Now I facing this issues:
I cannot move with singe rideable minecart
I'm no longer able to push other minecarts on unpowered rails (I need those in stations, because of kick-off glitch when two minecarts colide)
Behaviour of minecarts from 1.12.2 and previous versions was just fine. My question is: will new behaviour become new standard (then I will stay with 1.12.2) or its a bug that will be resolved later on (thus I can upgrade)?