4 réponses à ce sujet

[Nebril2]

Hi all!

 

 

I want to make a companion npc wich you can modify inventory as you wish, one armed.

 

So, he  has his right hand invisible, and i want to make it impossible to equip items in that hand.

 

I tried creating an invisible object (fashion) wich goes in the right hand and flaging it cursed, but can be unequiped. 

 

There is a way to flag items as un-unequipables?

 

Or maybe another idea. 

 

Thank you.

[Proleric]

I have a very similar problem with an NPC who has to keep a stick in her left hand, because she only has one good leg.

 

I'd be very interested if anyone has a better solution.

 

The frustration is that the OnEquip event doesn't fire for companions.

 

The kludge I came up with is to use the companion's OnHeartbeat to check that the stick is still in the left hand. In my case, it doesn't look too bad - if the PC forces an item into her left hand, or a two-handed item into her right hand, she almost immediately re-equips the stick. In your case, you might want a pseudoheartbeat running very frequently (once per second?) to make it seem that the right hand can't be equipped.

 

Another consideration is that my henchman AI equips the most effective weapon. I have the following system to prevent two-handed weapons being equipped:

 

Spoiler

In the OnItemAcquire event:

// Custom code - for Rosalind, nerf two-handed weapons
     if ((GetTag(oPC) == "ROSALIND")
     &&   bh_check_weapon(oItem))
       {
         string sWeaponWield = Get2DAString("baseitems", "WeaponWield", GetBaseItemType(oItem));
         if ((sWeaponWield != "1")    // One-handed melee
         &&  (sWeaponWield != "10")   // One-handed ranged
         &&  (sWeaponWield != "11"))  // ditto
           IPSafeAddItemProperty(oItem, ItemPropertyNoDamage());
       }

In the OnItemUnacquire event:

object oNPC  = GetModuleItemLostBy();
     if (GetTag(oNPC) == "ROSALIND")
       IPRemoveMatchingItemProperties(oItem, ITEM_PROPERTY_NO_DAMAGE, DURATION_TYPE_PERMANENT);

 

This is not quite foolproof if the PC removes all other weapons from inventory, but the heartbeat kludge overcomes that.

 

My function which checks if an item is a weapon is as follows:

 

Spoiler

// Is item a weapon? (Based on FunkySwerve's extended CEP definition)
int bh_check_weapon(object oItem)
{
  if (!GetIsObjectValid(oItem)) return FALSE;
    switch (GetBaseItemType(oItem))
      {
        case BASE_ITEM_CLUB:
        case BASE_ITEM_DIREMACE:
        case BASE_ITEM_HEAVYFLAIL:
        case BASE_ITEM_LIGHTFLAIL:
        case BASE_ITEM_LIGHTHAMMER:
        case BASE_ITEM_LIGHTMACE:
        case BASE_ITEM_MORNINGSTAR:
        case BASE_ITEM_QUARTERSTAFF:
        case BASE_ITEM_WARHAMMER:
        case BASE_ITEM_DAGGER:
        case BASE_ITEM_RAPIER:
        case BASE_ITEM_SHORTSPEAR:
        case BASE_ITEM_SHORTSWORD:
        case BASE_ITEM_TRIDENT:
        case BASE_ITEM_LANCE:
        case BASE_ITEM_BASTARDSWORD:
        case BASE_ITEM_BATTLEAXE:
        case BASE_ITEM_DOUBLEAXE:
        case BASE_ITEM_DWARVENWARAXE:
        case BASE_ITEM_GREATAXE:
        case BASE_ITEM_GREATSWORD:
        case BASE_ITEM_HALBERD:
        case BASE_ITEM_HANDAXE:
        case BASE_ITEM_KAMA:
        case BASE_ITEM_KATANA:
        case BASE_ITEM_KUKRI:
        case BASE_ITEM_LONGSWORD:
        case BASE_ITEM_SCIMITAR:
        case BASE_ITEM_SCYTHE:
        case BASE_ITEM_SICKLE:
        case BASE_ITEM_TWOBLADEDSWORD:
        case BASE_ITEM_WHIP:
        case BASE_ITEM_DART:
        case BASE_ITEM_HEAVYCROSSBOW:
        case BASE_ITEM_LIGHTCROSSBOW:
        case BASE_ITEM_LONGBOW:
        case BASE_ITEM_SHORTBOW:
        case BASE_ITEM_SHURIKEN:
        case BASE_ITEM_THROWINGAXE:
        case BASE_ITEM_MAGICSTAFF:
        case BASE_ITEM_RAZOR:                  // Custom
        case BASE_ITEM_CEP_ASSASSINDAGGER:
        case BASE_ITEM_CEP_DOUBLEPICK:
        case BASE_ITEM_CEP_DOUBLESCIMITAR:
        case BASE_ITEM_CEP_FALCHION:
        case BASE_ITEM_CEP_GOAD:
        case BASE_ITEM_CEP_HEAVYMACE:
        case BASE_ITEM_CEP_HEAVYPICK:
        case BASE_ITEM_CEP_KATAR:
        case BASE_ITEM_CEP_LIGHTPICK:
        case BASE_ITEM_CEP_MAUL:
        case BASE_ITEM_CEP_MERCURIALGREATSWORD:
        case BASE_ITEM_CEP_MERCURIALLONGSWORD:
        case BASE_ITEM_CEP_NUNCHAKU:
        case BASE_ITEM_CEP_SAI:
        case BASE_ITEM_CEP_SAP:
        case BASE_ITEM_CEP_WINDFIREWHEEL:
        case BASE_ITEM_CEP_LIGHTMACE_2:
        case BASE_ITEM_CEP_KUKRI_2:
        case BASE_ITEM_CEP_FALCHION_2:
        case BASE_ITEM_CEP_LONGSWORD_2:
            return TRUE;
      }
    return FALSE;
}

 

No doubt that check could made more general by examining baseitems.2da, as long as it isn't called too often.

[Nebril2]

Thanks for your reply.

 

I will use the pseudoheartbeat, but isnt this method heavy for the pc? i mean my module uses lots of onheartbeat functions, and im trying to reduce them, making a pseudoheartbeat consumes much than a simple heartbeat? or is not something i shouldnt worry about?

 

Been here i will also ask, if i add some scripts to the cached list, will it help? and will it change the way this heartbeat scripts work?

 

 

Thankkks    

[Shadooow]

Pseudoheartbeat isnt much better than normal heartbeat, however you can use it in different intervals and you can turn it off and on as needed which can make it much more efficient than normal heartbeat.

[Proleric]

My understanding is that the script cache does more harm than good. This is the Lexicon info:

http://www.nwnlexico...=Script_Caching

I don't find it helps, even in SP.

A pseudoheartbeat on one NPC will have a negligible effect on performance if it's only checking whether an item's equipped in the right hand. It's a good way to achieve a near-instantaneous result.