Difference between revisions of "Modding:Modder Guide/APIs/Config"
Taskmaster (talk | contribs) m (→Using the config file: turned 3 line comment into 1 line to improve readability) |
Pathoschild (talk | contribs) (undo change to standardized comment headers (see user talk page)) |
||
Line 58: | Line 58: | ||
public class ModEntry : Mod | public class ModEntry : Mod | ||
{ | { | ||
− | /********* Properties *********/ | + | /********* |
− | + | ** Properties | |
+ | *********/ | ||
/// <summary>The mod configuration from the player.</summary> | /// <summary>The mod configuration from the player.</summary> | ||
private ModConfig Config; | private ModConfig Config; | ||
− | /********* Public methods *********/ | + | /********* |
− | + | ** Public methods | |
+ | *********/ | ||
/// <summary>The mod entry point, called after the mod is first loaded.</summary> | /// <summary>The mod entry point, called after the mod is first loaded.</summary> | ||
/// <param name="helper">Provides simplified APIs for writing mods.</param> | /// <param name="helper">Provides simplified APIs for writing mods.</param> |
Revision as of 17:36, 18 September 2019
- Get started
- Game fundamentals
- Test & troubleshoot
- Release
- API reference
- Basic SMAPI APIs:
- Advanced SMAPI APIs:
- Specific guides
You can let users configure your mod through a standard config.json file. SMAPI will automatically create the file and take care of reading, normalising, and updating it.
Config model
Creating a config model
The config model is a C# class you create, with properties representing the settings you want to store. It can contain almost anything from a few boolean fields to a complex object graph (though you should try to keep things simple for players). Here's a simple config model:
class ModConfig
{
public bool ExampleBoolean { get; set; }
public int ExampleNumber { get; set; }
}
That model would be saved to config.json with this content:
{
"ExampleBoolean": false,
"ExampleNumber": 0
}
Default values
You can set default values in your data model:
class ModConfig
{
public bool ExampleBoolean { get; set; } = true;
public int ExampleNumber { get; set; } = 5;
}
...or set defaults with a constructor:
class ModConfig
{
public bool ExampleBoolean { get; set; }
public int ExampleNumber { get; set; }
public ModConfig()
{
this.ExampleBoolean = true;
this.ExampleNumber = 5;
}
}
Using the config file
To read the config.json (SMAPI will create it automatically):
- Create your config model.
- Access the config values in your ModEntry class:
/// <summary>The main entry point for the mod.</summary> public class ModEntry : Mod { /********* ** Properties *********/ /// <summary>The mod configuration from the player.</summary> private ModConfig Config; /********* ** Public methods *********/ /// <summary>The mod entry point, called after the mod is first loaded.</summary> /// <param name="helper">Provides simplified APIs for writing mods.</param> public override void Entry(IModHelper helper) { this.Config = this.Helper.ReadConfig<ModConfig>(); bool exampleBool = this.Config.ExampleBoolean; } }
That's it! When the player launches the game, SMAPI will create the config.json file automatically if it doesn't exist yet, using the default config options you provided in your model. If you need to save some changes, you can use this.Helper.WriteConfig(this.Config).