Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The Dragontouched feat is supposed to allow you to select draconic feats as if you were a sorcerer of your character level. This doesn't seem to work.
Example: Draconic Heritage requires Sorcerer level 1st, but is not a valid selection for non-Sorcerer that has Dragontouched.
I have no clue where to start with all of this. Can anyone help?
Thanks a lot
The Dragontouched feat is supposed to allow you to select draconic feats as if you were a sorcerer of your character level. This doesn't seem to work.
Example: Draconic Heritage requires Sorcerer level 1st, but is not a valid selection for non-Sorcerer that has Dragontouched.
~ find out if the other "Power Attack" is active
if (hero.childfound[1P].field[1F].value <> 0) then
~ if it is active, and the adjustment higher then ours then stop
if (hero.childfound[1P].field[1A].value >= hero.child[2P].field[2A].value) then
The next official version of d20 has a bunch of fixes for Power Attack including the 1H issue, double weapons, and ranged weapons. Its just taking longer to get out then expected.1) From the in-play tab, it appears that the bonus damage is not adding correctly when wielding a 1-handed weapon in two hands. I haven't looked at the code, but the Adjustment does factor correctly now, so most of that code could probably be copied to solve the problem with the feat's code.
As for the adjustment from the community it maybe time to deprecate it now that an official version is out.![]()
@valid = pickexists[fQuickDraw]
For example the Favored Soul gets proficiency with a weapon at first level and weapon focus with that weapon at third. However, even though the weapon focus tag is being broadcast to the weapons, the HasFeat tag is not being generated so the Favored Soul doesn't qualify for prestige classes that require weapon focus, such as Pious Templar.
The other side of this is that several prestige classes have pick requirements either using the Pick-req to specify a specific feat (for example: Occult Slayer, Dread Pirate or Frenzied Berzerker), or the Pre-req with specifications like:In these cases, even if the character has the appropriate HasFeat tag, they still do not qualify unless they have the specific pick.Code:@valid = pickexists[fQuickDraw]
My latest is a grizzled crusader turned hellreaver who is hunting after the party. The intention was to use Stone Power to gain temporary HP every round so he could last longer against the over powered PC's. Stone power states, "can be used in place of Power Attack to qualify for a feat, prestige class, or other special ability" and even though the HasFeat tag is present, the "Power Attack required" still shows up under the validation.
Usually, this kind of thing is caused by an error in compilation. Did you receive any errors prior to opening your portfolio? If so, please copy and past it here.
Not sure if this is working as intended but my sorcerer/incantatrix seems to have manifested a bunch of additional level 0 spells, specifically:
- Amaneunsis
- Caltrops
- Electric Jolt
- Launch Bolt
- Launch Item
- Repair Minor Damage
- Silent Portal
- Sonic Snap
- Stick
They appear greyed out in the spellcasting tab, and print with the abilities printout.
Sendric, I was going to ask how you bootstrap something (like a feat) and "silence" it, but if you're having problems with it, it may be beyond my crude skills.
If these are 0-level cantrips from the community set that uses Helper.Obsolete tag then this is fixed in the next d20 release. I discovered this same issue this last weekend. It has to do with the fact that they where bootstrapped at one time and so exist inside the .por file. You can use the .por file as a test when you get the Beta version to make sure the issue is fixed.Sorry. I missed this. Unfortunately, I can't reproduce this. I suspect it has something to do with the new Helper.Obsolete tag, but I can't be sure. Could you post the .por file here so I can take a look at it?
This here!EDIT: Oh, I see what's happening. When I equip 1st and 2nd in a stack of axes, it assumes I'm wielding a single axe with both hands, not an axe for each hand.