A request for a new feature

[chiefweasel]

could you send along the stats of the armor you are using, before trying to add the spikes and i"ll give it a shot as well.

The only problems that I have run into with spikes is when the magic bonus exceeds the limit of +5.

[Lawful_g]

+1 Breastplate with +1 Armor spikes.

[chiefweasel]

Ah, I see the error now. That wasn't there before the latest patch. I have attached spikes to armor in the past without a problem, so something new has cropped up. I guess the tech guys will need to check this one out. I tried to copy the error but couldnt figure a way to do it. Sorry about that.

[bodrin]

Originally Posted by Lawful_g

Oh, something else that would make life easier? A single entry for "Smite" that is then modified based on what your abilities are. There are lots of smites granted from different sources (like paladin, blackguard, celestial template, domain powers etc), and I am currently adding a feat (Extra Smiting) that adds 2 to any of them that you have, which is a pain to repeat code for all of them multiple times. Might simplify things in the future.

I have already coded Extra smiting from the completer warrior book Lawful g heres the working code in full.

I just copied and pasted the same script line then altered the smite thing.
I do agree that it is a pain though!

Eval script Post-levels (users) timing 10000

hero.childfound[xFieSmite].field[hTotal].value += 2
    hero.childfound[xCelSmite].field[hTotal].value += 2 
hero.childfound[cPalSmite1].field[hTotal].value += 2
    hero.childfound[cBlkSmite1].field[hTotal].value += 2

Pre-reqs

if (child[Attack].field[tAtkBase].value >= 4) then
   @valid = 1
   endif

Hope this helps!!

[Lawful_g]

Thanks Bodrin. Shouldn't there be another pre-requisite for having an ability to smite?

For what it is worth, I also did this feat, and I found a total of 9 different smite abilities. 7 of them were already in HL:

cPalSmite1
xFieSmite
cPfChvSmit
cBlkSmite1
cBlkPalSm1
cdDestSmit
xCelSmite

And two were part of classes I entered myself:
cFRaSmite
cKSwSmite1

It is the addition of more smite abilities by future classes that worries me. Every time I add a new class that does this will I have to revise the feat?

[Mathias]

At this point, what you probably want to do is replace the various versions of smite, adding a new User tag like User.Smite.

Then, your feat can use a foreach test to find everything that is a class special and is a smite ability:

foreach pick in hero where "component.BaseSpecial & User.Smite"

then do everything that modifies the ability from within the foreach.

Also, on a quick script on each smite ability, forward the Smite tag to the hero:

 
perform hero.forward[User.Smite]

That way your feat can test for the presence of that tag on the hero, rather than searching for each version of smite:

(in an expression requirement):

 
hero.tagis[User.Smite] <> 0

I'm afraid it's not going to happen soon, but I'll add a tag (probably Hero.Smite) to the various smite abilities and add the same behaviors. When that happens, just replace all the User.Smite tags with Hero.Smite. and delete your replacements.

[Lawful_g]

Thanks mghel

[Lawful_g]

Mathias, did you ever think about non-magical mods to armor? I've come back to that.