Apoth: 58,474 damage taken

Lilithu: 49,964 damage taken

Siphi: 57,514 damage taken

Rothos the Broken: 3,452 damage taken??? 

What is going on here? Why is he taking more than 10 times less damage?

Is there a possibility of having Hatchet Slinger in the next events?

Please due to all the mess, im glad you prolonged fusion, but i beg you, give us second chance to get those rare heroes also.  I see now chance to get mystic hand, som please keep it like that. I was not able to get fleshmonger due all this, and he is not droping for me from shards. Thank you. Or you can push my luck a bit on my main account  um25672245 | 25233000. Kisses.

I am now realizing I missed the chance to get the champion "fleshmonger" from the reward events because I was dealing with being banned, I have worked hard to accumulate all the necessary requirements to get "Roto the missing groom" but now I cannot fuse him because I am missing that one reward that I would have obtained had I not been wrongfully banned due to the technical issue. I have not received this in the mail like you stated. I feel I should be compensated for this as well. Please let me know how this will be fixed, Thanks!

Come on, don't be stingy with events.

why so mad said:

Apoth: 58,474 damage taken

Lilithu: 49,964 damage taken

Siphi: 57,514 damage taken

Rothos the Broken: 3,452 damage taken??? 

What is going on here? Why is he taking more than 10 times less damage?

Hi, 

codyputnam said:

I am now realizing I missed the chance to get the champion "fleshmonger" from the reward events because I was dealing with being banned, I have worked hard to accumulate all the necessary requirements to get "Roto the missing groom" but now I cannot fuse him because I am missing that one reward that I would have obtained had I not been wrongfully banned due to the technical issue. I have not received this in the mail like you stated. I feel I should be compensated for this as well. Please let me know how this will be fixed, Thanks!

Hi,

Have you sent a request to the game support? 

Hey guys,

Just a quick reminder that posts with excessive swearing will be deleted from the forum. 

Angry Lady said:

Hi, 

What's the DD crit rate? 

Seer has 107% crit rate. She did crit, the text is in yellow. Rothos is bugged if there is a champion with damage mitigation passive on the team, or if Rothos has Stalwart gear. 

It happened to me many times that when Dutchess is one the same team he takes 1-3k damage while others take 50-100k he is bugged. I reported it in Discord, but it seems nobody is looking into it.

Here Sir Nick takes 105,009 damage, Rothos takes 1,445 damage. It is a bug because of Dutchess who in on the team.

Google Play rating is now down to 3.9 from a 4.2 three weeks ago.  Maybe it's time to re-evaluate? 

why so mad said:

Angry Lady said:

Hi, 

What's the DD crit rate? 

Seer has 107% crit rate. She did crit, the text is in yellow. Rothos is bugged if there is a champion with damage mitigation passive on the team, or if Rothos has Stalwart gear. 

It happened to me many times that when Dutchess is one the same team he takes 1-3k damage while others take 50-100k he is bugged. I reported it in Discord, but it seems nobody is looking into it.

Here Sir Nick takes 105,009 damage, Rothos takes 1,445 damage. It is a bug because of Dutchess who in on the team.

Right. Thank you for pointing that out. Pls check out 1.13.5 and let me know, if the issue is still present.

why so mad said:

Angry Lady said:

Hi, 

What's the DD crit rate? 

Seer has 107% crit rate. She did crit, the text is in yellow. Rothos is bugged if there is a champion with damage mitigation passive on the team, or if Rothos has Stalwart gear. 

It happened to me many times that when Dutchess is one the same team he takes 1-3k damage while others take 50-100k he is bugged. I reported it in Discord, but it seems nobody is looking into it.

Here Sir Nick takes 105,009 damage, Rothos takes 1,445 damage. It is a bug because of Dutchess who in on the team.

Right. Thank you for pointing that out. Pls check out 1.13.5 and let me know, if the issue is still present.