This page documents some of the migration steps needed when loading MTR 3 custom content in MTR 4.
JS Scripting from the Nemo Transit Expansion is not implemented at the moment. If you rely on contents that make use of such feature, you are advised to either stay on MTR 3.x + Nemo Transit Expansion addon, or explore with the new Resource Pack Creator in MTR 4 and see whether similar effects can be achieved.
In MTR 3, a train refers to a single type of train, which can be dynamically fitted with any amount of carriage length depending on the siding length.
In MTR 4, the concept of a Train no longer exists. Instead we now have carriage (Vehicle car), where player can mixes different carriage together to form a train (consist). (Which, to the surprise of some, is actually how a train is made up in real life!)
To reflect the different transport types supported in the MTR mod, train are now referred as vehicle.
base_train_type
but without providing texture_id
no longer has base train's texture applied (Only transparent train with bogie & gangway)gangway_connection_id
(Or does not have it) can no longer walk between gangways like they can in MTR 3textures/entity/*
to textures/barrier
, textures/gangway
and textures/vehicle
respectively, as they are now separated.English1|中文|English2
.English
1 has a weight of 100%, 中文
has a weight of 250%, and English2
has a weight of 100%English1
has a weight of 100%, 中文
has a weight of 10%, and English2
has a weight of 100%