Well, if a rollback is done, they should lose the token, as well as any songs bought in the shop. Only problem is that if people actually earned a token, they would lose it.
To add on what my brother has said, A data base keeps all of the activity logged and it is saved. Depending on how much the host reserves for previous activity, a rollback can be executing.
What this rollback does is restore the database to a certain time. So lets say they decide to rollback the database to its activity 2 minutes before this glitch happened. Then all of your games, challenges, tokens, everything would reset to what it was 2 minutes before this glitch happened.
Since half of the community probably purchased all of the songs they missed, I am pretty sure a rollback is going to be the choice to not only give back missing/gained credits, but to ensure that users who started yesterday don't have all of the songs by just a glitch.
Originally posted by Tasselfoot
we have a credit count backup from a few days ago. i believe we'll be using that to re-set everyone's credit counts.
I guess it isn't as much as resetting the entire database, good call!
I want to know what on God's green earth happened. This kind of thing just doesnt happen on a perfectly good site. who was messing with the server here recently?
Comment