So with that bug how I am supposed to fight Guardian in necro
SplinterBG
Member Posts: 24 ★
15
SplinterBG
Member Posts: 24 ★
Comments
I went the Apoc path and probably ate more revives just because I was afraid of this bug.
@Kabam Crashed @KabamPinwheel Would be really cool if you guys could help with this subject.
Necroplis obviously isnt like a simple monthly event quest. It's likely that a fair amount of resources are invested by the time people reach this bugged Guardian fight, so starting over isn't really practical. Likewise, waiting for the fix isn't practical either since it locks you out of all other quest content.
Myself, and I'm sure many other, don't go scouring the forums looking for known bugs on a necroplis path prior to starting a run. The right thing to do would be to refund the resources used on that fight for anyone that's encountered this issue. And it would probably be a good idea to throw up a banner notifying players of the bug if they choose to do a necroplis run.
Supposed to be fixed this week.
My initial experience was with Vox, but in my efforts to see if anything in particular was triggering it, I ended up using my whole team at least once.
Happened at the start of every fight. Did the standard, close the game, force stop, clear cache, restart, and that didn't help. Also toggled between 30 & 60 fps, with restarts in between, and that didn't help either.
1) Wait until the bug gets fixed, or
2) Throw an infinite amount of resources at it and then hope that Kabam responds fairly.
I'd go with Option 1.
Bcuz if Kabam decides not to reimburse any resources that I spent, I can't be mad. I made the choice to burn thru extra revives and units. 🤷♂️
Seem like the visual bug that been happening since beginning of December have to do with the environment and the setting around it, and how it interact with certain champion. For this case it look the opacity of the smoke/fogs in the foreground being too low for whatever the reason.
I have tested a same match up in Practice mode, the fight was in a different background and did not have any problem, which lead me to believe it is the background that cause the problem.
I test it in 4 different mobile devices, 2 android and 1 iOS all have the same visual problem. Luckily I managed to find an Android tablet that work and finished the fight.
The real concern if that fact that this bugs and many other have been going on for 1 month and a half, and we are only getting a fix sometime this week for some of the bugs.
At the same time we would normally have a big Warming Noted on the forum about these problematic fights, which there isn't any.
Kabam is trying to bring MCOC to PC and communication all over various social platforms, while low on human resource, the end reason is much lower quality on everything, game and communication.
They have challenges explicitly calling out Necroplis completion, and many will take that lane. As I pointed out though, many will not come here looking for bugs on the path before starting, nor should they be expected to.
I also like to play Call of Duty B06, but I don't go looking for bugs prior to equipping a new weapon for the first time.
@Fryday can you revive your incursion sector 4 thread. I want to check the status and can't seem to find it since your profile is private (why you made it private lol).
However, as I said, after spending some revives and potions I restarted the phone(not the game) and it changed to the other broken screen - the reddish screen that happens when fighing spidy ham. It is still broken but you see a bit more and that help me.
This should not happen in this mode, aq or aw, that counts as a blocker issue imo and is now too long in the game.
Thanks in advance!