Games/ETS2/Modding guides/1.36

From SCS Modding Wiki
< Games‎ | ETS2/Modding guides
Revision as of 08:56, 13 November 2019 by Max (talk | contribs) (License plate generation templates format improvement)

Jump to navigation Jump to search

TIP: Be aware that page is not final. Thus do not fully rely on written subjects, until this message is here!


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.


  • 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



The editor now works as separate tool started by executing the game with "-edit" launch option/command line parameter. Its log is stored in editor.log.txt instead of the game.log.txt which is used by the game and preview modes.


Due to improvements in game trigger handling, there was some cleanup in /def/world/trigger_action.sii: several trigger commands were renamed and to keep backward compatibility, obsolete trigger actions were moved to /def/world/trigger_action.compatibility.sii.

Traffic data

License plate generation templates format improvement

More data driven license plate system for AI vehicles.

From unit traffic_vehicle the attributes lp_variant_front and lp_variant_rear has been removed.

Units license_plate_data has new attributes: background_front, background_rear. Both are strings (up to 32 characters). Default values are "front" and "rear" respective. Proper usage for variants of texture background is now per vehicle class. If no class is defined first class is used as default (typically "car" class). All other vehicle classes has to be defined explicitly.

Due to interaction with player-owned vehicles system (apportioned trucks and trailer in US) such textures should still be named "truck_front", "truck_rear" or "trailer" respectively (like they were before). Failing to use these names will end with improper backgrounds for player vehicles.

Vehicles data

Chassis data

There is new attribute nominal_voltage (float, default 24.0V) used for battery voltage simulations ranges and display.

Dashboard computer display elements

digital gauges, fuel economy bar (inst/avg), voltage