Nothing, my team is doing the same 25ish mill damage as always on NM.
Same. Nothing different for me, nothing changed in comp and normal range of results for me.
Eltox: Assuming you have the same gear as before, depending on what your comp, gearing and affinities look like you could theoretically see some reasonably sized range of results that fall in that 15-20m range and have it be normal.
My cb team seems to do different damage a lot. There are so many factors - how many poisons land, how many times crit rate is activated, and I'm sure other things. Against NM boss my team will do 15 - 30 million, typically around 22 million.
If you notice your team isn't doing as much damage try to close out before your team is dead and then re-attack cb. I do that if I pay attention and they aren't doing as much damage as normal.
7 runs isn't RNG in my books. It's possible, but not plausible .... and today I'm back to normal 23 & 25 mil
Every run is RNG. So if I understand, you do not believe a string of 7 runs with bad luck is RNG, but then your back to normal now. So this would imply they made changes to effect you and then changed them back 2 days later? You find that more plausible than RNG?
RNG would seem to be a much simpler, more plausible expaination.
I'm just trying to wrap my head around how 7 runs is not plausibly RNG? That's a tiny tiny sample.
Honestly, in this case, while I agree it probably is because of something random happening, my guess is the real culprit has something to do with your specific team. A few thoughts:
1) Have you checked whether your low damage coincides with specific affinities? Green especially throws wrenches into normal teams.
2) Is your team properly speed tuned? If not, it's possible there is some variance in the order your champs fight in - sometimes using abilities in different orders will result in different rotations, which could mean certain debuffs fall off, etc...
3) Do you have a stun blocker or cleanser on your team? If not, it's possible that CB is stunning a specific champ at a bad time, and causing the rest of the run to completely fall off. For example, if CB stuns the champ that you rely on to put ATK down, and as a result, CB is able to get an attack off without the debuff, it could easily result in your run just flat-out ending. Same deal for stunning a champ responsible for DEF up.
1) i always play against void
2) yes, well according to teh deadwood tool... but that wrecked my team
3) Yes I have Sep Sentinel getting extended by Aniri
Yeah .. it sounds silly right. But I didn't have time to post early this afternoon - I got 2 low low scores again .. 15mil both times and I HAVE A THEORY:
I *THINK* THAT I AM GETTING HIGH SCORES PLAYING ON MY IPAD AND LOW SCORES PLAYING ON PLARIUM PLAY ON PC
It didnt really occur to me until this afternoon that I've started to use 2 devices at different times. So, over the next week or so I'm going to record what goes on.
1) i always play against void
2) yes, well according to teh deadwood tool... but that wrecked my team
3) Yes I have Sep Sentinel getting extended by Aniri
Yeah .. it sounds silly right. But I didn't have time to post early this afternoon - I got 2 low low scores again .. 15mil both times and I HAVE A THEORY:
I *THINK* THAT I AM GETTING HIGH SCORES PLAYING ON MY IPAD AND LOW SCORES PLAYING ON PLARIUM PLAY ON PC
It didnt really occur to me until this afternoon that I've started to use 2 devices at different times. So, over the next week or so I'm going to record what goes on.
I can almost guarantee you that the problem will have nothing whatsoever to do with the device it's played on. They're all running the same codebase
Your response to point #2 concerns me. Why don't you put your roster and their speeds here? Pay special attention to whether your champs are running the Lore of Steel mastery, and whether they have sets that provide speed bonus.
One last thing to validate - make sure *none* of your champs have any of the masteries that provide speed bonuses or turn boosts based on events. Cycle of Revenge is usually the biggest culprit here.