Expected Behaviour
The player get blocked indefinitely, nothing else should change

Actual Behaviour
The player gets blocked indefinitely, but the FPS seems to drop as the actual train goes further and further away.
Here's the spark profile created while it's lagging (Seems to be checking for collision):

This is most noticable on very long distances high speed route.

Reproduction Steps

1. Seal off the pathway entirely, leaving no space for train to warp you back in (Using other solid block will work too, bedrock is only an example)
   
2. Ride on the train
3. You'll be stuck on the wall you created, but fps will starts to drop when the train is very far away
   (1km+, weaker system may start lagging only a few hundred blocks away)

Environment

• Minecraft Version: 1.16.5
• Installed Mods: MTR 3.0.0 beta-8 unofficial-3

Additional Information
Maybe we just let player clip through blocks? Or can we eject/force teleport the player to the train when it's getting too far from the train on the server?

Thanks for the detailed bug report, I have noticed this annoying behaviour too. I think your solution options are great, I just gotta think about how to code it in.

The train will now just disappear after a certain distance away instead of aggressively warping the player