[Natsheh]

Show the variables definition.

[abdelwahab]

enum any:TYPES
{
PACKS = 0,
POINTS,
COINS
}
new g_PlayerGamePoints[33][TYPES]
new g_level[33]
new g_exp[33]
new g_zombieclass[33]
new g_zombieclassnext[33]
new g_humanclass[33]
new g_humanclassnext[33]

[Bugsy]

Originally Posted by abdelwahab hmm 2 separate plugins ?

If you have 1 or 50 plugins it doesn't matter to the rule, from an individual data record perspective, nvault_get can only be used with nvault_set, and nvault_get_array can only be used with nvault_set_array. A vault file can have a mixture of regular nvault and nvault array data.

[abdelwahab]

Originally Posted by Bugsy If you have 1 or 50 plugins it doesn't matter to the rule, from an individual data record perspective, nvault_get can only be used with nvault_set, and nvault_get_array can only be used with nvault_set_array. A vault file can have a mixture of regular nvault and nvault array data.

Is it possible to use the same vault from another plugin ?

[Natsheh]

Since you're using individual players arrays to save players data you need to use nvault_set/get instead of nvault_set/grt_array

[Bugsy]

Right, you could consolidate all player data items to a single nvault array record for each player, instead of having multiple nvault records for each data item, for each player.

So with nvault array you could have this for each player:

Key:STEAM:0:12345
Data: <Points, XP, Money>

Instead of all of these for each player

Key:STEAM:0:12345_Points
Data: Points value

Key:STEAM:0:12345_XP
Data: XP value

Key:STEAM:0:12345_Money
Data: Money value