Gylgamesh-KT Posted October 4, 2020 Share Posted October 4, 2020 Okay, if they cannot even fix this annoying pin bug I think they are hopeless. I have had enough, every time I try to log on I get that pin bug and not only once but twice. I get so annoyed that I have lost interest on playing and the events are just a waste of my time, I do not find Aion fun anymore. Link to comment Share on other sites More sharing options...
Arhangelos Posted October 4, 2020 Share Posted October 4, 2020 Yes, I get the pin bug more often than not getting it now. If I manage to log in I feel accomplished, when I see the actual pin window I legit feel happy that I do not have to close and re-open the client and gamble my entry again. Link to comment Share on other sites More sharing options...
Azzmaria-KT Posted October 4, 2020 Share Posted October 4, 2020 I managed to avoid that not double clicking on each toon. Just selecting it once and pressing start on botton. With that I don´t get the bug (yet?). Link to comment Share on other sites More sharing options...
Arhangelos Posted October 4, 2020 Share Posted October 4, 2020 1 hour ago, Azzmaria-KT said: I managed to avoid that not double clicking on each toon. Just selecting it once and pressing start on botton. With that I don´t get the bug (yet?). Well this is how everyone initially started their game, but it quickly became the way to avoid. Now double clicking summons the pin bug more often. Link to comment Share on other sites More sharing options...
SKLWerKing-KT Posted October 4, 2020 Share Posted October 4, 2020 It only happen on the Katalam server! NCWEST Code something bugged and can't fixed it. NPC bug coming today too. How they let this bug alive few month. They didn't got paid for their Job? Link to comment Share on other sites More sharing options...
Vantheria-DN Posted October 5, 2020 Share Posted October 5, 2020 23 hours ago, SKLWerKing-KT said: It only happen on the Katalam server! Can confirm. I haven't had the pin bug on DN since I upgraded to the new launcher. So it's a KT problem -- like many other problems. Link to comment Share on other sites More sharing options...
Arhangelos Posted October 6, 2020 Share Posted October 6, 2020 21 hours ago, Vantheria-DN said: Can confirm. I haven't had the pin bug on DN since I upgraded to the new launcher. So it's a KT problem -- like many other problems. If I had a character in DN I would log there to put the pin, log to char select, change server, select katalam and then login without the necessity to use the pin. But I am 12/12 on Katalam so no way to do this. I bet this has to do with the fact katalam has more population and their server gets overload. Danaria is underpopulated. Link to comment Share on other sites More sharing options...
Azzmaria-KT Posted October 6, 2020 Share Posted October 6, 2020 On 4/10/2020 at 7:18 AM, Azzmaria-KT said: I managed to avoid that not double clicking on each toon. Just selecting it once and pressing start on botton. With that I don´t get the bug (yet?). Nope. I was wrong. Even whit the "start" option the bug happens. Link to comment Share on other sites More sharing options...
Gabrielis Posted October 6, 2020 Share Posted October 6, 2020 I had a client crash today followed by pin bug 4 times in a row (i logged in onto website after first 2 pin bugs but it still occured another 2 times) so I could only relog after 5 attempts. Link to comment Share on other sites More sharing options...
kober-KT Posted October 7, 2020 Share Posted October 7, 2020 Imagine having 7 pin bug in a row.. ughh Link to comment Share on other sites More sharing options...
Vantheria-DN Posted November 12, 2020 Share Posted November 12, 2020 On 10/5/2020 at 8:32 AM, Vantheria-DN said: Can confirm. I haven't had the pin bug on DN since I upgraded to the new launcher. So it's a KT problem -- like many other problems. Oh damnit. As of yesterday's server move, the pin bug is back on DN server. Welp, it was nice while it lasted. Smh... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.