Contents
Introduction
The following page contains modding guidelines for the new update of the game.
To better understand changes in units it is recommended to check Units documentation page.
Recommendations
- When basing your model on the original ones, add to your mod also ALL original /automat/ files used by it. The names of the files are generated as CityHash64 hash of theirs content so whenever we change the parameters of the material in any way, a different file will be used to store them and the original file might cease to exist if there is no other model utilizing the original parameters.
- When modifying original models, always include ALL components of the model (pmg+pmd) instead of just those you changed. Otherwise you risk crash if we change the model.
- As always when adding new objects to files which support multi-file approach (e.g. road_look.sii) it is HIGHLY RECOMMENDED to use suffix or prefix in the name to avoid conflicts with new objects we are adding in patches. Otherwise you might have to use the batch renaming functionality (see Batch renaming) to fix the conflicts when new patch appears.
How to convert map
- Load map
- Do rebuild (F8)
- Save map
Changes & New Features
More generic wheel system
Handling logic of wheels has been rewritten. Now there are not hardcoded front and rear wheel anymore, but just wheels of various types.
For backward compatibility so far existing wheels are F- and R-typed. They are mounted on locator with the same single letter tag and expected to be stored in similarly named folders with similar unit names (including wheel parts - tire, disc, hub ...). All old wheel data thus work exactly the same as before. But in addition you can create new types defined by different letter that are used and controlled by chassis model and its locators, but shared between vehicles still. Sets of truck and trailer wheels are separated much like before.
For example, new ATS dropdecks trailers have S- and D-type wheels (single and double wheels with much smaller diameter).
This change affects all related data - eg. per type defined defaults in def/vehicle/rim_data.sii require completely different fields.
External interior locators
As we now have wastly different interiors, it is not enough that cabin toy locators for exterior view are linked to cabin exclusively. Thus there can be locators put into external interior models optionaly. If they are not in external interior model, search falls back to cabin (or chassis) model to preserve backward compatibility.