Increase Attribute not working correctly
 

I get a warning for multiple stat advances within a rank.

I chose an attribute for my Novice rank at experience 5
I chose an attribute for my Seasoned rank at experience 20
I chose an attribute for my Veteran rank at experience 40

I believe the warning first popped up when I took an attribute increase at 20 xp. This should be ok, not a warning.


Cheers!
Texaspoet

Think I had a similar problem - in the end I removed all advances and put them in again (with attributes at the "right times") and finally it validated.

What was hidden to me was the order of the advances - once I'd added them they appeared alphabetically, so it was hard to see when the "one per rank" attribute advances had been taken.

More of an annoyance when creating a high-level character, where you know you want a few attribute advances. Would be good to have visibility of the advances ordering somewhere I guess - and possibly the ability to shift them up or down too ?

Yep. There seems to be some ordering problem from when you buy your Attribute increase. It doesn't matter if you buy one at Novice 15xp and then again at Seasoned 20xp, but Herolab isn't doing that correctly.

I just made a new character to re-check it. Took Attribute Increase at 5 xp, and then again at 20 xp, and it gives me the multiple attribute increase within a rank warning.

Yeah, feature request: Show the Advances by when you bought them:

Novice 5 xp:
Novice 10 xp:
Novice 15 xp:
Seasoned 20 xp:

And so on. Then allow them to be edited individually so that you don't have to kill the whole process. You can go delete your Novice 10 xp Advancement and replace it with something else that is appropriate.

This bug was due to the logic overlooking that the first transition between ranks occurred between advancements #3 and #4. It's fixed in the imminent update.

All advances are shown in reverse chronological order of how they were added, so the display already offers a clear history.

Changing advancements out of order is not possible. The reason is the design of the game system. The cost of boosting a skill depends on its current rating relative to the governing attribute, so the sequence is critical. If this order dependency did not exist, advances could be re-sequenced and edited. Alas, that's not the case, so HL has to enforce the rules by tracking the explicit sequence in which advances are gained.

Ah sweet, thanks Rob!