Junior Member
Join Date: Apr 2013
Posts: 20
|
I'm new to M&M 3e (Making characters; haven't actually played it yet), so I figure I'm doing something wrong or misunderstand the rules, but in a PL10 game, it should be valid for a character to have Dodge/Parry 8, Toughness 12, right?
'Cause every PL10 character in my Hero Lab either gets capped by the trade-off or actually generates a validation error when any defense goes over 10. Yes, even the characters that came with the download (Battlesuit.por, Construct.por, etc.). I pull up a New Portfolio, set Agility to 8 then put 4 points into Dodge, and Hero Lab shows 10/12 for the stat with a Trade-off warning. All with 0 Toughness and no other defenses. Is this a bug or what? |
#1 |
Senior Member
Join Date: Dec 2009
Location: Independence, Mo
Posts: 797
|
Not sure why it's doing that? I have characters I have made and just made to test your problem out and it doesn't throw an error for me on any of my characters that I have made on old or new characters. You might send in a request for help or put a portfolio of the character up on here that you made, and I will download it and take a look at it in my hero lab.
Question: are you just seeing the purple arrows beside the toughness or are you seeing the " ! " in a red diamond at the top right. If your just seeing the arrows beside the toughness when you have a Dodge/Parry of 8 and a Toughness of 12, then your fine - Hero lab is showing you that you traded off and you can't have your Dodge/Parry any higher then 8 - if your toughness is 12, if you make either Dodge or Parry a 9 then Hero lab will throw an error. Last edited by jbearwillis; July 8th, 2014 at 05:04 PM. |
#2 |
Junior Member
Join Date: Feb 2011
Posts: 21
|
Check the settings on the Hero, maybe the "Do not allow PL trade offs" option got checked?
I may be confused on your exact error, if that doesn't fix it maybe you could save and upload a portfolio to check ourselves? |
#3 |
Junior Member
Join Date: Apr 2013
Posts: 20
|
Hmm. Experimenting with the program today I am unable to generate validation errors that aren't correct, so that was probably just me. What I do still get, though, is the purple up-down Trade-Off error on any defense over 10 -- no matter the value of other defenses. This happens with Character Settings at "Game Default" and even on the sample characters.
I can deal with this Trade-Off arrow -- character sheets and stat blocks don't even show it -- but it's not supposed to be there, right? |
#4 |
Senior Member
Join Date: Dec 2009
Location: Independence, Mo
Posts: 797
|
Yes, they are suppose to be there. It's to show you that the program automatically corrected the trade-off, so you now know and are aware they can only go so high before you throw an error of going over. It's a helping tool only. It's not an error message, just a help tool.
Hope that helps explain it for you. |
#5 |
Junior Member
Join Date: Apr 2013
Posts: 20
|
Quote:
Are you saying that any trait over 10 is supposed to be flagged with the message "This trait is too high for the current power level?" 'Cause it's not. A character with 14 Toughness and 0 Dodge/Parry should not get that message -- that's simply not too high for the current power level. Read similarly for effects. Damage 12 (which gets the trade-off arrow) is fine for PL10 so long as your attack bonus is +8 or less. I'm not saying the trade-off arrow is an error message; I'm saying it's in error. |
|
#6 |
Senior Member
Join Date: Dec 2009
Location: Independence, Mo
Posts: 797
|
By the rules it is, But you are allowed to trade-off between the linked Characteristics, if your gamemaster allows you to.
The image, I have posted is showing that 12 is to high for the power level so Hero Lab automatically tries to correct for the difference. The arrows and message isn't an error but a message that my toughness trait is to high for the power level so it adjusted it for me. So if I tried to raise my Dodge or Parry above 8, it will through a real error in the upper right hand side of the screen. Trade-offs are not always allowed. Some GM's don't allow a player to do that, hero lab does that to try and adjust the traits for you when it is allowed and shows you that it did, is all it's doing, but by the rules it is to high for the power level it self, but the rules allow you to trade-off if your GM allows you to. It's not a given. Does that help explain it to you. As long as you don't have the error showing up in the right hand corner, your fine. If it does show up just click the diamond shape with the ( ! ) in it to see what's wrong with the character, if it's not there your fine. Last edited by jbearwillis; July 9th, 2014 at 02:06 PM. |
#7 |
Senior Member
Volunteer Data File Contributor
Join Date: Nov 2009
Posts: 1,502
|
No. The arrow indicates that you have a trade-off, nothing more and nothing less. And, if you're at PL 10, a 14 Toughness has a tradeoff. I do agree with you that they'd simplify things by amending that message to "This trait is too high for the current power level without a tradeoff" in case people miss the "Tradeoff" text at the top.
|
#8 |
Junior Member
Join Date: Apr 2013
Posts: 20
|
Quote:
Power Level is a value set by the Gamemaster for the series as a whole. It places certain limits ... Power Level imposes the following limits: ...This is exactly counter to the "This trait is too high for the current power level" message Hero Lab gives. Quote:
Quote:
But thank you for your explanation. I don't want to come off as hostile, just argumentative. |
|||
#9 |
Junior Member
Join Date: Apr 2013
Posts: 20
|
Quote:
Maybe it could alert the user just before a trade-off is getting close, but a) Hero Lab just flags any stat over PL, regardless how much 'room' is left before PLx2, and b) Hero Lab handles trade-offs automatically and generates a validation report anyway! There's no need for the trade-off alert at all. To say "This trait is too high for the current power level without a tradeoff" would imply that one is past the limit. That would be fine, but the limit is PLx2. I get the trade-off warning at PL+1. It should be fixed. |
|
#10 |
|
|