eShock wrote: @MikeHock, I'm a programmer (not for Demiurge), and looking over the descriptions of this bug. my gut feeling is that this is the sort of bug that takes a LOT of dev AND QA effort to handle.potentially difficult to even find the root-cause of the bug probably involves messing around in core parts of the game logic, which is inherently risky, since: potentially conflicts with other developers working on other features/bugs in the "best" case where it would be a small code fix, it would still require tons of QA time and effort for regression testing to make sure that all of the matching/cascading logic still works properly (let alone verifying all the edge cases to prove that the bug itself is fixed). There are probably tens to potentially hundreds of test cases involved (think board layouts + various characters on each team) in the "worst" case it might require a major refactoring of their core match/cascade game logic, so the same statements about QA regression apply but on a bigger scale. And unfortunately (for us users who know about the bug), in the grand scheme of things it's also a relatively lower priority bug, since doesn't crash or break the app battles still work more or less fine (tile matches still happen, damage gets done, AP is obtained, passive powers trigger), even though not in the "expected" way doesn't happen all the time, and most players probably don't even notice the issue even when it does happen issue has been present for many months, possibly since the beginning (which means it isn't urgent) So in summary: yes, the Devs have admitted that the behavior is not the intended effect (so yes, they know about the bug) it will probably take a LOT of effort to fix, and so is difficult for them to balance priorities and schedule time to fix it So we'll just have to be patient on this one.
"David wrote: Moore"] MikeHock wrote: LOL, unanswered ticket from 4 months ago. Good to see MPQ is back to its standard of customer dis-service. Please note the date of the post - Jan. 17. The ticket in question was handled back in January. Customer Support is operating normally and handling tickets in a relatively speedy manner at the moment. If you have an issue that you need assistance with they'd be happy to assist: https://d3publisherofamerica.zendesk.co ... quests/new Thanks!
MikeHock wrote: LOL, unanswered ticket from 4 months ago. Good to see MPQ is back to its standard of customer dis-service.
cynder9792 wrote: They have bigger issues at the moment I am afraid, all revolving around the R76 patch (TTS tiles not firing properly, multiple device bug). I have seen this also and gave some thought as to why it sometimes explodes and other times it drops. In the bigger scheme of things it is really not that big of an issue as a previous post said - you still do damage, gain ap, etc...I find that sometimes when it does drop it can be a game changer as there are no matches for where it drops thus you need to make an additional match that may give the opponent an advantage. Best advice is to just let it ride. Would you rather have them devote hundreds of hours to a minor glitch or work on more pressing issues that affect the playability of the game?