Hi Dvinn!
Two ways you could go about this:
a) add the weapon skill as a saved value on the object (Whisky's recommended way!)
If you haven't changed the object values from stock code you could use GET_OBJ_VAL(obj, 0)
In oedit.c you'll find that value 0 has a comment saying /* This doesn't seem to be used if I remember right. */
And they are right, although in oedit you get prompted for 'Modifer to Hitroll', it isn't ever implemented.
So GET_OBJ_VAL(obj, 0) can be used to find the skill required for the weapon.
Change the Modifier to Hitroll to say 'Number of weapon skill' or you can add a function to list the skills by name
if you want to be fancy.
Search for case OEDIT_VALUE_1:
and under the item type remove the values -50 and 50 like this:
Code:
case ITEM_WEAPON:
GET_OBJ_VAL(OLC_OBJ(d), 0) = MIN(MAX(atoi(arg), LOWEST_WEAPON_SKILL_HERE), HIGHEST_WEAPON_SKILL_HERE);
break;
Then just use the improve_skill function like this:
Code:
struct obj_data *weapon = GET_EQ(ch, WEAR_WIELD);
if (weapon)
improve_skill(ch, GET_OBJ_VALUE(weapon, 0));
Beware that calling GET_OBJ_VALUE will crash the MUD if you haven't confirmed the object exists.
b) use the weaponprof method of determining the skill based on the attack message (limits weapon messages - eg: all swords slashing etc)
You can quickly duplicate the code from 'int get_weapon_prof()' to just return the actual skill number.
Happy to help if you need a hand with either way.
