Powerplay 'Maintain rating 5' is going to be easier from now on!

It's shocking me. I was gaining 5333 merit per cycle so as to keep my rating 5. For 3 week. Then, 1 month later, I see this.

A99DABB9D217DEBC559DC8DF24EDB15E9CFDB1A3

You need at least 100 merit to be rating 2. But my current merit is 83. ?! Still rating 2.

You can type&search; 'elite merit fall off' on google. 'at 26/05/2017' every guide from each forum were wrong about keeping rating 5. I remember finding 1 discussion said "we need around 3,400 merit". Too bad, I lost the URL.

Every of us (me included), shared the same common misconception. To maintain 'rating 5', your merit must be at least 10,000 before each cycle end. When the cycle end, your merit will fall off between 5,000 - 8,750, but you will stay rating 5.
Just forget about all the table and calculation, you might have seen before. They all true about 'How merit fall off', only make us think we need 5333 merit per cycle to stay rating 5. Your merit that exceeded 10,000, are wasted.
Make this simple; Every time you see your merit lower than 10,000 (still at ratings 5), just top it up to 10,000. No more overflow merit.

Algorithm for efficiently maintain ratings 5 (For some proving only, remember the word "Just forget about all the table and calculation"?)

c(0) = 0 {You're starting with 0 merit.}
n{Power Play Cycle}12345678910
r(n){merit Achieving before the cycle end}10000100001000010000100001000010000100001000010000
c(n){merit at first minute of current cycle}0500075007500687562506249652966236570
m(n){merit Gaining at current cycle}10000500025002500312537503751347133773430
c(n-1){merit fall off from last cycle}0500025001250125015621875187517351688
c(n-2)0025001250625625871937937867
c(n-3)0001250625312312435468468

r(n) = c(n)+m(n)
"c(n) = [c(n-1) + m(n-1) + c(n-2) + c(n-3) + c(n-4)] / 2" only true if "r(n) >= 10000"

Your target Merit for each cycle is m(n).
RESULT: (counting from Cycle 1 to 8)
earn ratings 5 atcycle 2 (7 days)
earn ratings 5 for7 cycles (49 days)
total merit Gaining needed between cycle 2 to 824097
total overflow merit between cycle 4 to 100
 
Last edited:
I think you have a misconception when ranks awarded. PP rankings are awarded at the end of each cycle for the next cycle. How high your ranking is depends on how your merit end balance before decay.

When the cycle ticks merits decay at a 50% rate and merits older than four cycles are completely discarded one month after you earned them (after decaying three times). Look at this FDev post to assure that's how it actually works.

I.e. in your screenshot you had at least 100 merits last week. So you are rank 2 now. To keep rank 2 you'll have to do at least 17 merits this week. 18 to be sure rounding doesn't play tricks on you, it's always dangerous to just go to the exact number.

So yes to be rank 5 in the following cycle you must have an end balance of at least 10k merits this cycle. The guides you read were probably min-maxing ones with minimal (constant) weekly merit counts required to keep a rank.

I.e. if you do 5334 merits your week that's the most efficient way to keep rank 5: 5334 +5334*0.5 + 5334*0.5² + 5334*0.5³ + 5334*0= 10001.25

You are correct in your thought that doing 5334 every week is not what you want to do if you have fluctuations in your merit earnings. If you do 9k one week your merit load will be a lot lighter in the following cycle if you just want to reach 10k again. However in the long run the 5334 every cycle is the most efficient way to stay rank 5.
 
'Table for 5334 merits per week', include.

Your comment is ringing some-more idea. Now, I see that my screen-shot above didn't tell the whole things. I remembers FDev post well.
You are almost right about '5334 merits every week'. But 5334 isn't the most efficient way for ratings 5 anymore. It's the safely and efficient way, then it complicates thing.
We CMDR aware the risk of invest 100,000,000cr and start the ratings 5 at next cycle right-away. One mightn't make 10,000 merits in-time, I did. When it come to maintain the ratings. Do we just work up to exact-10,000-merits again before the cycle end? Or do we even need to exceed 10,000 merits, so at the first minute of next cycle our merit still higher than 10,000? How about testing things out, so we might go down to rating 4? No way! XD Then we play safe, exceed 10,000 merits. And it's work.
equation of safely maintain ratings 5 is below
Algorithm for safely maintain ratings 5

c(0) = 0 {You're starting with 0 merit.}
n{Power Play Cycle}12345678910
e(n){exceed & overflow merit}006682668400146675000516752505292
r(n){merit Achieving before the cycle end}533480011066812668140011466715000151671525015292
c(n){merit at first minute of current cycle}0266753347334866793339666983399169958
m(n){merit Gaining at current cycle}5334533453345334533453345334533453345334
c(n-1){merit fall off from last cycle}0266726672667266726672667266726672667
c(n-2)0013331333133313331333133313331333
c(n-3)000666666666666666666666

r(n) = c(n)+m(n)
"c(n) = [c(n-1) + m(n-1) + c(n-2) + c(n-3) + c(n-4)] / 2" only true if "at n >= 3, r(n) >= 10000"

Always earn 5333 Merit for each cycle, m(n).
RESULT: (starting from Cycle 1 to 10)
earn ratings 5 atcycle 4 (21 days)
earn ratings 5 for7 cycles (49 days)
total merit Gaining needed between cycle 4 to 1037338
total overflow merit between cycle 4 to 1032045
'5334 merits per week' is OK if you working for Li Yong-Rui, gain 200% exploration data payout. But newcomer who want to tryout ratings 5 (or try to earn income from FAST TRACK alone), 'more 1934 merits per week' can make the difference. (5334-3400 = 1934) And that's why the Power Play is dying out.
We can improve the efficiently. Simply by gaining 5334 per week, and after you reach 10,000, don't FAST TRACK to exceed 10,000 merit. It's a waste.
Equation of safe and efficiently maintain ratings 5 is below;
Algorithm for safe and efficiently maintain ratings 5

c(0) = 0 {You're starting with 0 merit.}
n{Power Play Cycle}12345678910
e(n){exceed & overflow merit}0000000000
r(n){merit Achieving before the cycle end}533480011000010000100001000010000100001000010000
c(n){merit at first minute of current cycle}0266753347000716666666375637564996567
m(n){merit Gaining at current cycle}5334533446663000283433343625362535013433
c(n-1){merit fall off from last cycle}0266726672333150014171667181218121750
c(n-2)00133313331166750708833906906
c(n-3)000666666583375354416453
Earn 5333 Merit for each cycle, but avoid an exceeded-10,000-merits.
RESULT: (starting from Cycle 1 to 10)
earn ratings 5 atcycle 4 (21 days)
earn ratings 5 for7 cycles (49 days)
total merit Gaining needed between cycle 4 to 1023352
total overflow merit between cycle 4 to 100
Remember, the Thargoid and Pirate cannot steal your merit, the only way you could steal your own merit is to blow-up your own allies ship. So, let the Power on playing again.
 
Last edited:
Sorry didn't really notice your formula work in my first reply.

So we agree that r(n) (which defines rank for cycle (n) = c(n) + m(n)

However your c(n) formula is not correct. c(n) is just the merits you earned in cycles c-1, c-2 and c-3. Of course properly discounted.

So using your notation: c(n) = c(n-1) + c(n-2) + c(n-3)

All merits from cycle n-4 or older are completely discarded and have no influence on c(n).

There is some other error in your tables, probably a spreadsheet formula calculation mistake?

We know that the decay rate is 0.5 so c(n) can be r(n-1)/2 at most ( =r(n-1)/2 if there are no old merits to completely discard). Unless there is a strange bug bitting the only inconsistency with that is on the +/-1 merit level from rounded numbers. If you look at your tables for all n > 2 cycles that's not true.


So your table should actually look like this (rounded numbers for c(n-2), c(n-3), c(n) & r(n)):

c(0) = 0 {You're starting with 0 merits.}
n{Power Play Cycle}12345678910
e(n){exceed & overflow merit}0001111111
r(n){merit Achieving before the cycle end}53348001933510001100011000110001100011000110001
c(n){merit at first minute of current cycle}0266740014667466746674667466746674667
m(n){merit Gaining at current cycle}5334533453345334533453345334533453345334
c(n-1){merit fall off from last cycle}0266726672667266726672667266726672667
c(n-2)0013331333133313331333133313331333
c(n-3)000667667667667667667667
c(n-4)0000000000


The ever increasing c(n) in your tables is actually not possible with a constant m(n) over time because of the complete discarding of merits from cycles n-4 and older. What merit activity took place before that may as well have never happened, it's not an infinite series!

If your m(n) is always constant, let's say m = 5334 it follows that c(n) = c(n-1) + c(n-2) + c(n-3) = 2667 + 1333 + 667 = 4667 for all n (I know this is not the actual mathematical proof for that ;) ).

If you look at your second table, with those m(n) rates you'd actually never even reach rank 5 once!
 
Last edited:
I'm happy my equation catch your attention. How accuracy the number on these table is not to be focus on, and I'll update my table soon enough. My emphasis for this Power play is "Do not FAST TRACK to exceed 10,000 of your total merit, at any cycle." Blowing enemy ships then exceed 10,000-merit is totally fine, you're going to gain Cr from voucher anyway.
My stand is;
"FAST TRACK for ratings 5 every cycle, do nothing else at all, and you still gain positive income from cycle 4 (28 days) and every next cycle."
And I take no offence from anyone who would disprove my stand. It's a good feedback.
You can have a life anytime you want to. Power Play is not hard to maintain. There are many others things you can do while letting your ratings 5 go on with 4-hours maintenance. (But not for Colonia, just no. You don't go 20,000 ly away, with ratings 5 dragging you back to home-system.)
 
Last edited:
5333 merit per cycle to stay rating 5. Your merit that exceeded 10,000, are wasted.

Your misconception lies in the fact that no one is saying you need 5334 to maintain every cycle, we're saying 5334 is the minimum constant needed every cycle, if you choose to do exactly the same number of merits. Let's go through a few weeks (not recommended to actually do this from R1; it's a tremendous waste of time & cash).

Week 1: [5334]
Week 2: [5334] + [2667 carryover] = 8001
Week 3: [5334] + [2667 + 1333.5] = 9334.5
Week 4: [5334] + [2667 + 1333.5 + 666.75] = 10001.25 (R5)
Week 5: [5334] + [2667 + 1333.5 + 666.75] = 10001.25 (R5)
Week 6 (and so on): [5334] + [2667 + 1333.5 + 666.75] = 10001.25 (R5)

If you instead randomly do whatever is needed to make 10,000, you'll end up doing a cycle of more/less/more/less needed (because your carryover will change based on what you did last cycle). That's fine, but the end result in both cases is to reach near-exactly 10000 merits each cycle. No one is recommending waste. More a matter of people not wanting to do e.g. 1950 merits one cycle and then 5575 the next because you only did 1950 last cycle.

Let's say you have this carryover
[4600 + 2300 + 1150] = 8050 (1950 needed)
and only do the 1950 that cycle to reach 10000, you'll have to do a great deal more next cycle to maintain.
[975 + 2300 + 1150 carryover] = 4425 (5575 needed)
[2212.5 + 487.5 + 1150 carryover] = 3850 (6150 needed)
[3075 + 1106.25 + 243.75 carryover] = 4425 (5575 needed)
[2787.5 + 1537.5 + 553.125 carryover] = 4878.125 (5122 needed)
[2561 + 1393.75 + 768.75 carryover] = 4723.5 (5277 needed)
etc.

Rather a lot of people like having the same amount to do each cycle, e.g. so they can plan their other activities & time available.
Neither way is more efficient, the constant is just desirable to many.
 
Last edited:
It's taking me so long.

Too bad I didn't discover something new for the community, it seem. I still believe, I found at least 1 discussion said "we need around 3,400 merit". That would made 100% FAST TRACK on Rating 5, profitable. Then, I lost that discussion's URL. It's gone. So I'd prove the myth or find someone to help me out. And after you guys help me out, look like my discussion are going to join their rank soon(the lost discussion).
But I glad, I didn't post it on Guide Page. Then here lies the remain of my misconception that I hope to be made as example to prevent anyone to do so.
 
Last edited:
Back
Top Bottom