ZiiKoraaviik Posted October 13, 2021 Share Posted October 13, 2021 Seems we went from armory chest cd to mass revival charms folks. Time for a hotfix 1 Link to comment Share on other sites More sharing options...
Cupidstar Posted October 13, 2021 Share Posted October 13, 2021 Yup, you read it right... You fixed the shared cooldown with Call to Arms event stuff, but you did this... 1 Link to comment Share on other sites More sharing options...
Ketsueki Tenshi Posted October 13, 2021 Share Posted October 13, 2021 (edited) Professional programming... at it's finest. Sigh, something tells me they got 1000s of items in their database. And different timers/cds on different values/switches. So once again they took one that is already in use, instead of making a new value, or use a unused one. So 2 items or more share the same value that triggers the same cooldown. In this case the lamb and the mass revive. Those items are so different from each other in functions in the game and yet... have both a bigger cooldown by default, and they just took same value by mistake. *Shrugs* and thus we see how they created this bug. Kill a bug to create one or more, gotta love game development. It feels like they not even test their fixes. No quality control at all... UE4 did help, but the code of the game is still spaghetti. Edited October 13, 2021 by Ketsueki Tenshi 1 Link to comment Share on other sites More sharing options...
ManIQ Posted October 14, 2021 Share Posted October 14, 2021 On 10/13/2021 at 8:15 AM, ZiiKoraaviik said: Seems we went from armory chest cd to mass revival charms folks. Time for a hotfix What bugs will emerge from their hot (mess) fix lol 1 Link to comment Share on other sites More sharing options...
Cupidstar Posted October 14, 2021 Share Posted October 14, 2021 6 hours ago, ManIQ said: What bugs will emerge from their hot (mess) fix lol Cooldown being shared with Reputation Charms (24 hours). Link to comment Share on other sites More sharing options...
NCSOFT Rynara Posted October 19, 2021 NCSOFT Share Posted October 19, 2021 Hi there, thank you for your report and your patience. The team has investigated and identified the cause of the issue and a fix for this should go live on Wednesday with the maintenance. The QA team has also developed some checks they can run to catch these kind of errors sooner. 1 Link to comment Share on other sites More sharing options...
metadune Posted October 20, 2021 Share Posted October 20, 2021 Nice, I like hearing that they developed checks for that too Link to comment Share on other sites More sharing options...
Recommended Posts