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.

• Train which uses a base_train_type but without providing texture_id no longer has base train's texture applied (Only transparent train with bogie & gangway)
• Train which does not specify a valid gangway_connection_id (Or does not have it) can no longer walk between gangways like they can in MTR 3
• When specifying built-in MTR barrier/gangway/vehicle texture, replace textures/entity/* to textures/barrier, textures/gangway and textures/vehicle respectively, as they are now separated.