• 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

Error in PL calculations for NPCs, with regard to Defense?

DLKTrazer

Member
Hello,

In the latest update, I noticed an issue with my previously created characters. Their PL seems to be tied directly to their highest of Toughness/Defense, ignoring any tradeoffs. Example: A character with Toughness +10, Def +0 is shown as PL 10. A character with Toughness +0, Def +10 is shown as PL 10 as well. A character with Toughness +10, Defense +10, still comes out as PL 10.

This only seems to be the case with defense tradeoffs; offense tradeoffs work as normal. I've already checked the options and made sure that I don't have any "No Trade Offs" option marked, so that's not causing it.

Anybody else having similar issues?
 
This is still on my list of stuff to look into for the next version of the Mutants & Masterminds data files, don't worry. The M&M files just got a big update, so my time is being taken up by other stuff right now :(
 
This made me curious. Not from the previously made character concept but from a "what happens if I make one fresh?" angle.

For this example I set the brand spanking new character's PL to 5.

The software will let me bring Toughness to +5, be it from Protection, CON bonus or a combination of the two, AND it will let me bring DEF to +5 which is fine. As I remember the rules both can meet but not exceed PL before any tradeoff has to take place. However, if I take either one to 6 it triggers the "you've busted the cap and automatic adjustment has been made to the linked trait" warning. However, I don't see a one-for-one decrease happen in the connected trait for the DEF/TOUGHNESS combo but I do get the up/down warning arrows with the trait I've cranked above 5.

Not so with the Attack Bonus/Save DC tradeoff, I only see the up/down arrow & warning when the attack bonus is taken beyond 5. No reduction takes place with REF/FORT/WILL Saves (I presume that's what it means by Save DC - don't have the book in front of me) nor any arrows/warning if I take them above +5.

Am I missing something obvious because it's 0513 and I haven't been to bed yet? lol
 
Not so with the Attack Bonus/Save DC tradeoff, I only see the up/down arrow & warning when the attack bonus is taken beyond 5. No reduction takes place with REF/FORT/WILL Saves (I presume that's what it means by Save DC - don't have the book in front of me) nor any arrows/warning if I take them above +5.
Save DC means the difficulty of saving against the power (generally, it's the rank of the power involved in the attack). For damaging effects, it's the damage bonus. For others, it's the value determining the save target. This can vary on a per-attack basis.
 
Gotcha. Of course it meant the attack bonus of a specific power not the characters base Attack Bonus. **smacks self in forehead** Was fuzzy-headed from lack of sleep. :)
 
I didn't have time to tackle this in the last update, sorry. I'll definitely look into this for the next data file update.
 
Not to be a pest, but is there an ETA on this fix? It's pretty critical to making characters...

I can get by with some number-juggling in my head, but the plain fact is that without this feature working properly, the characters aren't balanced properly.
 
Right now we're scrambling to finish another game system for release soon. Once I have some free time, I'll do my best to do an update which tackles this issue.
 
Right now we're scrambling to finish another game system for release soon. Once I have some free time, I'll do my best to do an update which tackles this issue.

Thanks, Colen. Honestly, I'd be fine with JUST this bug fix for the next update, if it speeds things up...
 
Back
Top