Intelligent Blademaster Bugfix

[MagicSN]

Hello!

I found out "Intelligent Blademaster"'s effect on Basic Melee is not correctly implemented. Due to the way Hero Lab works, it cannot be implemented by a user file (user files cannot replace Basic Melee as the system then complain "it is already in use"). I solved the issue by directly editing ddi_powers.dat (which is just an XML file). But I think this Bugfix should go into the next version of the data files from WolfLair as such a direct editing of a .dat file is an "ugly" solution.

Here is how to fix it:

Look in ddi_powers.dat for pwBasicMel and replace it with this (basically you only need to change the Script part):

  <thing id="pwBasicMel" name="Basic Melee" description="A basic melee attack." compset="Power">
    <fieldval field="pwTarget" value="One creature"/>
    <tag group="Helper" tag="Bootstrap"/>
    <tag group="ActionType" tag="Standard"/>
    <tag group="ReqLevel" tag="1"/>
    <tag group="AttackType" tag="MeleeWep"/>
    <tag group="Attack" tag="attrStr"/>
    <tag group="DamageAttr" tag="attrStr"/>
    <tag group="AttackVs" tag="defAC"/>
    <tag group="PowerAcc" tag="Weapon"/>
    <tag group="PowerType" tag="AtWill"/>
    <tag group="Damage" tag="Weapon1"/>
    <containerreq phase="Initialize" priority="0">
      !source.HideBasic
      </containerreq>
    <eval phase="Traits" priority="10000"><![CDATA[
if (#level[] >= 21) then
  perform delete[Damage.Weapon1]
  perform assign[Damage.Weapon2]
  endif

  if (hero.childexists[ftIntelBla] <> 0) then
   if (#attrbonus[attrInt]>#attrbonus[attrStr]) then
    var attidstr as string
    attidstr = "attrInt"
    perform deletestr["DamageAttr.attrStr"]
    perform deletestr["Attack.attrStr"]
    perform assignstr["DamageAttr." & attidstr]
    perform assignstr["Attack." & attidstr]
   endif
  endif

]]></eval>

[Cryptoknight]

Two things.

1. The error message that pops up is OK.  You can in fact allow it and have it delete the item and re-add it from the character (or that's what I've been told before).  It's just an error that pops up because you're overriding a power that's on the currently loaded profile.

2.  You can edit the .dat file in the editor as well and change the power, but the next run of the downloader will override it.

[Cryptoknight]

In fact I was working on that problem before (I had forgotten) and I already had a basic melee attack power that overrode the basic melee attack.

I added your code to it (which works great) and when I saved and tested I got the same error about deleting and re-adding.

I then went to Develop and chose quick compile.  When it reloaded, my swordmage now works correctly.

The hard one will be the Melee Training and the 1/2 damage from the stat trick.

[dracusmage]

I'm sorry for resurrecting this, but I thought I should put my 2 copper in on this. It seems that replacing "Basic Melee Attack" is heavy handed and prone to cause future problems when someone else decides that the best way to fix another issue is to do it too. Also, if we put the fix into the attack, it means we have to do some checking to see if the feat exists.

Instead what I did was fixed the feat. This has the benefit of not changing anything unless the feat is actually picked, and means that if someone else needs to make a change to Basic Melee, they don't need to add another fix on top, or release a different incompatible fix.

I also fixed the script so that it does some paranoid checking on the off chance that we are using something else that also changes the basic attack stat.

Code Select Expand


<eval phase="Traits" priority="10000"><![CDATA[
perform hero.child[pwBasicMel].setfocus
var text as string
var current as number
text = focus.tagids[DamageAttr.?]
current = hero.findchild[Attribute,text].field[attrBnBase].value
if (#attrbasebonus[attrInt] > current) then
perform focus.delete[DamageAttr.?]
perform focus.delete[Attack.?]
perform focus.assign[DamageAttr.attrInt]
perform focus.assign[Attack.attrInt]
endif
]]>
<after name="Calc attrBnBase"/>
</eval>

What this will do is grab whatever the Attribute being used for Basic Melee currently is, check it against Int to see which one is better, then if Int is better, replace whatever is currently the attribute (probably Str, but maybe something else) with Int. I don't know if other feats are this courteous, but this one will not cause a problem.

Did you ever get the Melee Training you mentioned handled?

[Cryptoknight]

Nice, added your fix to the compiled data files...