Differences

This shows you the differences between two versions of the page.

--- mtr:4.0.x:content_developer [2026/04/09 15:00] – Add note on mtr_custom_resources_pending_migration.json AmberFrost
+++ mtr:4.0.x:content_developer [2026/09/23 12:35] (current) – Remove mtr_custom_resources_pending_migration.json (Does not migrate signs, only for internal use) AmberFrost
@@ Line 3: / Line 3: @@
 This page documents some of the migration steps needed when loading MTR 3 custom content in MTR 4.
-===== Javascript Scripting =====
+===== JS Scripting =====
-JS Scripting from the [[mtr_addon:nte:start|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.
+JS Scripting from the [[mtr_addon:nte:start|Nemo Transit Expansion]] is not implemented in the main mod, however there are 3rd party efforts such as [[mtr_addon:jcm:start|Joban Client Mod]] which aims to re-implement the JS scripting feature from NTE.
+You can also explore with the new Resource Pack Creator in MTR 4 and see whether similar effects can be achieved.
 ===== Train (Concept) =====
@@ Line 15: / Line 17: @@
   * For MTR 4 loading legacy trains made for MTR 3, the MTR mod will try to detect and split your "Train" into several parts (e.g. Cab Forward, Trailer, Cab Backward)
   * For the new MTR 4 format, you are suppose to define everything per-carriage instead of a single train.
-  * While JS scripting is not implemented yet, if and when it is implemented, you are expected to make heavy modification to your script to align with the new per-carriage system.
 To reflect the different transport types supported in the MTR mod, **train** are now referred as **vehicle.**
@@ Line 26: / Line 27: @@
   * 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.
+  *
-==== Dual-versioned resources (MTR 3 Custom Resource + MTR 4 Custom Resource) ====
-MTR 4 supports reading **mtr_custom_resources.json** in both MTR 3 and MTR 4 format.
-However during migration period, you may run into a situation where some content are migrated to MTR 4, while others are not, but you want to fit them in to the same resource pack.
-To that, MTR 4 supports an alias called **mtr_custom_resources_pending_migration.json**, which works effectively the same as the regular **mtr_custom_resources.json**.
-This allows you to put MTR 3's custom resources into **mtr_custom_resources_pending_migration.json**, while using **mtr_custom_resources.json** for MTR 4 content.
 ==== Custom Model Changes ====