In case you want to prepare for the next version, the new customweaps will look something like this:
PHP Code:
"custom_weapons_v3"
{
"STEAM_0:1:13776935 ; STEAM_0:1:17919459"
{
"12"
{
"quality" "5"
"level" "100"
"admin-flags" "a"
"1" "134 ; 2"
"2" "2 ; 100"
"3" "4 ; 10"
"4" "6 ; 0.25"
}
"12"
{
"quality" "4"
"level" "50"
}
"18"
{
"quality" "1"
"level" "100"
"1" "134 ; 2"
"2" "2 ; 100"
"3" "4 ; 10"
"4" "6 ; 0.25"
}
"45"
{
"quality" "3"
"level" "10"
"1" "134 ; 2"
"2" "2 ; 100"
"3" "4 ; 10"
"4" "6 ; 0.25"
"5" "16 ; 500"
"6" "26 ; 250"
"7" "31 ; 10"
"8" "123 ; 3"
"9" "134 ; 4"
"10" "3 ; 0.17"
"11" "97 ; 0.6"
"12" "106 ; 0.5"
}
"4"
{
"quality" "9"
"level" "10"
}
}
"*"
{
"4"
{
"quality" "2"
"level" "50"
}
"*"
{
"quality" "3"
}
}
}
- Multiple SteamIDs can be specified on the same block, delimited by the ";" character. Only define each SteamID once.
- Added the admin-flags key wich can be used to specify flag restriction for that weapon entry. If you want to have fallback cases if the player doesn't meet the requires flags, remember to put them in the specific order. The plugin will always retrieve the first item that can be usable, so if you put the admin restricted after the fallback one, it'll get ignored.
- There's no need to input the number of attributes the weapon will use, just place them in the correct order. The key name is the attribute number. The value uses the format "<id> ; <value>".