technology_price_multiplier = 4 end end ) script. An example would be:ĭata : extend () -in a: script. This works the same way as other prototypes. Mod settings are defined and modified by using the data table during the settings stage. The 'mod-settings.dat' file stored in the mods folder for the game contains the local players settings between game sessions similar to the player-data.json file. Since the settings stage gets loaded first, there is also no prototype data or remote interface available. The settings are all defined in the same stage and their user defined values are not available, therefore mods cannot conditionally create settings depending on the values of other mod settings. These 3 different phases of the settings stage allow to change settings of other mods without needing to rely on dependencies to load last. After a has been called for all mods, the a file is called for each mod (in the same order) and finally the a file is called for each mod (in the same order). There are three files in which settings can be defined:įirst the a file is called for each mod, in the order of their dependencies and then in the natural sort order. This stage is loaded before the data stage. Mod settings are defined in the settings stage. They allow modders to easily create a graphical interface for their configuration options, instead of using on text files that have to be edited manually by users. The values of these settings can be accessed from inside the data stage or the control stage depending on their setting_type and allow to conditionally create or modify prototypes and to add configuration options to control scripts. Each mod can specify settings that users can change.

Where are factorio mods located