Agreed, this isn't ideal but it can work.
I personally would do something more organized, like below. OP, if you can provide some use-cases for how your plugin will be utilizing costumes, I can make adjustments.
PHP Code:
#include <amxmodx>
enum CostumeTypes
{
Male1,
Male2,
Female1
}
enum CostumeGender
{
Male,
Female
}
enum CostumeModels
{
CostumeGender:Gender,
Hat[ 50 ],
Shirt[ 50 ],
Pants[ 50 ],
Shoes[ 50 ]
}
new CostumeData[ CostumeTypes ][ CostumeModels ] =
{
{ Male , "models/costume/male1_hat.mdl" , "models/costume/male1_shirt.mdl" , "models/costume/male1_pants.mdl" , "models/costume/male1_shoes.mdl" },
{ Male , "models/costume/male2_hat.mdl" , "models/costume/male2_shirt.mdl" , "models/costume/male2_pants.mdl" , "models/costume/male2_shoes.mdl" },
{ Female , "models/costume/female1_hat.mdl" , "models/costume/female1_shirt.mdl" , "models/costume/female1_pants.mdl" , "models/costume/female1_shoes.mdl" }
}
public plugin_init()
{
server_print( "%s %s %s %s" , CostumeData[ Male1 ][ Hat ] , CostumeData[ Male1 ][ Shirt ] , CostumeData[ Male1 ][ Pants ] , CostumeData[ Male1 ][ Shoes ] );
server_print( "%s %s %s %s" , CostumeData[ Male2 ][ Hat ] , CostumeData[ Male2 ][ Shirt ] , CostumeData[ Male2 ][ Pants ] , CostumeData[ Male2 ][ Shoes ] );
server_print( "%s %s %s %s" , CostumeData[ Female1 ][ Hat ] , CostumeData[ Female1 ][ Shirt ] , CostumeData[ Female1 ][ Pants ] , CostumeData[ Female1 ][ Shoes ] );
}
__________________