Tip for future reference: If you ever find yourself thinking “is X either a secret stealth nerf, or just a bug?”, then the answer is almost always one of two things. Either 1) it’s just a bug, or 2) you were wrong about something in the first place.
Given that, I suggest you first double-check and verify your numbers, and if they still look wrong, file a bug report in the Support section. Veiled insults or implications help no one.
You forgot option 3: it might really be a nerf from the devs.
My numbers are absolutely correct +11,+19,+19 and +11 was old Paragons bonuses and +8,+14,+14 and +8 are actual bonuses. All sentinels from all members to the max.
btw I have no idea where you saw veiled insults in my previous post?? If not only you have nothing useful to write in my thread, but you also invent things, I guess its better to just shut up!
I forgot nothing; I told you what the answer almost always is. If you double checked your numbers, then go post a bug report in the appropriate forum.
Starting your post off with vague “secret nerf” questions comes across as accusatory and insulting. If you feel that my telling you the correct course of action to report a bug is “nothing useful”, then I don’t know what else to tell you.
You told me nothing useful in your 2 answers! All I need is an answer from a dev as stated in my 1st post.
I wrote all ranks bonuses before 3.2 update and now only rank 5 is the same (5, 10, 10, 5)
Another example is rank 2: +9, +17, +17, +10 before update and now its +7, +13, +13, +7.
Well as my numbers are 100% correct (no need to be a genius to write paragons bonuses when all 30 members had their sentinels to 5 and to do it again after 3.2 update) There are 3 options:
Its a bug
Its a nerf that is not secret and I simply didnt find it on the patch notes. (would be my fault)
Its a nerf that has not been communicated from the devs.
I’m on PC steam.
And, unless my childhood arithmetic class failed me completely, I’m pretty sure the numbers in these Sentinel equations don’t add up. @Ozball, is this another known bug issue?