510
edits
Changes
Jump to navigation
Jump to search
→Timezone sub-areas
Data for time zone sub-areas has been introduced silently in 1.34 update (look for Malheur county, Oregon in ATS or Kaliningrad area, Russia in ETS).
One set of data is in '''city_data''' units and are data is used for static city-based zone usage (eg delivery times in game economy):* '''time_zone''' (integer, default is undefined value, represented by week of time, 10080) - time delta zone of given city in minutes
* '''time_zone_name''' (string, default empty) - name of eventual time zone
If city time zone is undefined (or 10080) then time zone of country the city belongs to is used.
Second set of additional data consist of three synchronized arrays (same length expected) stored in '''country_data''' units and is used for spatial detection of time zone on map:
* '''secondary_time_zone''' (integer array) specifies time delta of given area in minutes
* '''secondary_time_zone_name''' (string array) specifies name of time zone in given area
If point is in given country (decided by map - logic by road/prefabs) then all existing rectangle elements are checked for different time zone than country has. If no area is found, country time zone is used.
== Transmission mode names ==
(already silently introduced ??)
