godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-07 02:12:07 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update feature_tags.rst

Browse Source
This commit is contained in:
corrigentia
2018-12-10 18:01:30 +02:00
committed by GitHub
parent 6761462a19
commit 984d6ecb0c
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
getting_started/workflow/export/feature_tags.rst
View File

@@ -89,7 +89,7 @@ Here is a list of most feature tags in Godot. Keep in mind they are **case-sensi
Custom features
---------------
It is possible to add custom features to a build, use the relevant
It is possible to add custom features to a build; use the relevant
field in the *export preset* used to generate it:
.. image:: img/feature_tags1.png
@@ -98,10 +98,10 @@ Overriding project settings
---------------------------
Features can be used to override specific configuration values in the *Project Settings*.
This allows to better customize any configuration when doing a build.
This allows you to better customize any configuration when doing a build.
In the following example, a different icon is added for the demo build of the game (which was
customized in a special export preset which, in turn, includes only demo levels).
customized in a special export preset, which, in turn, includes only demo levels).
.. image:: img/feature_tags2.png
@@ -112,7 +112,7 @@ After overriding, a new field is added for this specific configuration:
Default overrides
-----------------
There are already a lot of settings that come with overrides by default, they can be found
There are already a lot of settings that come with overrides by default; they can be found
in many sections of the project settings.
.. image:: img/feature_tags4.png
@@ -121,4 +121,4 @@ Customizing Build
------------------
Feature tags can be used to customize a build process too, by writing a custom **ExportPlugin**.
They also are used to specify which shared library is loaded and exported in **GDNative**.
They are also used to specify which shared library is loaded and exported in **GDNative**.