[Bacardi]

Open file ...addons/sourcemod/data/MyKv.txt

Re-open that file when new players has joined server.

This now only save players name who join into server.

PHP Code:



KeyValues MyKv;

public void OnPluginStart()
{
    char buffer[PLATFORM_MAX_PATH];
    BuildPath(Path_SM, buffer, sizeof(buffer), "data/MyKv.txt");

    MyKv = new KeyValues("data");
    MyKv.ImportFromFile(buffer);
}

public void OnClientPostAdminCheck(int client)
{
    if(IsFakeClient(client)) return;

    char buffer[PLATFORM_MAX_PATH];

    GetClientAuthId(client, AuthId_Engine, buffer, sizeof(buffer));

    MyKv.JumpToKey(buffer, true); // Find or Create entry

    GetClientName(client, buffer, sizeof(buffer));

    MyKv.SetString("name", buffer);
    MyKv.Rewind();

    BuildPath(Path_SM, buffer, sizeof(buffer), "data/MyKv.txt");
    MyKv.ExportToFile(buffer);
} 


[BraveFox]

Originally Posted by Bacardi Open file ...addons/sourcemod/data/MyKv.txt Re-open that file when new players has joined server. This now only save players name who join into server. PHP Code: KeyValues MyKv; public void OnPluginStart() {     char buffer[PLATFORM_MAX_PATH];     BuildPath(Path_SM, buffer, sizeof(buffer), "data/MyKv.txt");     MyKv = new KeyValues("data");     MyKv.ImportFromFile(buffer); } public void OnClientPostAdminCheck(int client) {     if(IsFakeClient(client)) return;     char buffer[PLATFORM_MAX_PATH];     GetClientAuthId(client, AuthId_Engine, buffer, sizeof(buffer));     MyKv.JumpToKey(buffer, true); // Find or Create entry     GetClientName(client, buffer, sizeof(buffer));     MyKv.SetString("name", buffer);     MyKv.Rewind();     BuildPath(Path_SM, buffer, sizeof(buffer), "data/MyKv.txt");     MyKv.ExportToFile(buffer); }

thank you
I will test it later.

[Kolapsicle]

https://sm.alliedmods.net/new-api/keyvalues

[Vergil333]

Originally Posted by shavit have fun with files over 10mb and insane server lag when you read them to memory.. don't you think a database is a more proper approach?

This interests me. I'm catching a few events and storing them to a multiarray. After a match an array is inserted to db and unset/null/erased/whatever.

An array can have 500 rows... 500 times 4 columns... Let's say 10 characters per value...
500x4x10 = 20 000 bytes.

So stored array can reach 20 kB? That's low for causing any lag... isn't it???

[Kolapsicle]

Originally Posted by Vergil333 This interests me. I'm catching a few events and storing them to a multiarray. After a match an array is inserted to db and unset/null/erased/whatever. An array can have 500 rows... 500 times 4 columns... Let's say 10 characters per value... 500x4x10 = 20 000 bytes. So stored array can reach 20 kB? That's low for causing any lag... isn't it???

A hard drive is a lot slower than a CPU or RAM, accessing (reading/writing to) it regularly is something you want to avoid if possible, especially when dealing with a single thread that has a lot of work to do. Utilizing a database on a separate thread circumvents the issue of interrupting the main game thread. Not to mention the vast benefits an SQL database holds over a locally stored raw text file.

[shavit]

Originally Posted by Vergil333 This interests me. I'm catching a few events and storing them to a multiarray. After a match an array is inserted to db and unset/null/erased/whatever. An array can have 500 rows... 500 times 4 columns... Let's say 10 characters per value... 500x4x10 = 20 000 bytes. So stored array can reach 20 kB? That's low for causing any lag... isn't it???

but OP wants -keyvalues- that will have a new subkey for every unique player

so..

"{{key}}"
{
	"{{STEAMID}}"
	{
		"Name"	"{{NAME}}"
	}
	
	"{{STEAMID}}"
	{
		"Name"	"{{NAME}}"
	}

	
	"{{STEAMID}}"
	{
		"Name"	"{{NAME}}"
	}

	
	"{{STEAMID}}"
	{
		"Name"	"{{NAME}}"
	}

	
	"{{STEAMID}}"
	{
		"Name"	"{{NAME}}"
	}
	
	... /* and so on */
}

i have had over 10,000 unique players in one of my servers, imagine such a large file being read and written to every time a player joins (read) and if he's new, also write
= insane lag

[Potato Uno]

Keyvalues are horrible for data storage, great for parsing config files.

Use SQLite if you want data storage. Leverage SQL without needing an SQL server.