Fieldset

Will this snippet here create and attribute that the API can access? Is the attr_ it makes going to be repeating_feats_x_feat? <fieldset class="repeating_feats"> <input type="text" name="attr_feat"/> </fieldset>

Yes.

Heh, I just solved this my self fiddling with the API. One step closer to feat implementation into my scripts. Now is the hard part... how to find what feats a given token has, and more importantly, what does the feat do. I am thinking a function that just gets the repeating_feats name put them in an array, then write a ridiculously long if tree to match up the names then apply the pros and cons to new attr_ that the API can use as needed. Or am I over complicating this, yet again!

You're be doing a lot of unnecessary stuff that can be done by just modifying macros that the feat affects.

The ultimate goal is automation. I know my players, and the games always come to stand stills because someone has to look up a feat or ability. I would like to use macros more, but since I can't call them in the API, they are rather useless to my purposes other then calling my scripts. Don't get me wrong, I have absolutely no idea what I am doing. Before tonight, I had nearly 0 experience with HTML, but I ask questions, I absorb knowledge, then apply it. Sometimes I don't know the proper application of what I know so I have to experiment. What would you suggest I do for feats?

All I'm doing for feats is applying them to the appropriate macro or field. For power attack, I made a separate Power Attack weapon that was just a copy of another weapon and modified the attack and damage modifiers. Then I just copied a macro and did a find/replace to change the weapon indices. For anything else, I just repurpose existing sections of the sheet.

Interesting. So just use the feats as reference, and have an %ability add x modifier to what ever roll is being used? I would still have to use the API since I don't use dice rolls. This is actually pretty interesting indeed because I already have misc and temp modifiers on my sheet as 0 value. My combat resolution script already accounts for these fields, so I already have an entry point. This is why I made my own sheet instead of using yours, I just couldn't do what I wanted to with all the autocalcs. Glad this solved the issue with feats, but I guess that's what I absent mindlessly was reaching for. I never know what I am doing half time, I'm on autopilot a lot these days.