Major Flaw in the Krayt Raid

"BubbaFett;c-2423902" wrote:

"iMalevolence;c-2423885" wrote:

"Dawnsinger;c-2423883" wrote:
Our raid runs for 71 hours and calculates for an hour before auto starting at the same time every 3 days. Is yours lasting the full 72, or calculating for more than an hour? Seems bizarre it wouldn’t be consistent between guilds.

It has only failed to auto launch two or three times since we starting running it. But we capped tickets once because of it and therefore wasted rewards because of the bug. And it's not unreasonable to assume that the current implementation will screw over every guild in the game, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset window.

"Enigmatic_Potato;c-2423884" wrote:
Change it to auto launch immediately instead of a set time.

See above.

The raid runs 71 hours... If it launches at noon, it will finish at 11 o'clock 3 days later, spend an hour finalizing results, then launch again at noon...

Our guild had the same issue after they fixed the rewards. The raid didn't auto launch even though it was set to... I went in, reddid the launch commands and it had been working fine ever since.. I'd suggest you try that..

The failure to auto launch at a specific time is seemingly random. I assume because it depends on if the game fully processes your final results in that window. I assume more populated raid times means an increased processing time that exceeds the window, pushes the completion to slightly later, and then fails to auto launch because that time is gone.



Our raid was auto launched at 8pm 3 days prior and the game didn't fully complete our raid until 8:02pm.



This picture we had it set to auto launch at 7 and it missed the finalizing window by 4 minutes. This is when we first noticed it happening. Our guild reset timer is at 7:30pm. Over the course of it happening a few times and officers needing to go in and manually launch it, we went over that 7:30 threshold and lost tickets.