Issues with 3.5 Conversion

[Mathias]

Hero Lab can't currently handle the sort of weapon power/bonus swapping that the mind blades and the Paladin's divine bond: weapon requires.

So, we'll set up a work-around. The 3.5 versions of the Mind Blades are set up not to show up in the list of weapons available for purchase. That's actually not the way it should be handled. Instead, on the weapons tab in the editor, uncheck "Don't Allow Selection". Now, a user can purchase Mind-Blades. More specifically, they can add them as custom magic weapons, adding the bonuses and powers they want for that weapon today.

Okay, now to make sure your average fighter isn't walking around with a Mind Blade.

Go to any feat or custom class ability that requires the presence of another class ability. For example, in the custom class ability tab, the Rogue's Major Magic ability - that requires the Minor Magic ability.

Take a look at that ability's Expr-Req, and you'll see that the Minor Magic requirement is:

 
hero.tagis[Ability.cRogMinMag] <> 0

Updating that to a more modern way of handling it:

 
#hasability[cRogMinMag] <> 0

So, go to your Mind Blade weapon, and add a new Expr-Req

Message: "Mind Blade ability required."
Pre-requisite Expression: #hasability[XXXXX] <> 0

Replace the XXXXX with the Id of the Mind Blade ability you created.

If you're doing things this way, you may also want to remove the bootstrapping of the Mind Blades - just let the user add the Mind Blade version(s) they want, with the bonuses and powers they want.

[JMD031]

Originally Posted by Mathias

Please check a calender before thinking you're being ignored. You posted these questions on Sunday afternoon, and then wondered why you hadn't gotten a response Tuesday at 7AM, the day after the labor day holiday.

Sorry, I was just making a joke.