This is a known bug being patched during the extended down time today. The worst part about this though is it's a known bug and GMs will still refuse to reset your timer for you. I guess I can kinda understand the problem of resetting timers, but.. for known bugs?? Here's the explination I got on what caused the problem.
Quote:
|
After much explanations by the design team we finally understand why you and other players are getting longer lockouts. If you drop your instance timer for Emerald Halls after the new instance you go to was created, the time from the creation of the new instance up to the moment you actually entered is added to your timer. This means you have the initial 5 days plus the layover time from when you entered. This causes you to have a timer longer than five days. I regret to say that since this is working as designed we are no longer able to remove EH lockouts. The only way you will be able to get back in sync with your raid is to either skip a week or to have the raid wait to create a new instance until everyone has dropped the previous timer. I hope I was able to clarify the issue. My apologies that we could not remove your timer. If you have any other issues we may be able to address in the future, please contact us at your convenience. We wish you good luck and safe journey in the lands of Norrath.
|
Luckally I was able to get my timer reset after a little persistance, but isn't that explination a little confusing on what causes the bug?