hexagram wrote:Question for the person who discovered the bug. How did it work and how could you get unlimited gran - it does not make sense to me.You can tell us or pm me as mirage master is disabled now.
Hiya Hex, i'm surprised you didn't know it was me who reported this and "tested" it extensively.
I can't give you precide times and dates, but here's the general development of the issue...
i was playing randomly then i accidentally clicked MM pre-maintenance and saw gran, which i did. after finishing and receiving the gran, saw it was still there. Did it a second time, and it happened again. Since, as you may already know, the gran amount in the My Iczer tab does not automatically refresh, so i relogged. Could not log back in because of maintenance. Got on AFTER maintenance and saw gran still there, did once, then it reset like normal. Illicit gran on first day = 30.
Tried to replicate the event by doing MM before maintenance. At this point i realized 15 before was sufficient. maintenance = 6pm philippine time so i went into MM 5:45PM, gran was there. Same scenario, but this time i ran mixes of different difficulties and stars to see if it affected all of the. Conclusion 1: it works consistently until 6:15PM (end of maintenance). Conclusion 2: the server is unstable, disconnection was about twice as likely as when playing in folart (which is not uncommon enough) but reconnection is possible until 6PM (meaning at most only 15 mins worth of MM time lost). Illicit gran on second day = ~100
On top of all this, i hopped into chat and asked around about this bug. People CONFIRMED IT EXISTS but it was apparently confused with another bug that lets people load MM and still do daily lotto pull netting at least a freebie card from lotto (which was highly likely a 1* and sometimes a 2* anyway). I did not know that bug even existed but since its a bug, its not discussed openly anyway.
Day 3 onwards:
I tried "pushing the limit of time". i went slow, logging on by 5 mins earlier every day (not that i can't keep doing this every day literally since i have responsibilities at this time too, ie. work). The earliest i've managed to make after a couple weeks of testing was 4:50pm. This was with constant rotations of difficulty and disconnections.
In all this time, i realized that something was wrong with this... i immediately 1) emailed logress about this issue 2) filed a bug report using MM's tool (on the login page) 3) forum mailed Romdeau because i know how active the dude is and how fast he reacts to shyt.
Now the fun bit...
In all of this time, i kept spamming the chat and making it obvious that i'm getting illicit gran somehow, ofcourse many questions popped up but after saying i'm getting upwards of 300 gran a day i knew things would stir up. I NEVER disclosed how the bug worked and made sure i kept it secret while i continued to test it extensively. At one point, i had enough time and tenacity to super MM spam it to see my limit and i got ~700 gran in around an hour doing nothing but intermediate 3* (seemed the best winrate and return per time) and a pretty bad headache... because apparently that much constant focus strains the brain or something. Doing the match, i calculate upwards of 900 gran is possible in a day with back-to-back-to-back wins in intermediate 3*. That much gran leaking out is economy breaking.
I was intentionally creating animosity around myself, but i think people understood why i was doing it. Upon ranting by a guildmate i even wrote a public announcement for the bug here
. Then i mailed logress again, and even got a confirmation with MysteryMan on it.
and then... the fix they did turned out to be to remove it completely which is a dumb way to do it tbh, but i'm hopeful of its return.
Login an hour or so before maintenance, spam mirage master, gran does not set to 0 during this time, continue until mentally stressed or time runs out until maintenance end, get tons of illicit gran from wasting your time on a dumb minigame... buy set 13 stuff.
I'm by far the most vocal person who openly admits participating in this bug and has reported it... But i cannot believe that i am the only one.