Bug Reports - Community Created 3.5 D&D data set

[paulh]

Update: This issue was caused by Improved Cunning Defense and has been fixed. I've also improved a few other class specials.

Update: Apparently, I hard-coded the ? with the intention of changing it with a script. After taking another look at it, I decided it's probably not necessary to have the Inspiration points in the Specials tab, so I've removed it.

That was quick! Thanks for the fixes.

 

[paulh]

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.

 

[bryandet]

Huge problem - please help

So, my computer crashed a couple months ago, had to replace hard drives, couldn't mirror much of my old data. Anyway, reloaded Herolab, reset the secondary update sites, got everything loaded, then tried to open a portfolio on a character that I had saved in my email that I'll be playing with, and got this:

The following sources are not present for 'Kirildhoran', which may cause problems during load: 'CompMage', 'CompPsi', 'CompScound', 'CompWarrio', 'DMGPoison', and 27 others
Critical information not found in data files: Source 'Advanced Bestiary'
Critical information not found in data files: Source 'Book of Exalted Deeds'
Critical information not found in data files: Source 'Complete Adventurer'
Critical information not found in data files: Source 'Complete Arcane'
Critical information not found in data files: Source 'Complete Champion'
Critical information not found in data files: Source 'Complete Divine'
Critical information not found in data files: Source 'Complete Mage'
Critical information not found in data files: Source 'Complete Psionics'
Critical information not found in data files: Source 'Complete Scoundrel'
Critical information not found in data files: Source 'Complete Warrior'
Critical information not found in data files: Source 'Dungeon Masters Guide Posions'
Critical information not found in data files: Source 'Dungeonscape'
Critical information not found in data files: Source 'Draconomicon'
Critical information not found in data files: Source 'Dragon Compendium'
Critical information not found in data files: Source 'FCodex2'
Critical information not found in data files: Source 'Frostburn'
Critical information not found in data files: Source 'Heroes of Battle'
Critical information not found in data files: Source 'Libris Mortis'
Critical information not found in data files: Source 'Lords of Madness'
Critical information not found in data files: Source 'Magic Item Compendium'
Critical information not found in data files: Source 'Miniatures Handbook'
Critical information not found in data files: Source 'Monster Manual'
Critical information not found in data files: Source 'Monster Manual 2'
Critical information not found in data files: Source 'Monster Manual 5'
Critical information not found in data files: Source 'Player's Handbook 2'
Critical information not found in data files: Source 'Races of the Dragon'
Critical information not found in data files: Source 'Sandstorm'
Critical information not found in data files: Source 'Spell Compendium'
Critical information not found in data files: Source 'Stormwrack'
Critical information not found in data files: Source 'Races of Stone'
Critical information not found in data files: Source 'Races of the Wild'
Pick 'pACharging' has been orphaned due to missing thing in batch '87'
Pick 'pPsiFocus' has been orphaned due to missing thing in batch '88'
Pick 'pcnAwakeUn' has been orphaned due to missing thing in batch '89'
Pick 'pcnHaste' has been orphaned due to missing thing in batch '105'
Pick 'sWizAciSpl' has been orphaned due to missing thing in batch '118'
Pick 'sWizAmaneu' has been orphaned due to missing thing in batch '119'
Pick 'sWizArcMar' has been orphaned due to missing thing in batch '120'
Pick 'sWizCaltro' has been orphaned due to missing thing in batch '121'
Pick 'sWizDanLig' has been orphaned due to missing thing in batch '123'
Pick 'sWizDaze' has been orphaned due to missing thing in batch '124'
Pick 'sWizDetMag' has been orphaned due to missing thing in batch '125'
Pick 'sWizDetPoi' has been orphaned due to missing thing in batch '126'
Pick 'sWizDisrUn' has been orphaned due to missing thing in batch '127'
Pick 'sWizElJolt' has been orphaned due to missing thing in batch '128'
Pick 'sWizFlare' has been orphaned due to missing thing in batch '129'
Pick 'sWizGhoSou' has been orphaned due to missing thing in batch '130'
Pick 'sWizLaBolt' has been orphaned due to missing thing in batch '132'
Pick 'sWizLaItem' has been orphaned due to missing thing in batch '133'

I have no clue where to start with all of this. Can anyone help?

Thanks a lot

 

[Sendric]

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.

Thanks for the report. I'll take a look when I get the chance.

 

[Sendric]

I have no clue where to start with all of this. Can anyone help?

Thanks a lot

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.

 

[Sendric]

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.

Looks like an over-sight specific to Draconic Heritage. This issue has been resolved.

 

[Nightfox]

Possible bug with the Power Attack issue. It seems like power attack is being handled in two places now. There's the adjustment which is user added and on the In-Play tab when the feat is added. Here are the two issues I'm now seeing.

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.

2) This is more of a notation, but the penalty and bonus from both the adjustment and in-play are being stacked. If we're going to keep both in the community files, we may want to add a warning, or better yet, add an eval to check for the existence of the other and see which one is adding the higher penalty/bonus. Perhaps something like:

~ 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

Where 1P & 2P are the picks for the feat and adjustment, 1F & 2F are the activation check boxes, and 1A & 2A are the adjustment values. And the ">=" should be just ">" on one of them so that if both values are the same, one would be used, and the other would be disabled.

 

[ShadowChemosh]

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.

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.

I apologize for that.

As for the adjustment from the community it maybe time to deprecate it now that an official version is out.

 

[Nightfox]

No stress, just did not see where anyone else had mentioned it, so I thought I'd point it out lest it end up forgotten.

 

[Sendric]

As for the adjustment from the community it maybe time to deprecate it now that an official version is out.

Oh, yea I guess I should probably do that.

 

[Nightfox]

I'm not sure if this should be mentioned here, or if it would be a bug at all, but I've been noticing a lot of problems with my NPC's qualifying for prestige classes because of pick requirements and the lack of HasFeat tags.

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:

@valid = pickexists[fQuickDraw]

In these cases, even if the character has the appropriate HasFeat tag, they still do not qualify unless they have the specific pick.

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.

 

[Sendric]

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.

This issue is caused by the Favored Soul ability. In this case, the ability is acting like Weapon Focus, but is not informing HL that the character has the Weapon Focus feat. I'll take a look at how to improve this.

Update: Resolved this issue. Also updated the Weapon Specialization ability to match.

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:

@valid = pickexists[fQuickDraw]

In these cases, even if the character has the appropriate HasFeat tag, they still do not qualify unless they have the specific pick.

I'll take a look at these three classes. In general, the process works, but there may be certain issues. If you have specific issues, feel free to list them out if that's not unreasonable.

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.

Looking for the pick and looking for the HasFeat tag are two different things. I'll take a look a the Stone Power feat. I can probably bootstrap Power Attack, then silence it so that the pick exists but isn't shown on the character. This would likely be easier than changing all the pick-req's that are looking for Power Attack.

Update: OK, I lied. Apparently there is a downside to switching from the #hasfeat look-up to the pick-req. Feats that count as another feat (such as Stone Power for Power Attack) won't qualify with the pick-req method. Lesson learned. This issue is fixed for Power Attack.

Thanks for the reports.

 

[saturn082]

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.

 

[bryandet]

All fixed

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.

Hey Sendric- I uninstalled Hero Lab, did a clean reinstall, reloaded only the most recent community files, now everything is working. Thanks for your willingness to lend a hand!

 

[Nightfox]

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.

 

[Sendric]

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.

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?

 

[Sendric]

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.

I never even got that far, actually. Once I took a look at it, I realized my mistake in moving feat pre-reqs to pick-reqs. In any case, I was going to start with the Helper.FtDisable tag, though I think that leaves the feat grayed out so it may not have been ideal anyway.

 

[ShadowChemosh]

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?

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.

 

[paulh]

There's a calculation issue with two weapon fighting when using two of the same weapon that are stacked.

For example, a single throwing axe in primary hand, I have +7 melee/+7 ranged. If I equip a second axe in that same stack, I still have +7 melee/+7 ranged.

If I equipment 1st axe from one stack, and 2nd from a different stack, it properly calculates +5 melee/+5 ranged.

I may not have explained that well. I could do screen shots if necessary.

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.

So, perhaps not a bug.

 

[ShadowChemosh]

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.

This here!

This is also the same behavior as Pathfinder so I think its more of a way of HL works not just d20.