mirror of
https://github.com/godotengine/godot.git
synced 2024-11-10 14:12:51 +00:00
doc: Clarify need to save ConfigFile to apply changes to file
See #52645 for context.
(cherry picked from commit fd8bdddd5d
)
This commit is contained in:
parent
8e55a1870f
commit
1c1bc75e28
@ -45,6 +45,7 @@
|
||||
var player_score = config.get_value(player, "best_score")
|
||||
score_data[player_name] = player_score
|
||||
[/codeblock]
|
||||
Any operation that mutates the ConfigFile such as [method set_value], [method clear], or [method erase_section], only changes what is loaded in memory. If you want to write the change to a file, you have to save the changes with [method save], [method save_encrypted], or [method save_encrypted_pass].
|
||||
Keep in mind that section and property names can't contain spaces. Anything after a space will be ignored on save and on load.
|
||||
ConfigFiles can also contain manually written comment lines starting with a semicolon ([code];[/code]). Those lines will be ignored when parsing the file. Note that comments will be lost when saving the ConfigFile. This can still be useful for dedicated server configuration files, which are typically never overwritten without explicit user action.
|
||||
[b]Note:[/b] The file extension given to a ConfigFile does not have any impact on its formatting or behavior. By convention, the [code].cfg[/code] extension is used here, but any other extension such as [code].ini[/code] is also valid. Since neither [code].cfg[/code] nor [code].ini[/code] are standardized, Godot's ConfigFile formatting may differ from files written by other programs.
|
||||
@ -55,6 +56,7 @@
|
||||
<method name="clear">
|
||||
<return type="void" />
|
||||
<description>
|
||||
Removes the entire contents of the config.
|
||||
</description>
|
||||
</method>
|
||||
<method name="erase_section">
|
||||
|
Loading…
Reference in New Issue
Block a user