Spork98765
Member
- Jul 3, 2015
- 363
- 0
IDK if this is a matter of again or still, honestly. I reported this same issue on Android in May 2016 and it's happening again/still, but is also an issue on Steam.
Turning on pro mode overwrites local highscores - this isn't supposed to happen
Pro Mode isn't retaining ROM state - which it is supposed to do
Pro Mode isn't retaining secondary data (loop/ramp/combo champ etc) - which it is supposed to do.
Pro Mode isn't maintaining a separate and discrete local high score list - which it is supposed to do.
I'd report this to support, but reporting things to support@ is mostly an exercise in frustration as I have to explain to them how the program functions, and the last issues with pro mode I reported took over a year of reporting it every month before support was even able to identify that it was a bug. Then it took another 6-8 months after that for it to get fixed. Shortly after, Pro Mode was broken again with another update. :/
[MENTION=3799]FlippyFloppy[/MENTION]
Can there be some QA where the focus isn't solely on play testing the new release, but instead on assurance that new releases aren't breaking old features and tables?
Turning on pro mode overwrites local highscores - this isn't supposed to happen
Pro Mode isn't retaining ROM state - which it is supposed to do
Pro Mode isn't retaining secondary data (loop/ramp/combo champ etc) - which it is supposed to do.
Pro Mode isn't maintaining a separate and discrete local high score list - which it is supposed to do.
I'd report this to support, but reporting things to support@ is mostly an exercise in frustration as I have to explain to them how the program functions, and the last issues with pro mode I reported took over a year of reporting it every month before support was even able to identify that it was a bug. Then it took another 6-8 months after that for it to get fixed. Shortly after, Pro Mode was broken again with another update. :/
[MENTION=3799]FlippyFloppy[/MENTION]
Can there be some QA where the focus isn't solely on play testing the new release, but instead on assurance that new releases aren't breaking old features and tables?