[klippy]

You should do some reading on database normalization. That's not the only possible way, and it's a bad one.

If you happen to normalize your database properly, I would advise against using Steam ID as a primary key. I would leave Steam ID as a unique key, but make a new auto-increment column and set it to primary key, and use that new 'database ID' for all future queries. It should make joins faster and possibly other simple queries.
If you continue having all skill levels in the same column, you will most likely run into a wall if you try to add new skills or remove old ones.

EDIT:
Also, you should (more like 'must' than 'should') use threaded queries to avoid lagspikes, especially if the database server is not hosted on the same machine.

[Bugsy]

We could take a stab at this using nvault_get/setarray using nvault utility. If you do not need top15 or any querying or web interaction then it should be ok.

[WAR3DM]

Originally Posted by KliPPy I would leave Steam ID as a unique key

That's the plan.

Originally Posted by KliPPy If you continue having all skill levels in the same column, you will most likely run into a wall if you try to add new skills or remove old ones.

An easy fix.

Originally Posted by KliPPy Also, you should (more like 'must' than 'should') use threaded queries to avoid lagspikes, especially if the database server is not hosted on the same machine.

Converting to multi-thread sounds difficult.

Originally Posted by Bugsy We could take a stab at this using nvault_get/setarray using nvault utility. If you do not need top15 or any querying or web interaction then it should be ok.

Sounds good, I don't need top15 or web interaction.

[Bugsy]

Here's a simple nVault way to do it.

PHP Code:

#include <amxmodx>
#include <nvault_util>

#define MAX_PLAYERS 32

const MAX_SKILLS = 9;

new g_PlayerSkills[ MAX_PLAYERS + 1 ][ MAX_SKILLS ];
new g_szAuthID[ MAX_PLAYERS + 1 ][ 34 ];
new g_Vault;

public plugin_init() 
{
    register_clcmd( "say setskills" , "SetFakeSkills" );
    
    g_Vault = nvault_open( "SkillsVault" );
}

public client_authorized( id )
{
    new iTS;
    
    get_user_authid( id , g_szAuthID[ id ] , charsmax( g_szAuthID[] ) );
    
    if ( nvault_get_array( g_Vault , g_szAuthID[ id ] , g_PlayerSkills[ id ] , sizeof( g_PlayerSkills[] ) , iTS ) )
    {
        server_print( "Skills loaded %d %d %d %d %d %d %d %d" , g_PlayerSkills[ id ][ 0 ] , g_PlayerSkills[ id ][ 1 ] ,
                                    g_PlayerSkills[ id ][ 2 ] , g_PlayerSkills[ id ][ 3 ] ,
                                    g_PlayerSkills[ id ][ 4 ] , g_PlayerSkills[ id ][ 5 ] ,
                                    g_PlayerSkills[ id ][ 6 ] , g_PlayerSkills[ id ][ 7 ] ,
                                    g_PlayerSkills[ id ][ 8 ] );
    }
    else
    {
        server_print( "No skills exist" );
    }
}

public client_disconnect( id )
{
    nvault_set_array( g_Vault , g_szAuthID[ id ] , g_PlayerSkills[ id ] , sizeof( g_PlayerSkills[] ) );
}

public SetFakeSkills( id )
{
    for ( new i = 0 ; i < MAX_SKILLS ; i++ )
        g_PlayerSkills[ id ][ i ] = random_num( 50, 100 );

    nvault_set_array( g_Vault , g_szAuthID[ id ] , g_PlayerSkills[ id ] , sizeof( g_PlayerSkills[] ) );
} 


[WAR3DM]

Awesome, thanks for the example!

Unfortunately, it outputs "øªªªbøªªªTøªªªAøªªªdøªªª4øªªªcøªªª;øªªªPøªªª _" next to my Steam_ID.

[Bugsy]

Read the nvault utility thread. nvault_set stores the data in binary format so you cannot use an nvault editor app to view the data. It is stored correctly, though it will not appear that way in a viewer application.

[WAR3DM]

Originally Posted by Bugsy Read the nvault utility thread. nvault_set stores the data in binary format so you cannot use an nvault editor app to view the data. It is stored correctly, though it will not appear that way in a viewer application.

Perfect, thanks!