With the release of Infinite Odyssey today, we have some of our 11th Anniversary events beginning, but more to come as the anniversary gets into full swing next week! We'll update you as we go with more information about what's coming in the weeks ahead.
In the meantime, you can check out the server settings that will be active for the event, as well as a timetable of events for a sneak preview.
Great, I get a black balloon stick on a toon I haven't played in 10 years that I cant even use on my character that I play now since for some odd reason, you can't trade any of these rewards that give no stats whatsoever so it wouldn't be game breaking in the least. Thanks. Free the gatekeeper hats, free the agathions..
Hey... I'm looking for a reply from the development team, or someone who can help. I posted the following many days ago with no reply at all, in the general technical sub-forum. It has to do with anniversary items:
"Typically, I am very understanding of certain issues knowing they usually get resolved in a reasonable amount of time. This particular issue is one that is not a bug, but a development oversight. I haven't seen anyone raise this issue yet, which leads me to believe nothing will happen unless someone speaks up.
Overview: I created my account during open beta (March, 2004) and played through OB, up to current times, with a few short breaks. As most of us have, I rerolled over and over until I found something I liked. My eldest toon was turned into a perma-red and eventually deleted because I had no way to know they would clean the slates across the board once in a while. Now, I do not have a toon that reflects my veteran status to receive the rewards for 10th and 11th years eligibility.
So... For those of us who have stayed through everything - and FFS, there have been times I wondered if I cared enough to continue playing (and paying) - why is it that the development team chose character creation dates, rather than account creation dates, to reflect someone's veteran status?
I was referred here by the support team after some communications via ticket submission. They said the best way to solve the issue is to bring it up with the development team on the official forums. So there it is..."