Quote:
Originally Posted by FlaminSarge
I can try the steamid and menu stuff.
|
Neat. For the Steam ID stuff, I'd do something like this (keep in mind this example doesn't use actual coding, it's just a simple example)
PHP Code:
if (weapon has steam id field)
{
if (weapons steam id matches players steam id)
{
GivePlayerTheWeapon();
}
else
{
PrintToChat(client, "This weapon isn't for you");
}
}
But yeah, ignore the fake if statements and what not. You should get the idea of what I'm trying to suggest
Of course, if the Steam ID thing gets implemented, you'll have to add coding for the menus that checks a player's Steam ID and adds any weapons that have their Steam ID listed as the "steamid" field, to the proper slot, and for the proper class.
And that's another thing I forgot to mention. Adding a "class" field for the weapons would be nice so we could specify which class a weapon is for, so other classes can't use it, plus it'd allow you to set up class-based menus.
But we run into the issue of weapons that multiple classes can use, such as the Pain Train, Half-Zatoichi, Lugermorph, etc. Maybe the option of doing:
"class" "SOLDIER, SCOUT"
And have some defines set up like so:
#define SOLDIER TFClass_Soldier
#define SCOUT TFClass_Scout