Lag in bahamut fight

Xoxo18Xoxo18 Member Posts: 46
edited May 2023 in General Discussion

I don’t know if it’s just me but the game has been really laggy recently especially in big health pool fights. I started the quest fully prepared with 800+ units I got to him after using like 200 units I started the fight but quickly noticed how much lag his special cause at first I tried to decide but kept getting clipped and after many revives I reached his phase 2 and now I no matter what can’t parry or heavy his blast because the game lags so much that the timing is always off. I don’t think my phone is the problem because I use a iPhone 11 and can smoothly operate in all the other games but mcoc. It is always moments like this that make me want to quit the game because I am a free to play player and the units took a lot of time to get. I am not expecting any compensation but I want the word to get out to any other player that is thinking of attempting the fight.

Comments

  • KnightOfTheRealmKnightOfTheRealm Member Posts: 950 ★★★
    Did you get a removal charge first?
    You need to launch a special into the blast with 3 volatility or more to gain a removal charge, then after that you have to build him back up to 3 volatility and parry/heavy the blast to remove the armor.
    Repeat this until the phase is over, then do the exact same thing for phase 3. Only difference with phase 3 is that there's a chance of fire blasts, which are not able to be blocked so just dex these. It will warn you when a fire blast is coming.
    For phase 4, you don't need a removal charge, just keep getting to 3 volatility and parrying the blast back and forth. The more times this occurs the more damage you will do. It's a very fun and well designed fight once you get used to it.
  • Drago_von_DragoDrago_von_Drago Member Posts: 938 ★★★★
    Also, close and reopen the game when you notice it starting to slow down. If I play for too long without restarting I notice more lag. Restarting usually helps a bit. I think Kabam or someone else familiar with the problem referred to it as a “memory leak” issue. Whatever it is, closing and restarting the app tends to help for me.
Sign In or Register to comment.