Major Flaw in the Krayt Raid
The raid has a 3 day timer with a 90k ticket cost. The guild I'm in has it set to auto launch. The raid system has failed to finalize the results in time and has missed the auto launch window multiple...
Forum Discussion
Why this is a nothing bug even at a 10 minute delay per raid. So first at 10 minutes per raid, you need to launch 144 raids before you “lose a day of tickets.” However, if your guild didn’t average 29930 tickets or more for 436 days you’d have lost a day raiding due to not having tickets and the 144 raids restarts because you shift to launching raid back to right after guild reset. Of course the smaller the delay is consistently the closer to perfect you have to be on tickets.
Now, if you do manage to make it a full 444 days where your guild averages more than 29930 tickets, you are only “losing tickets” if your guild averaged more than 29965 because if your guild was between 29930 and 29965 you can handle getting a 4 days of tickets in a 3 day window.
But what of roster locks you say? Tw and gac are on 28 day cycles while the raid is on a three day cycle. It’ll take 84 days to complete the pattern of locks. So, there is no sense in trying to “time a raid ending for right before a lock.
That all said, if it’s an easy fix to make it exactly 72 hours by all means.
Now, if you do manage to make it a full 444 days where your guild averages more than 29930 tickets, you are only “losing tickets” if your guild averaged more than 29965 because if your guild was between 29930 and 29965 you can handle getting a 4 days of tickets in a 3 day window.
But what of roster locks you say? Tw and gac are on 28 day cycles while the raid is on a three day cycle. It’ll take 84 days to complete the pattern of locks. So, there is no sense in trying to “time a raid ending for right before a lock.
That all said, if it’s an easy fix to make it exactly 72 hours by all means.
