You be the dev: Word of Faith

[Lokey]

Continued nice weather put this on the back burner.

So some minor disabling effect (i.e. current miss-chance), ok damage, something nasty for diametrically opposed alignments (short duration stun or blind no save or slightly longer with save) and not spammable seem like something worth using but not the only thing you'll use?

[Midterm]

What about a no-save curse? More ability scores lost, the more diametrically opposed you are. Nothing too life-threatening, but could be dangerous in the long run.

Would put the remove curse spell to good use.

[cRaZy8or5e]

What about a no-save curse? More ability scores lost, the more diametrically opposed you are. Nothing too life-threatening, but could be dangerous in the long run.

Would put the remove curse spell to good use.

People would only hate imploders more

[Blystos Re]

What about a no-save curse? More ability scores lost, the more diametrically opposed you are. Nothing too life-threatening, but could be dangerous in the long run.

Would put the remove curse spell to good use.

The changes to Bestow Curse already put Remove Curse to good use.

[Shamedmonkey]

What about a no-save curse? More ability scores lost, the more diametrically opposed you are. Nothing too life-threatening, but could be dangerous in the long run.

Would put the remove curse spell to good use.

The changes to Bestow Curse already put Remove Curse to good use.

Yes, lots of people use Bestow Curse in PvP...oh wait...

[Lokey]

Curse is weird, won't affect lots of things for various reasons.

Oh, you get to be the testers too.

Enemies only and SR = yes for:
- 20% misschance, lasting caster level/4 rounds
- d4/level sonic damage
- if caster lg, cg, le, ce, opposed alignment gets will save or stun two rounds (visual on that...should probably apply visual regardless of save).

[LunarSquirrel]

So I used WoF quite a bit yesterday in testing as we had that huge 3-way battle in MA. Here are some observations from a 35/5 cleric split:

*The miss chance was noticeable; mostly so when a toon stunned me immediately after I WoF'ed and combined with my current buffs made me a great deal unhittable (I do not have high AC). Most toons though did not seem to be bothered by it.

*I did not see ANYONE that was diametrically opposed become stunned from a failed will save.

*The sonic damage was about 60-100 depending on whom I hit. Again, this did not seem to affect most of the characters I fought.

Things I think could use a lil tweaking still:

1.) Is there some sort of effect in play to let you know if someone was affected by the hit? When you're hitting a group it's hard to rely on the sonic damage numbers since there's tons of extra numbers going on - maybe a visual effect like the drain effect you "see" when you detect evil with a CoT. That was my biggest confusion - not knowing how many people were actually hit with the spell.

2.) The miss chance could be tweaked up another 5% and I don't think it would be uncalled for. As I said it was noticeable, but except for one incident I don't think it made any real difference.

3. ) Even though I think the sonic damage output is fair for the fail, I would like to see it allow damage even after the target is under the hitchance reduction. a 25% or maybe even 50% reduction in the sonic damage while affected would keep it unspammable but would be useful for trying to get that kill shot, or as I found last night while pvping, clearing out a hallway of bothersome path-blocking mobs

4.) Do you happen to know how the will save is calculated? I'd like to ask if it could be upped a little to ensure that we at least stun *SOME* opponents but in all honesty I didn't have a chance to check combat logs to see what it was or how much people were beating the save by.

5.) Any chance we could return the summon dispel function to this spell? SR Check for summons or some sort of check - failure = bye bye? That was one of my favorite things about WoF before; even above the blinding.

I would like to say though, I think these changes are headed in the right direction. Personally, I think it needs a couple more small tweaks though

[Rufio]

define "opposed alignment"

I'm guessing for a lawful good caster that is anything that is chaotic OR anything that is evil, but I don't really know.

[Lokey]

See change notes. LG smites CE, CG smites LE, etc...

[frogofpeace]

Not to pick nits, but NE vs NG, LN vs CN as well?

[Blystos Re]

Those aren't real alignments.

[cRaZy8or5e]

In testing between me and zerg, we never noticed any misses at all due to miss percentile, concealment, or anything. I don't know if blind fight completely negates the miss percentile, but so far it's hit and miss about when it decides to hit and when it doesn't. Everyone I know has said that they've seen the miss percentile work, but I have yet to see it . If it does in fact work and I'm blind, stupid, or both; then I disagree and don't think it should be bumped up. Anymore than 20% and you start making clerics even more difficult than they already are to kill.

The stun DC works like any other regular spell, so if you have a 20 wisdom mod +6 epic sp focus +10 base +7 spell lvl = 43 DC WoF. Anything bard, pally, monk, cleric, bg, caster, druid, should probably make the save.

Otherwise, in my opinion, everything else worked as advertised. Good stuff.

[mining]

In our testing, blind fight totally nullified miss chance, i.e. Roz was screwed, Sancreed was not.

[LunarSquirrel]

That would fall in line with my testing. I believe the character I was fighting did not have blind fight.

[Rufio]

I feel like this change just creates more of a reason to stick to a neutral alignment for everyone besides a DC focused cleric caster.