Before reporting, I have confirmed that

• This bug does not appear to be reported on GitHub Issues before.
• This bug still exists in the latest version of the Minecraft Transit Railway mod.
• I have tested this in the official version of Minecraft Transit Railway, not a modified, custom, or unofficial build.

Describe the Bug

Cable cars within a circuit do not slow down to 2kmph when entering a platform section, and continue at their normal speed of 30kmph. This makes entering and exiting the cable car difficult and practically unusable.

Reproduction Steps

1. Create a circuit of siding-curved section-platform-cable-platform-curved section-cable (any working gondola loop will do)
2. Deploy the cable cars
3. Cable cars do not slow down for platform sections.

In-game Log and Crash Report

Game did not crash, log probably isn't relevant in this case.

Mod Loader

Fabric

Minecraft Version

1.20.4

Minecraft Transit Railway Version

4.0.0-prerelease.3+1.20.4

Operating System

Windows 11

List of Mods or Modpack You Were Using

DistantHorizons-fabric-forge-2.3.2-b-1.20.4.jar
indium-1.0.31+mc1.20.4.jar
memoryleakfix-fabric-1.17+-1.1.5.jar
CreativeFly-1.2.1-1.20-fabric.jar
journeymap-1.20.4-5.10.0-fabric.jar
MTR-fabric-4.0.0-prerelease.3+1.20.4.jar
fabric-api-0.97.3+1.20.4.jar
Chunky-1.3.146.jar
ferritecore-6.0.3-fabric.jar
starlight-1.1.3+fabric.f5dcd1a.jar
lithostitched-fabric-1.20.4-1.1.8.jar
sodium-extra-0.5.4+mc1.20.4-build.116.jar
modmenu-9.2.0.jar
entityculling-fabric-1.8.0-mc1.20.4.jar
extended-wold-height-1024-3.2.jar
MSD-fabric-1.20.4-4.0.0-prerelease.2-1.3.19.jar
BetterF3-9.0.2-Fabric-1.20.4.jar
BadOptimizations-2.2.3-1.20.2-20.4.jar
TC-Redstone-1.20.4-Fabric-3.2.3.jar
jei-1.20.4-fabric-17.3.1.5.jar
WorldEditCUI-1.20.3+01.jar
lithium-fabric-mc1.20.4-0.12.1.jar
accurate-block-placement-1.2.1.jar
worldedit-mod-7.3.0.jar
sodium-fabric-0.5.8+mc1.20.4.jar
lazydfu-0.1.3.jar
tectonic-fabric-1.20-2.3.5b.jar
cloth-config-13.0.138-fabric.jar
placeholder-api-2.4.0-pre.3+1.20.4.jar

Extra Information

This is happening for the last 3 prereleases of 4.0.0 for version 1.20.4. When reverted to 4.0.0 beta16 1.20.4, the problem disappears.