pelle plutt
03-03-2015, 07:17 AM
Yes gree, i know that pretty much everything is broken with the app now and you are hopefully working on fixing some of it
Getting the chance now to see a bit on how you work "live" i can understand why nothing is ever working as it should
so this has happened: When you leveled to l302 the rivals list broke down and you could only see people around level 175 and around l250. After about 1 day gree managed to fix this and you could now also see people around your own (300+) level
When you leveled up to 303, the same isssue came back, 1 day later gree applies a fix..
exact same thing happened at level 304...
....then 305.... then 306
Gree, doesnt it ever occur to you to take a step back in look at what you are actively trying to fix? Everytime you try to fix an error/glitch you only fix the current symptom, never the actual issue
In this case, how can it come as a surprise that the same glitch will reoccur on each level, and why would you only develop a fix that manages the symptom on 1 level?
The exact same thing has happened with the 2.147bn glitch, how about you actually look at the app and replace all instances of where you use a normal INT and replace it with a LONG (or whatever does the same thing), instead of the users finding new glitches every week or so?
sorry for rant, just so upset with how things can be so poorly managed
/pelle
Getting the chance now to see a bit on how you work "live" i can understand why nothing is ever working as it should
so this has happened: When you leveled to l302 the rivals list broke down and you could only see people around level 175 and around l250. After about 1 day gree managed to fix this and you could now also see people around your own (300+) level
When you leveled up to 303, the same isssue came back, 1 day later gree applies a fix..
exact same thing happened at level 304...
....then 305.... then 306
Gree, doesnt it ever occur to you to take a step back in look at what you are actively trying to fix? Everytime you try to fix an error/glitch you only fix the current symptom, never the actual issue
In this case, how can it come as a surprise that the same glitch will reoccur on each level, and why would you only develop a fix that manages the symptom on 1 level?
The exact same thing has happened with the 2.147bn glitch, how about you actually look at the app and replace all instances of where you use a normal INT and replace it with a LONG (or whatever does the same thing), instead of the users finding new glitches every week or so?
sorry for rant, just so upset with how things can be so poorly managed
/pelle