510
edits
Changes
Jump to navigation
Jump to search
Aditional data are in '''city_data''' units and are used for city-based zone usage (eg delivery times in game economy).
SIMPLE_ATTR_INT(time_zone, NULL),
SIMPLE_ATTR_STRING(time_zone_name, NULL),
→Timezone sub-areas
== Timezone sub-areas ==
Data for time zone sub-areas has been silently 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 used for 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 of given city in minutes* '''time_zone_name''' (string, default empty) - name of eventual time zone Basic data consist of three synchronized arrays (same length expected) stored in '''country_data''' units:
* '''secondary_time_zone_area''' (float4 array) define elements of rectangle areas in editor coordinates
* '''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 - road/prefabs) then all existing rectangle elements are checked for different time zone than country has.
== Transmission mode names ==
(already silently introduced ??)
