mtr:4.0.x:content_developer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| 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/04/09 15:01] (current) – JS scripting (JCM impl) is no longer per-carriage. AmberFrost | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * For MTR 4 loading legacy trains made for MTR 3, the MTR mod will try to detect and split your " | * For MTR 4 loading legacy trains made for MTR 3, the MTR mod will try to detect and split your " | ||
| * For the new MTR 4 format, you are suppose to define everything per-carriage instead of a single train. | * 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, | ||
| To reflect the different transport types supported in the MTR mod, **train** are now referred as **vehicle.** | To reflect the different transport types supported in the MTR mod, **train** are now referred as **vehicle.** | ||
mtr/4.0.x/content_developer.txt · Last modified: 2026/04/09 15:01 by AmberFrost