Yes, it was doing this even last year on the console side.
1 Like
Mobile beta testers, @Ozball
Is this how the game was performing during beta and is supposed to perform now?
Galaxy s8, 7.0
1 Like
I donât know if this has been reported as I havenât gone over all comments here but there is a visual glitch when in soul forge menu.
Seems smoother than on my mobile⌠I should learn how to caption, to show 
For 4-matches and skulls, it has been changed to match console AI behavior, and I find this bad.
I mean, tricking and baiting AI by doing the good cascade to make a skull match position for AI, and thus avoid AI to cast a spell was an aspect giving GoW a puzzle felling. Now, it will just be a race to the one who fill mana first and cast, without any need of a brain.
3 Likes
How are you playing on OSX?
Dear devs, as some people said above, my game as become very laggy since the last update, even in the lowest graphic details and power saver on. My phone is not the best one on the market but not the worst either. Itâs a Huawei p8 lite. The problem here is that makes the game horrible to play, so horrible that annihilate all kind of fun playing. I know you will create a patch for this issue in the 3.2 but to be honest, if I have to wait 3 months for a solution since the patch goes out, I will have to quit the game after almost three years of daily logging. So please dear devs, I know we players are annoying and we ask you a lot, but this issue is a priority, please, make the game fluid again into a short time. I believe in you. P.s : pls give me some answer to know what are you thinking about this issue. Thank you.
4 Likes
BTW, I found another 2 workarounds:
- press the home button to minimize the game before locking the phone screen.
OR - launch a different app from the lock screen (swipe left for Siri App suggestions or something)
Just had a crash on iOS.
iPad mini 2, ultra-rare graphics, power save on.
I first did the quest lines for both soulforge and dungeon. This was with a TDS dragons tean.
Then I started my first GW match.
It was my Hydra/Dryad/EK/Apothecary team vs at least EK/Valkyrie/something/something. My team was fully traited, so when I fired Apothecaryâs spell the entire opposing team got stunned. Thats when the crash occured.
It makes sense that my device ran out of memory but I find it disturbing that this happened with the default setting.
1 Like
I had no idea what the % was for. Thanks for explaining it.
With mythics costing 4,000 diamonds itâs pretty stupid there is a chance you wonât get any diamonds from the fights.
2 Likes
I agree completely (and so do others based on posts Iâve seen today). Right now the only guaranteed way to get Diamonds is to buy them.
1 Like
Itâs too pay to win for my liking I wonât be spending money on them again.
1 Like
To be fair, we get free Gems from tasks/tribute and we can get a slow trickle of them from maps, but depending on how much the amount of raw Gems from tasks was reduced and what percent was converted to Gem keys (which to me are a lot less useful than the Gems themselves) this could become an even more blatant pay-to-win mechanism. The $5 daily bundle is already iffy, in my opinion.
The update just went in 17 hours ago (on PC), though. I think itâs best to reserve judgement for a little while and see what, if anything, is adjusted.
Note: Iâm NOT against there being an advantage for paying players. Iâm against an exponential/grossly lopsided advantage.
1 Like
Most mythics are not âinsta-winsâ. Most mythics arenât even as good as many of the legendaries. Whatâs P2W about using money to get a semi-decent Mythic more quickly than someone who doesnât pay? And how is that any different from whatâs always been the case? Havenât payers always been able to progress toward mythics more quickly?
With the gem nerf itâs going to be even harder to get mythics
Not really. The math is pretty straightforward:
- Before you were getting enough gems to probably get one mythic every month. Thatâs 3 in 3 months.
- Letâs assume that youâre now getting enough to probably get one every 1.5 months. Thatâs 2 in 3 months.
- Now youâre also guaranteed to get one of your choice for free every 3 months.
So even if we assume the situation is 50% worse (and it clearly isnât) then youâd still be breaking even. You also have the benefit of guaranteeing that you get one mythic in that time, and that itâs one you want. And I think there are many players that will testify to the fact that probabilities can also mean that you donât get a mythic for much longer than what the average gems should suggest. The fact that youâre now guaranteed to get one at least every 3 months is a huge boon.
The ability to get mythics (and especially the ones you most want) is objectively much better than before.
I have spent everything I have had but I missed out on the last 3 mythics. It depends on how many diamonds we get from guild tasks because at the moment we are only guaranteed 1,680 diamonds every 3 months and and that is spending 350 gems a week for them. I would be a lot happier if they reduced the amount per battle but guaranteed them for every battle at least that way everyone can get them without having to spend real money to get a decent amount.
My biggest problem with this is the luck factor there is a chance you wonât get any from battles in a week.
1 Like
Iâm not sure how to qualify this, exactly. The new version is just crawling on my Nexus 5X. Itâs not âliterally unplayableâ, but itâs darn close. Itâs lagging for everything, gem matches and explosion spell effects especially. I turned the graphics settings to âcommonâ, but thereâs no perceptible perf difference.
If you wanted to nerf TDS, there are better ways than by making his spell lag so badly 
1 Like
One of your choice for free every 3 months? The estimate for that is 5-6 months, last I saw.
You can spend gems or real money daily if you choose, but 1,500 gems a month is a big investment and we donât know how badly our raw gem income has been nerfed yet, between the â16-20% reduction in gem value of tasksâ and the âsome gem prizes have been turned into gem key prizesâ vague patch notes.
Iâm also seeing this behavior 100% of the time on both iPhone 6 and iPhone 7 when Power Saving disabled. The âenable power savingâ workaround fixes it for me. Thank you for that! 
1 Like