Config to disable "catchup" tick skipping

[PeterKitsune]

Describe the suggestion
Currently, if IR takes too long to calculate physics (i.e. more than one tick) then once it realises it is behind it will "skip" ticks to get the train into the position it "should" be (i.e. where it would be if calculation was instantaneous). If a train is going fast when such an issue occurs, or the server is over capacity, this can cause the player to be left in unloaded chunks client-side, which caused them to be unable to control the train.

My suggestion is a config to disable the catchup, such that it IR is running slower than the tick speed, the trains just run slower.

Applications of the suggestion
Prevents loosing control of trains at speed on low-end servers

[PeterKitsune]

Not entirely sure if it should be a bug or a suggestion - I put suggestion because I believe the catchup tick skipping is an intentional feature, but bug would work since the problem that arises from it is definitely not

[PeterKitsune]

From experience when the TPS is below ~16, this gets noticably worse to the point that it can become unplayable