If you went from having a lot xp trained in a few areas to having less xp trained in more areas then it may be that MPR is calculated not by xp trained but by the levels of the spells trained

For example if you train 100xp into one spell/stat you will get you get a level of x, if you train the same 100xp into two spells/stats each will have a level of y for a total of 2y.

now while it is obvious that x>y, it is also true that 2y>x (because of the increasing costs of each level)

So if (and this I am not sure of but it could be figured out rather easily) MPR is calculated by the level of the spells and not the actual xp spent on those levels then it could be possible to increase pr by splitting the xp from the untrain into more areas than they were in before the untrain.

If someone wants to see if this is true find me in chat and we will test it out.

When you untrain you only get a % of the xp back that you put into it initially, so you have less xp to train and thus (at least when untraining one-for-one) your MPR does go down. The question that Derek is asking is why his MPR went UP.

hmm, I had around 277 k mpr, untrained GA, and retrain it to AS. Then, my MPR became 220 k+, that's normal ? I just thought it might have some connection with Derek's MPR jump. I made a thread about it like a week ago, but no one seems to know what's the problem.

My untrain/retrain was pretty much a straight swap of spells on my minion that previously had the ROE equipped so I don't think it's to do with splitting my XP amongst more spells. The PR jump was slightly more than 20k - you can see it on my history graph, although it doesn't show up that well.

I also just did a *minor* retrain and my mpr jumped by about 10 to 15K. Like Derek, I had NO unallocated XP.

I also notice that the first battle after training (in this case, I mean the routine allocation of XP) does not show any RoE rewards. It is only in the second and subsequent battles that the RoE minion gets a bonus.
This is not a biggie, just an indication that something is amiss.

This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=001U11">Possible Bug....</a>