[Facksy]

Hey i got problems with keyvalues:

PHP Code:

public Action:Test(client, args)
{
    BuildPath(Path_SM, KvPath, sizeof(KvPath), "configs/admins.cfg");
    new Handle:DB = CreateKeyValues("ddd");
    FileToKeyValues(DB, KvPath);
} 


It replies me:

KeyValues Error: LoadFromBuffer: missing { in file addons\sourcemod\configs\admi
ns.cfg
(*Admins*), (*Me*),
KeyValues Error: LoadFromBuffer: missing { in file addons\sourcemod\configs\admi
ns.cfg
(*Admins*), (*Me*),

My admins.cfg is like that:

Admins
{
    "Me"
    {
		"auth"			"steam"
		"identity"		"STEAM_0:0:75807078"
		"flags"			"z"
    }
}

Can you help me?

[Spirit_12]

First of all try using the new Syntax.

PHP Code:

public Action Test(int client, int args)
{
    BuildPath(Path_SM, KvPath, sizeof(KvPath), "configs/admins.cfg");
    KeyValues kv = new KeyValues("ddd");
    kv.ImportFromFile(KvPath);    
} 


Your admins.cfg file seems a bit off as well. I'm sure someone will correct me, if I'm wrong, but I think this is how it should be.

PHP Code:

"Me"
{
    "auth"            "steam"
    "identity"        "STEAM_0:0:75807078"
    "flags"            "z"
} 


If you want to use a custom tree then you need "" around admins like this.

PHP Code:

"Admins"
{
    "Me"
    {
        "auth"            "steam"
        "identity"        "STEAM_0:0:75807078"
        "flags"            "z"
    }
} 


[Facksy]

Even with these changes it doesnt worj

[Facksy]

Alright, i fixed, strangely it was this part which is supposed to be a comment:

**
 * USE THIS SECTION TO DECLARE DETAILED ADMIN PROPERTIES.
 *
 * Each admin should have its own "Admin" section, followed by a name.
 * The name does not have to be unique.
 *
 * Available properties: (Anything else is filtered as custom)
 *      "auth"          - REQUIRED - Auth method to use.  Built-in methods are:
 *                        "steam"  - Steam based authentication
 *                        "name"   - Name based authentication
 *                        "ip"	- IP based authentication
 *                        Anything else is treated as custom.
 *					 Note: Only one auth method is allowed per entry.
 *
 *      "identity"      - REQUIRED - Identification string, for example, a steamid or name.
 *					 Note: Only one identity is allowed per entry.
 *
 *      "password"      - Optional password to require.
 *      "group"         - Adds one group to the user's group table.
 *      "flags"         - Adds one or more flags to the user's permissions.
 *		"immunity"		- Sets the user's immunity level (0 = no immunity).
 *						  Immunity can be any value.  Admins with higher 
 *						  values cannot be targetted.  See sm_immunity_mode 
 *						  to tweak the rules.  Default value is 0.
 *
 * Example:
	"BAILOPAN"
	{
		"auth"			"steam"
		"identity"		"STEAM_0:1:16"
		"flags"			"abcdef"
	}
 *
 */

When i remove it, it doesnt reply any errors

[Fyren]

You can't have multiline comments in KeyValues.

[ddhoward]

If you want to parse a Sourcemod config file with a custom plugin (and keep multiline comments), you'll probably need to use SMCParser rather than KeyValues.

Good luck though, there's almost zero documentation that I've found.

[Powerlord]

Originally Posted by ddhoward If you want to parse a Sourcemod config file with a custom plugin (and keep multiline comments), you'll probably need to use SMCParser rather than KeyValues. Good luck though, there's almost zero documentation that I've found.

SMCParser doesn't get used a lot because it's literally a library for writing the equivalent of the API KeyValues already gives you.

In other words, it's a lot of extra work for very little benefit.

[Fyren]

Originally Posted by Powerlord In other words, it's a lot of extra work for very little benefit.

SMC is better when you don't want to deal with the bugs, slowness, and limitations of Valve's KV implementation.

Originally Posted by ddhoward Good luck though, there's almost zero documentation that I've found.

SMC is basically a SAX-style parser as opposed to DOM. You get callbacks as the input is walked through. The header is pretty short to read through and there are examples of usage in the base SM plugins.