Official Factorio Wiki - User contributions [en]

Tutorial:Localisation

2024-11-10T13:27:42Z

Nallaj: Fix broken link

{{Languages}}Mods should define human readable names for prototypes that they add. They can also define descriptions for items or custom strings for usage in GUIs etc. This is called '''localisation'''.

== File format ==
Translations are stored as .cfg files, with the following format:

<pre>welcome-message=Hello world
[category]
title=Category related title
# Comment
; Another comment</pre>
Any whitespace after or before <code>=</code> is included in the key or string, so <code>title =Category related title</code> will give an unknown key error if you are looking for the <code>title</code> key, since it is the <code>title </code> key.

<code>category</code> can be one of the existing locale categories, which permits implicit search mechanisms to find translations, but may also be another key, such as <code>[my-mod-messages]</code>. These are accessible the same as other translations, e.g. <code>{"my-mod-messages.hello"}</code>

These files are located within the language code of the language in the locale folder of the mod, so as an English example <code>__mod__/locale/en/any_name_here.cfg</code>. There can be more than 1 file per language, all of them will be read.

== Localising simple strings ==
The simplest localisation is of items, entities etc. If we say the item is <code>iron-plate</code>, the game will then search all loaded locale files for <code>item-name.iron-plate</code> and <code>item-description.iron-plate</code>, which in the locale file looks like this:

<pre>[item-name]
iron-plate=Iron plate
[item-description]
iron-plate=A plate made of iron.</pre>
If found in the locale, the label is set to this string. If not found, the game will instead show: <code>Unknown key: "item-name.iron-plate"</code>

In script, the localised string is formatted as <code>{"category.name"}</code>, so <code>game.print({"item-name.iron-plate"})</code> prints ''Iron plate''.

It is possible to use [[rich text]] features in the localised text if the location where the text is shown supports it, e.g. in the chat, prototype names and prototype tooltips.

<code>\n</code> can be used for line breaks if the location where the text is shown supports multiline text.

The list of all localization categories used by the base game is:

{| class="mw-collapsible mw-collapsed wikitable"
|-
!Localization categories
|-
|<code>[achievement-description]</code>
|-
|<code>[achievement-name]</code>
|-
|<code>[ammo-category-name]</code>
|-
|<code>[autoplace-control-names]</code>
|-
|<code>[controls]</code>
|-
|<code>[damage-type-name]</code>
|-
|<code>[decorative-name]</code>
|-
|<code>[entity-description]</code>
|-
|<code>[entity-name]</code>
|-
|<code>[equipment-name]</code>
|-
|<code>[fluid-name]</code>
|-
|<code>[fuel-category-name]</code>
|-
|<code>[item-description]</code>
|-
|<code>[item-group-name]</code>
|-
|<code>[item-limitation]</code>
|-
|<code>[item-name]</code>
|-
|<code>[map-gen-preset-description]</code>
|-
|<code>[map-gen-preset-name]</code>
|-
|<code>[mod-description]</code>
|-
|<code>[mod-name]</code>
|-
|<code>[modifier-description]
|-
|<code>[programmable-speaker-instrument]</code>
|-
|<code>[programmable-speaker-note]</code>
|-
|<code>[recipe-name]</code>
|-
|<code>[shortcut]</code>
|-
|<code>[story]</code>
|-
|<code>[string-mod-setting]</code>
|-
|<code>[technology-description]</code>
|-
|<code>[technology-name]</code>
|-
|<code>[tile-name]</code>
|-
|<code>[tips-and-tricks-item-description]</code>
|-
|<code>[tips-and-tricks-item-name]</code>
|-
|<code>[virtual-signal-description]</code>
|-
|<code>[virtual-signal-name]</code>
|}

== Localising with parameters ==
For more complex strings, localisation parameters can be used. For instance we want to show ''Time left: 10 minutes.''

So a key with a placeholder is defined, which is replaced by the first parameter after the locale key.:

<pre>time-left=Time left: __1__ minutes.</pre>
So it is used like this:

<syntaxhighlight lang="lua">game.print({"time-left", 10})</syntaxhighlight>
It also works with multiple parameters:

<syntaxhighlight lang="lua">game.print({"time-left", 10, 45})</syntaxhighlight>
<pre>time-left=Time left: __1__ minutes and __2__ seconds.</pre>
Which results in ''Time left: 10 minutes and 45 seconds.''

=== Built-in parameters ===
For some situations, we use localisation to show control schemes. For instance we want to say:

<pre>technology-prompt=Use T to open the technology screen</pre>
However the player may have rebound the key, but we can’t figure out which key as it would not be deterministic. So instead we use the built-in replacement functionality

<pre>technology-prompt=Use __CONTROL__open-technology-gui__ to open the technology screen.</pre>
We can also use this for items and entities:

<pre>big-iron-plate=Big __ITEM__iron-plate__</pre>
<pre>tiny-gun-turret=Tiny __ENTITY__gun-turret__</pre>

==== List of built-in parameters ====
<code>name</code> is the name of an internal game control or a prototype name, depending on context. <code>n</code> can be 1 or 2, it's used in parameters that control [[#Localising_alternate_input_names|alternate input names]]. For a list of internal game control names, see [https://lua-api.factorio.com/latest/types/LinkedGameControl.html CustomInputPrototype::linked_game_control].
* <code>__CONTROL__name__</code> - The combination of modifiers and input, such as "Control + Alt + Left-click", or "Not set".
* <code>__CONTROL_MODIFIER__name__</code> - The modifiers, such as "ControlShift", or, "No modifier selected."
* <code>__CONTROL_STYLE_BEGIN__</code>
* <code>__CONTROL_STYLE_END__</code>
* <code>__CONTROL_LEFT_CLICK__</code> is replaced with <code>control-keys.mouse-button-1</code> or <code>control-keys.controller-b</code>[https://crowdin.com/project/factorio/discussions/214]
* <code>__CONTROL_RIGHT_CLICK__</code> is replaced with <code>control-keys.mouse-button-2</code> or <code>control-keys.controller-x</code>
* <code>__CONTROL_KEY_SHIFT__</code> is replaced with <code>control-keys.shift</code> or <code>control-keys.controller-leftshoulder</code>
* <code>__CONTROL_KEY_CTRL__</code> is replaced with <code>control-keys.control</code> or <code>control-keys.controller-rightshoulder</code>
* <code>__ALT_CONTROL_LEFT_CLICK__n__</code> is replaced with <code>control-keys.mouse-button-1-alt-n</code> or <code>control-keys.controller-button-alt-n</code> (with parameter <code>control-keys.controller-b</code>)
* <code>__ALT_CONTROL_RIGHT_CLICK__n__</code> is replaced with <code>control-keys.mouse-button-2-alt-n</code> or <code>control-keys.controller-button-alt-n</code> (with parameter <code>control-keys.controller-x</code>)
* <code>__REMARK_COLOR_BEGIN__</code>
* <code>__REMARK_COLOR_END__</code>
* <code>__ALT_CONTROL__n__name__</code>
* <code>__CONTROL_MOVE__</code> - The Movement keys, squished together. Example: "WASD", from a conventional QWERTY English keyboard.
* <code>__ENTITY__name__</code> - The localised name of the [https://lua-api.factorio.com/latest/prototypes/EntityPrototype.html EntityPrototype] subclass.
* <code>__ITEM__name__</code> - The localised name of the [https://lua-api.factorio.com/latest/prototypes/ItemPrototype.html ItemPrototype] or subclass.
* <code>__TILE__name__</code> - The localised name of the [https://lua-api.factorio.com/latest/prototypes/TilePrototype.html TilePrototype].
* <code>__FLUID__name__</code> - The localised name of the [https://lua-api.factorio.com/latest/prototypes/FluidPrototype.html FluidPrototype].

=== Plurals ===
Pluralization can be used in any string that uses a parameter (e.g. __1__) that is numeric, so something like an amount of minutes. It can be used multiple times per string.

<pre>format-days=__1__ __plural_for_parameter__1__{1=day|rest=days}__</pre>
This results in "1 day" and "2 days" / "500 days" etc.

The number after <code>__plural_for_parameter__</code> denotes which parameter is used to determine the plural. This is the parameter 1 in the above example. Anything inside the {} is used to make the plural. Each plural form is separated by a |.
The text in front of the = determines for what the plural form is used. Options for this are:
* a simple number, e.g. "1".
* Multiple numbers, e.g. "2,3,4".
* What the number ends with, e.g. "ends in 11" or "ends in 1"
* Multiple ends with, e.g. "ends in 1,ends in 2,ends in 12".
* "rest" to give the default plural.

'''Starting with version 2.0''', there have to be two underscores surrounding the number that denotes which parameter is used to determine the plural: <code>__plural_for_parameter__1__{1=day|rest=days}__</code>

Plural forms may be empty or contain other keys such as __1__ or spaces. This allows rather large plural forms:

<pre>__plural_for_parameter__1__{1=__1__ player is|rest=__1__ players are}__ connecting</pre>

The system chooses the first fitting plural that it encounters when multiple would fit:
<pre>__plural_for_parameter__1__{ends in 12=option 1|ends in 2=option 2|rest=option 3}__</pre>
This will result in "option 1" for 12 and in "option 2" for 22 and in "option 3" for numbers not ending with 2.

=== Concatenating localised strings ===
The special locale key: <code>""</code> is used to concatenate, as the table format does not support concatenation:

<syntaxhighlight lang="lua">game.print({"", {"item-name.iron-plate"}, ": ", 60})</syntaxhighlight>
Will result in: ''Iron plate: 60''

=== Localising alternate input names ===

In the introduction campaign, a special locale system is used for informing players how to do certain actions with their mouse.
The normal form is to use eg:
<pre>how-to-build=Use __CONTROL__build__ to place a building</pre>
which results in "Use Left mouse button to place a building". A more natural phrasing would be "Left-click to place a building", which can be achieved by using the following:
<pre>how-to-build=__ALT_CONTROL__1__build__ to place a building</pre>

These "alt" versions are controlled by a few special locale keys, mouse-button-X-alt-1 and mouse-button-X-alt-2. In English, form 1 produces eg "Left-click", and form 2 produces eg "Left-clicking". Only two alt forms ("1" and "2") are available at the moment, but if this a problem for some languages, more forms may be added in the future.
Extra mouse buttons, mouse scroll and keyboard keys are handled through the mouse-button-n-alt-1/2, mouse-wheel-alt-1/2 and keyboard-alt-1/2 keys, which just take the normal name and prepend something like "Press/Pressing", or "Scroll/Scrolling".

When translating to another language, you can use whatever forms you want here, but the important part is that you are consistent when you use the alt-forms everywhere else. It does not necessarily make sense to just copy the usages of alt forms from the English locale, and for some languages it may be more natural to simply not use this system at all.

== Accessing the localised result in code ==
While usually unneeded, it is possible to read the resulting localised text in code, for example to search in localised names.

See
[https://lua-api.factorio.com/latest/classes/LuaPlayer.html#request_translation LuaPlayer::request_translation],
[https://lua-api.factorio.com/latest/classes/LuaPlayer.html#request_translations LuaPlayer::request_translations] and
[https://lua-api.factorio.com/latest/events.html#on_string_translated on_string_translated event].

== Default Behavior(s) for finding an Unspecified Localised String ==
If a localised_string is not defined in the prototype for certain prototype classes, e.g. entity, item, Factorio may have a default search behavior.

Determining an item's localised name:
Note: the angle brackets are meant to mean a generic term, they are not part of the actual string. Also, place_result and placed_as_equipment_result are strings, and Factorio fetches the matching prototype to examine.

# if localised_name is provided in the item prototype and it is not empty {}, use the provided value
# else if there is place_result and it has localised_name that is not an empty table: {}, use the localised_name of place_result
# else if there is place_result with an empty localised_name, use {"entity-name.<entity prototype name>"}
# else if there is placed_as_equipment_result and it has a localised_name that is not an empty table: {}, use the localised_name of placed_as_equipment_result
# else if there is placed_as_equipment_result with empty localised_name, use {"equipment-name.<equipment name>"}
# else use default {"item-name.<item name>"}

Reference: [https://forums.factorio.com/viewtopic.php?p=494243#p494243]

Example: The transport-belt item does not have a localised_name, so 1->2. There is a place result, but not localised_name in the entity prototype. 2->3. The place result lacks a localised_name. Use the localised string {"entity-name.transport-belt"}

Such defaults often include a "leading key" using [<group>-name] or [<group>-description] (such as [recipe-name], [mod-setting-description]). However, each prototype may have a distinct search behavior before using those, based on presence/absence of values in the prototype. [[Prototype/Recipe]] for example may use the first product's localised_name, or the main_product's localised_name, or the localised string found in {"recipe-name.<recipe name>"], depending on values provided (and lacking) in the prototype.

== See also ==
* [[Types/LocalisedString|LocalisedString data stage doc]]
* [https://lua-api.factorio.com/latest/Concepts.html#LocalisedString LocalisedString control stage doc]

[[Category:Modding]]

Command line parameters

2024-09-04T12:49:13Z

Nallaj: Separate arg type from arg name

{{Languages}}__TOC__

Command line parameters can be used to set settings in the command line before the game launches, this is useful mainly for advanced users or server hosts.

{| class="wikitable"
|+General options
|-
| -h, --help
|
| display help
|-
| --version
|
|show version information
|-
| -v, --verbose
|
|enable verbose logging
|-
| -c, --config
| PATH
|config file to use
|-
| --no-log-rotation
|
|don't rotate log file
|-
| --mod-directory
| PATH
|Mod directory to use
|-
| --check-unused-prototype-data
|
|Print a warning for all prototype values that were not accessed. Note for mod authors: If an entry is unused and is a table that contains the key/value pair 'ignore' with the value 'true' then the entire entry is ignored.
|-
| --executable-path
| PATH
|Override autodetected __PATH__executable. Usually not needed except on very weird systems.
|}

{| class="wikitable"
|+ Running options
|-
| -s, --map2scenario
| arg
|map to scenario conversion
|-
| -m, --scenario2map
| arg
|scenario to map conversion
|-
| --apply-update
| arg
|immediately apply update package
|-
| --create
| FILE
|create a new map
|-
| --map-gen-settings
| FILE
|Map generation settings for use with <code>--create</code>, <code>--start-server-load-scenario</code> or --generate-map-preview. See data/map-gen-settings.example.json
|-
| --map-gen-seed
| SEED
|Map generation seed for use with --create, --start-server-load-scenario or --generate-map-preview. Will override seed specified in map gen settings
|-
| --map-gen-seed-max
| SEED
|Map generation seed for use with --generate-map-preview to generate multiple previews using every second seed in the interval from map-gen-seed to map-gen-seed-max.
|-
| --map-settings
| FILE
|Map settings for use with --create or --start-server-load-scenario. See data/base/prototypes/map-settings.lua
|-
| --preset
| arg
|Name of the map generation preset to be used.
|-
| --generate-map-preview
| PATH
|Generate preview images of the map; PATH should name a PNG file or end with a '/' or '\' to indicate a directory.
|-
| --generate-map-preview-random
| COUNT
|Number of maps to generate with a random seed using --generate-map-preview.
|-
| --map-preview-size
| SCALE
|Size (in pixels) of map preview (default: 1024)
|-
| --map-preview-scale
| SCALE
|Scale (meters per pixel) of map preview (default: 1)
|-
| --map-preview-offset
| X,Y
|Offset of the center of the map, in meters (default: 0,0)
|-
| --noise-outputs
| TAG,TAG...
|Indicate which variables of noise program to output
|-
| --slope-shading
| SHADEAMOUNT
|Apply elevation shading to map preview
|-
| --slope-shade-property
| SHADEPROP
|Property to apply slope shading to (default: elevation)
|-
| --report-quantities
| PROTOTYPE,...
|When generating map preview, report approximate quantities of the named entity prototypes
|-
| --threads
| THREADCOUNT
|Number of threads to use when generating map previews
|-
| --disable-migration-window
|
|Disables the gui that is shown when opening a save with migrated content
|-
| --instrument-mod
|
|Name of a mod to enable [https://lua-api.factorio.com/latest/Instrument.html Instrument Mode]
|-
| --start-server
| FILE
|start a multiplayer server
|-
| --start-server-load-scenario
| [MOD/]NAME
|start a multiplayer server and load the specified scenario. The scenario is looked for inside the given mod. If no mod is given, it is looked for in the top-level scenarios directory.
|-
| --start-server-load-latest
|
|start a multiplayer server and load the latest available save
|-
| --until-tick
| TICK
|run a save until given map tick
|-
| --benchmark
| FILE
|load save and run benchmark
|-
| --benchmark-ticks
| N
|number of ticks for benchmarking. Default is 1000
|-
| --benchmark-runs
| N
|how often the number of ticks will be run, map will reload after each run. Default is 1
|-
| --benchmark-verbose
| timings
|comma separated list of Update timings to output each tick. "all", "timestamp" as well as all other values seen in the debug show-time-usage view's Update section are allowed here. An empty string disabled verbose benchmarking. Timings are returned in nanoseconds.
|-
| --benchmark-sanitize
|
|only output the final benchmark results
|-
| --benchmark-ignore-paused
|
|leaves the game paused if it was paused when saved. By default the game is unpaused when a benchmark starts.
|-
| --output-perf-stats
| FILE
|path of file to which rendering performance statistics measurements should be saved. Special tags {api}, {hw}, {time} and {tag} will be replaced.
|-
| --dump-data
|
|dumps data.raw as JSON to the script output folder and exits.
|-
| --dump-icon-sprites
|
|dumps all icon sprites as png files to the script output folder and exits.
|-
| --dump-prototype-locale
|
|dumps all prototypes name and description (if they have a valid value) to the script output folder and exits.
|-
| --mp-connect
| ADDRESS
|start factorio and connect to address
|-
| --password
| PASSWORD
|the password to use when using mp-connect (if any)
|-
| --heavy
|
|run the game in heavy mode if singleplayer with graphics (heavy mode is related to investigating desyncs, see [[Desynchronization#Using_heavy_mode_command]])
|-
| --load-game
| FILE
|start Factorio and load a game in singleplayer
|-
| --load-scenario
| [MOD/]NAME
|start Factorio and load the specified scenario in singleplayer. The scenario is looked for inside the given mod. If no mod is given, it is looked for in the top-level scenarios directory.
|-
| --benchmark-graphics
| FILE
|load save and run it with graphics for benchmark-ticks number of ticks as normal game would
|-
| --benchmark-frame
| FILE
|load save and benchmark graphics rendering of single frame (prepare + render) without updating the game
|-
| --force-opengl
|
|use OpenGL for rendering (windows only)
|-
| --force-d3d
|
|use Direct3D for rendering (windows only)
|-
| --d3d-adapter
| ID
|adapter which should be used to initialized Direct3D (windows only)
|-
| --d3d-feature-level
|
|override feature level (11, 10.1, 10) (windows only)
|-
| --dxgi-blit-model
|
|force Blit presentation mode (windows only)
|-
| --audio-driver
|
|default = sdl = SDL's WASAPI driver (windows)/SDL's PulseAudio or ALSA driver (linux)/SDL's CoreAudio driver (mac); allegro = Allegro's DirectSound8 driver (windows)/Allegro's PulseAudio, ALSA or OSS driver (linux)/Allegro's OpenAL driver (mac); allegro-via-sdl = Allegro mixer with SDL's WASAPI driver (windows)/not supported (linux + mac)
|-
| --debug-graphics
|
|enables debugging layer for graphics API. If DirectX is used DirectX SDK needs to be installed for this to work.
|-
| --fullscreen
| BOOL
|start game in windowed mode (saved to configuration)
|-
| --max-texture-size
| N
|maximal size of texture that the game can use (saved to configuration). Should be power of two greater than 2048
|-
| --graphics-quality
| arg
|accepted values: high, normal, low, very-low. low and very-low are deprecated and are migrated to normal.
|-
| --video-memory-usage
| arg
|accepted values: all, high, medium, low
|-
| --force-graphics-preset
| arg
|accepted values: very-low, low, mac-with-low-ram, medium-with-low-vram, medium, high, very-high, extreme
|-
| --gfx-safe-mode
|
|resets some graphics settings to values that should work on most configurations
|-
| --low-vram
|
|sprites that are not put into sprite atlases won't be allocated as texture objects
|-
| --shader
|
|enable/disable shader postprocessing (saved to configuration)
|-
| --disable-audio
|
|Disable audio. Mainly for faster startup during development.
|-
| --window-size
| arg
|Desired window resolution. For example "1680x1050". Or "maximized"
|-
| --single-thread-loading
|
|Disables loading of sprites in multiple threads.
|-
| --cache-sprite-atlas
| BOOL
|Enable/disable sprite atlas cache.
|-
| --nogamepad
|
|Disable gamepad(controller) support
|}

{| class="wikitable"
|+ Server options
|-
| --port
| N
|network port to use
|-
| --bind
| ADDRESS[:PORT]
|IP address (and optionally port) to bind to
|-
| --rcon-port
| N
|Port to use for RCON
|-
| --rcon-bind
| ADDRESS:PORT
|IP address and port to use for RCON
|-
| --rcon-password
| PASSWORD
|Password for RCON
|-
| --server-settings
| FILE
|Path to file with server settings. See data/server-settings.example.json
|-
| --use-authserver-bans
| BOOL
|Verify that connecting players are not banned from multiplayer and inform Factorio.com about ban/unban commands.
|-
| --use-server-whitelist
| BOOL
|If the whitelist should be used.
|-
| --server-whitelist
| FILE
|Path to file with server whitelist.
|-
| --server-banlist
| FILE
|Path to file with server banlist.
|-
| --server-adminlist
| FILE
|Path to file with server adminlist.
|-
| --console-log
| FILE
|Path to file where a copy of the server's log will be stored
|-
| --server-id
| FILE
|Path where server ID will be stored or read from
|}

=== Boolean options ===

Parameters shown above with a BOOL option must be formatted as <code>[parameter]=true</code> or <code>[parameter]=false</code>. For example,

--fullscreen=false

will start the game in windowed (not fullscreen) mode.

=== Multiplayer ===

--start-server SAVE

Will start a Headless (Dedicated) server, with no GUI.

--mp-connect ADDRESS
ADDRESS is the IP:port of the remote host. Port is optional.
Examples:

./factorio --mp-connect 192.168.1.101
./factorio --mp-connect 192.168.1.101:2345

As above, port can be specified by placing the port number after a colon in the address.

=== Creating a map from custom settings ===

Sometimes it's useful to create a new game with map and/or map generator settings stored in a JSON file rather than going through the in-game map settings screen.
One reason is that by editing the settings directly it is possible to set settings outside the range normally available from the GUI.

To do this, Factorio is run from the command-line, and a JSON file containing the map generator settings and a JSON file containing map settings (if customizing them) are needed.

Example for custom generator settings:
<pre>{
"terrain_segmentation": 0.5,
"water": "2",
"width": 0,
"height": 0,
"starting_area": "normal",
"peaceful_mode": false,
"autoplace_controls":
{
"coal": {"frequency": 1, "size": 2, "richness": 0.5},
"copper-ore": {"frequency": "low", "size": "normal", "richness": "high"},
"crude-oil": {"frequency": "normal", "size": "normal", "richness": "normal"},
"enemy-base": {"frequency": "normal", "size": "normal", "richness": "normal"},
"iron-ore": {"frequency": "normal", "size": "normal", "richness": "normal"},
"stone": {"frequency": "normal", "size": 0, "richness": "normal"},
"uranium-ore": {"frequency": "normal", "size": "none", "richness": "normal"}
},

"cliff_settings":
{
"name": "cliff",
"cliff_elevation_0": 30,
"cliff_elevation_interval": 20,
"richness": 1
},

"property_expression_names":
{
"elevation": "0_16-elevation",
"temperature": "35"
},

"seed": null
}
</pre>

Note that this is the same format as [https://lua-api.factorio.com/latest/Concepts.html#MapGenSettings MapGenSettings] that are modifiable from Lua. Everything in the file is optional.

Creating a custom save:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --create stuff-seed123.zip --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

Generating a map preview:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --generate-map-preview preview-seed123.png --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

==== Creating the JSON files from a map exchange string ====

It can be useful to create the initial JSON files from a known map exchange string instead of creating them from scratch. To convert the map exchange string to JSON, open the game and run the following command with your map exchange string:

/c game.write_file('map.txt', game.table_to_json(game.parse_map_exchange_string("<your exchange string here>")))

Then open the script_output folder in the [[user data directory]] and open map.txt - it will look like this:

{"map_settings":{ ...<MAP_SETTINGS> ... },"map_gen_settings":{ ...<MAP_GEN_SETTINGS>... }}

Copy the { ...<MAP_SETTINGS> ... } section into a new file called 'map-settings.json' in the desired location. Copy the { ...<MAP_GEN_SETTINGS> ... } section section into a new file called 'map-gen-settings.json' in the desired location.

== See also ==
* [[Console]]

{{C|Modding}}