• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

a flaw to disable all dodge bonus

psych777

Well-known member
i tried searching for something similar that disabled dodge bonus to look at and compare but couldn't find anything.
been looking at the dodge feat in the debug windows and just can't seem to wrap my mind around it.
from what i can tell it would need to run after Post-levels 10000 as that seems to be when the dodge feat applies the ac bonus. that right?
i can't figure out how to look at the debug info for AC
flaw i'm trying to make needs to disable any dodge bonus (whether feat or item/equipment, spell, etc)
 
I would run the script very late (in Final or Render).

You just need to set the Dodge bonus to AC to 0. Go to Develop/Floating Info Windows/Show Selection Fields and check the thing ArmorClass. You should see the Dodge bonus field there.
 
Here's how I'd approach finding the right phase & priority to use for this.

In the Develop menu...Floating Info Windows, choose "Show Selection Tasks".

In the list of picks that gives you, find "Armor Class (ArmorClass)". Check that, and click OK, and it will give you a list of all the scripts that runs.

There are three scripts that might be it: Post-Attributes/10000, Final/10000, and Final/9999999.

I think it's the middle one, so I'd start by trying your script at Final/9990, then try Post-Attributes/9990, then try Final/9999989. Test it at those phase & priority combinations until you find one that works.
 
thanks for the direction.
whats the difference in the phases that have "(Users)"?
example, there is a "Final Phase" and a "Final Phase (Users)"

this is the script i came up with that seems to work:

if (hero.child[ArmorClass].field[tACDodge].value <> 0) then
hero.child[ArmorClass].field[tACDodge].value = 0
endif

is there a simpler way to word it?

ps. i was quite frustrated for awhile there cuz none of my script attempts were working until i finally realized i had forgotten to add the flaw to the char! LOL
 
The "(Users)" phases were an idea from early on in the development of the d20 files that's been mostly abandoned. Generally, use the regular versions of the phases.
 
ahh your right. that was the first thing i tried (no if statement) and when it didn't work i started working on the if/then. that was before i caught my mistake of not adding the flaw to the char. just changed it and it is working with just

hero.child[ArmorClass].field[tACDodge].value = 0

thanks!
 
thanks mathias, i was actually more inclined to use the (Users) one thinking it was meant user interaction haha
 
update...
looks like if i have it set on the Final Phase it does make the Dodge AC entry 0, but it still counts the dodge value to the overall AC.
if i have Final Phase (Users) set then it doesn't add the dodge value to the overall AC

ok, now i'm just plain confused...
i kept looking at the developer window and was seeing the AC adjust like i expected (or not when it wasn't working). but i've just noticed that the char still is showing the dodge bonus (see screenshot).
for testing that dodge wouldn't get added i added the dodge feat, and an adjustment for Armor Class (Dodge) and made it a +2.
 

Attachments

  • AC.jpg
    AC.jpg
    304.7 KB · Views: 3
Last edited:
It all has to to do with timing, what you're needing to do exactly is edit the value AFTER dodge bonus is calculated, but BEFORE it's added to AC.

Which timing did you end up using?
 
i was using Final Phase (Users) 10001, then changed it to Final Phase (Users) 999999. same result. when i had it set to Final Phase with same numbers it didn't correctly apply to the develop window total (instead of 11 it would be 14)
 
okay, reread his post and didn't remember the last paragraph.
looks like Post-Attributes/9990 might have done the trick...gonna test a bit more now
 
i don't see a "Final", only "Final Phase" and "Final Phase (Users)" and i've tried them both...
Final is just short cut way of saying "Final Phase". Sometime I may just say run at Final/10000 which is the phase and the timing together. :)

So Final Phase User runs just before Final phase does. Most of the time I don't use that late of timing unless setting "text" onto something.
 
Back
Top