[MeRcyLeZZ]

Settings API

API to load/save settings in a Key+Value format that resembles Windows INI files (http://en.wikipedia.org/wiki/INI_file).

What's new is you can store a variable amount of values in a single key, supporting the use of amxx dyamic arrays.

Use Case:

You want your plugin to use custom sounds and models, then allow users to change them. Previously it would require coding a section into the .sma file, making recompile necessary every time you want to change something. This API allows resources to be edited "externally" through the INI file instead.

Example:

Load admin knife models from file, store them in dynamic array. If section/key is not found, a new entry will be added automatically.

#define SETTINGS_FILE "plugin_resources.ini"
#define MODEL_MAX_LENGTH 64

new const default_model_vknife[] = { "models/v_knife.mdl" } // Default model
new Array:g_array_models_admin_vknife

public plugin_precache()
{
    g_array_models_admin_vknife = ArrayCreate( MODEL_MAX_LENGTH, 1 )
    
    if ( !amx_load_setting_string_arr( SETTINGS_FILE, "Admin Models", "V_KNIFE", g_array_models_admin_vknife ) )
    {
        amx_save_setting_string( SETTINGS_FILE, "Admin Models", "V_KNIFE", default_model_vknife )
        ArrayPushString( g_array_models_admin_vknife, default_model_vknife )
    }
}

File syntax:

; Add custom admin models here
[Admin Models]
V_KNIFE = models/admin/v_knife_dragon.mdl , models/admin/v_knife_nyan.mdl , models/admin/v_knife3.mdl

Usage:

Download files below into your scripting folder, then do: #include <amx_settings_api>.

[NiHiLaNTh]

Awesome, finally you released it.

[meTaLiCroSS]

What's the difference between using "txt" files and "ini" files? Or "cfgs", and others? I don't really know

This would be good as a 3rd party module, for avoiding usage

[Arkshine]

I think I will try to import TextParser from SourceMod. It supports INI and Json format. An unified API would be welcomed.

[fysiks]

I guess I really don't understand the purpose. It appears to me that it's just a global .ini file that can be used by several plugins at once instead of each plugin using it's own.

Originally Posted by meTaLiCroSS What's the difference between using "txt" files and "ini" files? Or "cfgs", and others? I don't really know

A .ini file is a text file with a specific syntax. Take a look at the Wikipedia document linked to in the original post.

[joropito]

Originally Posted by meTaLiCroSS What's the difference between using "txt" files and "ini" files? Or "cfgs", and others? I don't really know

As fysiks said, it's just a text format to save Key/Values in groups.

[section1] a=a b=b [section2] a=1234 color=blue

Originally Posted by fysiks I guess I really don't understand the purpose. It appears to me that it's just a global .ini file that can be used by several plugins at once instead of each plugin using it's own.

If you write an application with a lot of settings to be saved somehow, sometimes INI format it's useful. Just that. Not only to share settings between plugins, you can use this in just one plugin, but a big one like ZP.

[CryWolf]

MeRcyLeZZ, Thanks man it's awesome, but one question ZP4.3fix5a is using this method for saving loading ?

I think i will go back from ZP5.0.8 to 4.3Fix5a but not shure, just asked

[Backstabnoob]

Originally Posted by Arkshine I think I will try to import TextParser from SourceMod. It supports INI and Json format. An unified API would be welcomed.

Yes please, I totally need JSON for my current project. Or SMJansson

[TheDS1337]

Originally Posted by CryWolf MeRcyLeZZ, Thanks man it's awesome, but one question ZP4.3fix5a is using this method for saving loading ? I think i will go back from ZP5.0.8 to 4.3Fix5a but not shure, just asked

ZP 5.0 versions using this method, older versions doesn't

[meTaLiCroSS]

Originally Posted by fysiks I guess I really don't understand the purpose. It appears to me that it's just a global .ini file that can be used by several plugins at once instead of each plugin using it's own. A .ini file is a text file with a specific syntax. Take a look at the Wikipedia document linked to in the original post.

Yeah, I saw it, but it changes something the "readability" of it? Would be different reading a .txt from a .ini?