Okay, I have no idea how many people are affected by the cookie limit in terms of switching computers (for whatever reason - being at school/university, not saving cookies, etc) so don't know how useful or indeed used this system would be, but I propose a slight alteration to the cookie limit lock scheme.
At the moment, when you hit a certain number of logins without a cookie, your account is locked out for a finite period; irregardless of the fact you may have logged in from that exact computer before.
I suggest that along with a cookie check, your are subjected to an IP/Agent/time/etc check as well.
If that doesn't quite make sense, read on...
Say somebody logs onto their Bushtarion account from a computer at University at lunchtime, 1300 hours, on a Friday to plant some seeds and send out an attack - for simplicities sake, their Cookie Limit is currently at two, but after this login, has decreased to one.
Under current conditions, their next login would be subject to a lock out. Under my proposed solution, if the same person came back to the same machine at 1700 hours on the same day and logged in successfully, they would be informed that although their cookie limit is at one, they logged on via this IP&Agent combo* less than 12 hours ago and thus are being granted access anyway.
This would reduce overall cookie limit lockouts and irritate less people (willym..?)
If people are concerned that if it was someone else that logged onto this machine and somehow logged in to this other persons account and was granted access, then you could make it a 'limited' access session - IE they can access everything EXCEPT account/preference controls (ie they can't delete/change details, etc, they can only do gameplay-related stuff).
* This could be a combination of anything that might be able to identify the individual PC. I believe Azzer has methods for this detection anyway...
Again, I'm not 100% sure how many people this cookie thing affects but this was an idea I just suddenly had while at Uni (hence why I didn't just send it straight to you, Azz) and figured it might be worth posting to see if anybody actually cares
At the moment, when you hit a certain number of logins without a cookie, your account is locked out for a finite period; irregardless of the fact you may have logged in from that exact computer before.
I suggest that along with a cookie check, your are subjected to an IP/Agent/time/etc check as well.
If that doesn't quite make sense, read on...
Say somebody logs onto their Bushtarion account from a computer at University at lunchtime, 1300 hours, on a Friday to plant some seeds and send out an attack - for simplicities sake, their Cookie Limit is currently at two, but after this login, has decreased to one.
Under current conditions, their next login would be subject to a lock out. Under my proposed solution, if the same person came back to the same machine at 1700 hours on the same day and logged in successfully, they would be informed that although their cookie limit is at one, they logged on via this IP&Agent combo* less than 12 hours ago and thus are being granted access anyway.
This would reduce overall cookie limit lockouts and irritate less people (willym..?)
If people are concerned that if it was someone else that logged onto this machine and somehow logged in to this other persons account and was granted access, then you could make it a 'limited' access session - IE they can access everything EXCEPT account/preference controls (ie they can't delete/change details, etc, they can only do gameplay-related stuff).
* This could be a combination of anything that might be able to identify the individual PC. I believe Azzer has methods for this detection anyway...
Again, I'm not 100% sure how many people this cookie thing affects but this was an idea I just suddenly had while at Uni (hence why I didn't just send it straight to you, Azz) and figured it might be worth posting to see if anybody actually cares
