At another loss

[Minous]

Originally Posted by ErinRigh

does this seem right?

foreach pick in hero where "thingid.shBuckler"
     if eachpick.field[gUserEquip].value <> 1
        perform assign[Helper.SpcDisable]
        done
     endif
 nexteach

Close but you might run into issues if the PC has multiple shields. Might want to do the reverse process though. add the disabled tag and then delete it if a buckler is equipped.

[ErinRigh]

Ok, how Sensei?

[ShadowChemosh]

Sorry to interrupt but several things.

If you are using "Thingid.?" as a tag you are most likely heading in the wrong direction. 99% of the time you should never use Thing ID because Thing ID's change. In this case what if I made a new buckler up tomorrow or a magic buckler up with a different Unique ID. Then your script logic won't work.

Foreach loops should be avoided when you can. Always look for hero tags to use instead.

If I add a Buckler and equip it I can look at the tags on the hero for "Buckler". Develop->Floating Info Windows->Show Hero Tags. This then shows I have a tag called "ShldClass.Buckler" which tells me I have a buckler equipped.

Meaning to see if a buckler is equipped you just need to do:

~ If we don't have a buckler disable ourself
If (hero.tagis[ShldClass.Buckler] = 0) Then
  perform assign[Helper.SpcDisable]
Endif

[Minous]

Thanks Shadow I expected something like that, but I dont have HL handy so I couldnt look that up.

[ShadowChemosh]

Originally Posted by Minous

Thanks Shadow I expected something like that, but I dont have HL handy so I couldnt look that up.

Normally true for me during the week but I am actually off this week!

[ErinRigh]

Thanks SC that makes perfect sense

[EightBitz]

Originally Posted by Minous

Putting it on the buckler is a bad idea.

Just curious as to why.

[ShadowChemosh]

Originally Posted by EightBitz

Just curious as to why.

Its a "Great" plan if you have full access to the skeleton files or you are making your own game system.

When working within LW game systems you want to avoid doing a "Replace Thing ID" as much as possible. LW makes too many changes in future releases that will cause you issues.

Its best to work from the OUTSIDE looking for tags and field values when working within LW game systems.

[Minous]

Originally Posted by EightBitz

Just curious as to why.

What about custom bucklers? special materials/named ect? If you look for the item type instead of a named thing its less prone to issues.

[EightBitz]

OK, I misunderstood. I was parsing this as being particular to a specific buckler.

The example I provided was for a custom magic item, and certain things are dependent on whether or not this specific magic item is equipped.

Going back and rereading, I now see where this question is about bucklers in general, not just one specific buckler.