Get Value of a Custom Item Property?

[Legacy_Zeke]

               

After tinkering with CEP I saw a new Item property - Use Limitation: Gender.

 

 

It doesn't have or at least I can't find any functionalities implemented, so I started implementing my own. I saw in itempropdef.2da that the ID of the property is 150 and that it is getting its values from gender.2da

 

 

The problem is that I can't get what gender is selected (I think it's called subtype?) for it to limit.

 

GetItemPropertyCostTableValue() in the following function always returns 0:

// This scipt is attached on OnPlayerEquipItem

object oItem = GetPCItemLastEquipped();
object oPC   = GetPCItemLastEquippedBy();
itemproperty ipLoop = GetFirstItemProperty(oItem);

while (GetIsItemPropertyValid(ipLoop))
{   
   if  (GetItemPropertyType(ipLoop) == 150 ) // Check to see if the item has UseLimitationGender
      {
         int nCost = GetItemPropertyCostTableValue(ipLoop);
         SendMessageToPC(oPC, IntToString(nCost));
      }

   ipLoop = GetNextItemProperty(oItem);
}

I guess GetItemPropertyCostTableValue() is not the function I have to use?

 

 

Yes, I know all of this can be achieved with a simple variable on the equipment but I want to use the property (it has a text in the game interface).

               
               

               
            

[Legacy_meaglyn]

               

You want the subtype. i.e. : GetItemPropertySubType(ipLoop).

               
               

               
            

[Legacy_Zeke]

               

Ah, sounds so logical. Couldn't find this function in the Lexicon... Thank you, once again!

               
               

               
            

[Legacy_Zeke]

               

Oh, and now - a bonus question time!

 

Is there OnEquip for henchmen? Because currently, if I make Female-Only Armor, I can equip it on a male henchman.

               
               

               
            

[Legacy_Proleric]

               

No, OnPlayerEquipItem is only for players. You have to prevent the henchman from acquiring the item in OnAcquireItem. This is my custom code for single player:

 

   Spoiler
   

object oPC   = GetModuleItemAcquiredBy();
     if (!GetIsPC(oPC))
       if (!GetIsPC(GetMaster(oPC))) return;
     string sItem = GetTag(oItem);
     // Custom code - stop PC giving inappropriate gender-specific clothing to companions.
     // Inventory panels refreshed to prevent ghosting visuals.
    if (!GetIsPC(oPC))
      if (GetLocalInt(GetFirstPC(), "join" + GetTag(oPC)))
        {
          int bInvalid = FALSE;
          if (GetItemHasItemProperty(oItem, ITEM_PROPERTY_USE_LIMITATION_GENDER))
            {
              itemproperty ipGenderProperty=GetFirstItemProperty(oItem);
              while ((GetIsItemPropertyValid(ipGenderProperty))
                   &&(GetItemPropertyType(ipGenderProperty)!=ITEM_PROPERTY_USE_LIMITATION_GENDER))
                {
                  ipGenderProperty=GetNextItemProperty(oItem);
                }
              if (GetItemPropertySubType(ipGenderProperty)!=GetGender(oPC))
                {
                  SetCustomToken(12, "The " + GetStringLowerCase(GetName(oItem)) + " doesn't fit " + GetName(oPC));
                  bInvalid = TRUE;
                }
            }
 
           if (bInvalid)
             {
                  AssignCommand(oPC, ActionGiveItem(oItem, GetFirstPC()));
                  OpenInventory(oPC, GetFirstPC());
                  OpenInventory(GetFirstPC(), GetFirstPC());
                  AssignCommand(GetFirstPC(), ActionStartConversation(GetFirstPC(), "zzComment", FALSE, FALSE));
                  return;
             }
         }

 

Sorry that oPC is a confusing variable name, it ought to be oHenchman or whatever, but I don't have time to edit it this morning!

               
               

               
            

[Legacy_meaglyn]

               

@proleric, does that actually work? I've been under the impression that OnAcquireItem and friends also only fire for PCs. 

               
               

               
            

[Legacy_Proleric]

               Yes, it works. Live code from my Dark Energy module. OnPlayerX events only work for player (the clue is in the name) but OnAcquireItem works for NPCs.
               
               

               
            

[Legacy_meaglyn]

               

Interesting!

 

Someone should update some of the lexicon pages then.  Grimlar's Tag based scripting tutorial, for example, clearly says no (at least in the CHM version).  Having read that I had not bothered looking at it closely...  Does it fire when stores acquire items or just creature objects? Chests?

 

I like the ghosting visuals hack. I'm going to crib that one for my cursed item stuff which has that issue '>

               
               

               
            

[Legacy_meaglyn]

               

Well cool.  Seems to fire for all creatures. How about activate? I did not think you could make NPCs activate item special powers.   I guess I need to use a bigger grain of salt when looking at the lexicon '>

               
               

               
            

[Legacy_Proleric]

               I don't know of a way to force a creature to activate an item (unless there is some backdoor using spell functions). If that's correct, then OnActivateItem is player-only.


You could, of course, by-pass the event, by modding the creature AI to execute a similar script if it has the item in inventory and ought to activate it. I do something like that with thieves' tools, for example.
               
               

               
            

[Legacy_Zeke]

               

Aah, this worked! Nice!

 

What is the purpose of the last line (the conversation one)?

 

And what is that ghosting visuals hack that meaglyn talks about?

               
               

               
            

[Legacy_Proleric]

               The conversation simply displays custom token 12. Sorry, should have explained that. If you prefer floaty text or a message instead, no problem. I prefer conversation because it's more obvious and has to be cleared by the player once read.


Dummy out the OpenInentiory lines to see the ghosting they prevent.