• 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

Workaround for Double Weapons

Currently, double weapons do not allow for 1.5 damage if used two handed but not as a double weapon. This is the fix I implemented on my end, put here in case the community wants to use it.

Code:
<<Post-Attributes (Users) 1000>>
~ Fix for double weapons (HL workaround).
~ If we're not equipped, do nothing.
var result as number
result = field[gIsEquip].value
if (container.ishero = 0) then
  result += container.parent.field[gIsEquip].value
endif
doneif (result = 0)

~ Determine if we are used in both hands but not as a double weapon.
if (container.ishero <> 0) then
  doneif (field[wIsDouble].value <> 0)
  field[wDamBonus].value += round(hero.child[aSTR].field[aModBonus].value / 2, 0, -1)
else
  doneif (container.parent.field[wIsDouble].value <> 0)
  container.parent.field[wDamBonus].value += round(hero.child[aSTR].field[aModBonus].value / 2, 0, -1)
endif
 
I inserted it into every double weapon, which means I copied and replaced those weapons. Have no idea if it would work with the Pathfinder set, maybe someone else proficient with Pathfinder would know, as I don't have that set.
 
Pathfinder already correctly handles Double weapons so no need to do anthing. I am a little surprised that d20 is not handling them correctly. Will double check later...
 
It was never doing it for me, so I just decided to code it myself. It's been too long since any bug fixes have occured in d20 and it doesn't look like the d20 will see much attention anytime soon, so I'm just going to have to put in temporary workarounds for those things that I can for the time being. Just kept getting tired of things being calculated incorrectly in the midst of a gaming session.
 
It was never doing it for me, so I just decided to code it myself.
Yep appears you are correct. Good job on the above code. Wonder if someway to do a more global fix instead of having to do a Replace ID....

Also playing around I found that when the double weapon prints it is actually correct. You can see this when you do a File->Print Preview... Leading to the idea that double weapons displayed in HL should take into account the 1.5 Str.

Here is the changed code to prevent double weapons when printed from getting a x2 str bonus:
Code:
~<<Post-Attributes (Users) 1000>>
~ If we're in output mode, don't do anything
doneif (state.isoutput <> 0)

~ Fix for double weapons (HL workaround).
~ If we're not equipped, do nothing.
var result as number
result = field[gIsEquip].value
if (container.ishero = 0) then
  result += container.parent.field[gIsEquip].value
endif
doneif (result = 0)

~ Determine if we are used in both hands but not as a double weapon.
if (container.ishero <> 0) then
  doneif (field[wIsDouble].value <> 0)
  field[wDamBonus].value += round(hero.child[aSTR].field[aModBonus].value / 2, 0, -1)
else
  doneif (container.parent.field[wIsDouble].value <> 0)
  container.parent.field[wDamBonus].value += round(hero.child[aSTR].field[aModBonus].value / 2, 0, -1)
endif
 
Last edited:
Back
Top