Major Flaw in the Krayt Raid

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.

Change it to auto launch immediately instead of a set time.

"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.

"iMalevolence;c-2423885" wrote:
, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset time.

Eventually. Let's say 10 seconds delay every run. Once it has happened to a guild once, and then their "immediate" is now after guild reset, then it will take 8640 more runs of the raid to come back around to their guild reset time. Once every 3 days makes that 71 years until it comes back around to happen to that guild again.

I think your definition of major flaw is different to mine, and I hope the devs don't waste any hours on this.

Setting to immediate is an adequate solution.

Here's my math in case I messed it up:
10 seconds delay per run slowly moving immediate launch.
24×60×60=86,400 seconds in a day.
86,400÷10= 8,640 number of runs to move immediate launch by a day with 10 second delay.
8,640×3=25,920 number of days to launch a raid that lasts 3 days 8,640 times.
25,920÷365=71 years (rounded down and not accounting for leap years).

This game has shown its got legs, but 71 years is crazy talk.

"Winterwolves;c-2423886" wrote:

"iMalevolence;c-2423885" wrote:
, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset time.

Eventually. Let's say 10 seconds delay every run. Once it has happened to a guild once, and then their "immediate" is now after guild reset, then it will take 8640 more runs of the raid to come back around to their guild reset time. Once every 3 days makes that 71 years until it comes back around to happen to that guild again.

I think your definition of major flaw is different to mine, and I hope the devs don't waste any hours on this.

Setting to immediate is an adequate solution.

Here's my math in case I messed it up:
10 seconds delay per run slowly moving immediate launch.
24×60×60=86,400 seconds in a day.
86,400÷10= 8,640 number of runs to move immediate launch by a day with 10 second delay.
8,640×3=25,920 number of days to launch a raid that lasts 3 days 8,640 times.
25,920÷365=71 years (rounded down and not accounting for leap years).

This game has shown its got legs, but 71 years is crazy talk.

My guild has lost over 15k tickets because of it because our raid launch time was right before the guild reset. Rewards are eventually being delayed after TW or GAC lock. Problems happening to just 1% of guilds is a lot of people.

"Winterwolves;c-2423886" wrote:

"iMalevolence;c-2423885" wrote:
, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset time.

Eventually. Let's say 10 seconds delay every run. Once it has happened to a guild once, and then their "immediate" is now after guild reset, then it will take 8640 more runs of the raid to come back around to their guild reset time. Once every 3 days makes that 71 years until it comes back around to happen to that guild again.

I think your definition of major flaw is different to mine, and I hope the devs don't waste any hours on this.

Setting to immediate is an adequate solution.

Here's my math in case I messed it up:
10 seconds delay per run slowly moving immediate launch.
24×60×60=86,400 seconds in a day.
86,400÷10= 8,640 number of runs to move immediate launch by a day with 10 second delay.
8,640×3=25,920 number of days to launch a raid that lasts 3 days 8,640 times.
25,920÷365=71 years (rounded down and not accounting for leap years).

This game has shown its got legs, but 71 years is crazy talk.

They don't have to waste hours to fix it. Shorten length of raid or the stupid calculation hour by 10 mins, problem solved

"iMalevolence;c-2423889" wrote:

"Winterwolves;c-2423886" wrote:

"iMalevolence;c-2423885" wrote:
, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset time.

Eventually. Let's say 10 seconds delay every run. Once it has happened to a guild once, and then their "immediate" is now after guild reset, then it will take 8640 more runs of the raid to come back around to their guild reset time. Once every 3 days makes that 71 years until it comes back around to happen to that guild again.

I think your definition of major flaw is different to mine, and I hope the devs don't waste any hours on this.

Setting to immediate is an adequate solution.

Here's my math in case I messed it up:
10 seconds delay per run slowly moving immediate launch.
24×60×60=86,400 seconds in a day.
86,400÷10= 8,640 number of runs to move immediate launch by a day with 10 second delay.
8,640×3=25,920 number of days to launch a raid that lasts 3 days 8,640 times.
25,920÷365=71 years (rounded down and not accounting for leap years).

This game has shown its got legs, but 71 years is crazy talk.

My guild has lost over 15k tickets because of it because our raid launch time was right before the guild reset. Rewards are eventually being delayed after TW or GAC lock. Problems happening to just 1% of guilds is a lot of people.

So over the 71 year period for this to happen to your guild again that's 15k÷71÷365=0.58 energy per day (across a 50 player guild, so 0.012 per player). Seems the definition of a negligible flaw to me.

Also, does having auto launch set prevent an officer from just launching it when they notice it's not going? How did you cap out? If you did, then it runs for 3 days anyway, enough time to max out tickets again anyway.

So the major flaw is that it's going to be however much later than when an officer notices it isn't running? Or a member that asks an officer?

Negligible.

"Winterwolves;c-2423893" wrote:

"iMalevolence;c-2423889" wrote:

"Winterwolves;c-2423886" wrote:

"iMalevolence;c-2423885" wrote:
, even setting it to "immediate", because each second or two over will eventually push a guild past their guild reset time.

Eventually. Let's say 10 seconds delay every run. Once it has happened to a guild once, and then their "immediate" is now after guild reset, then it will take 8640 more runs of the raid to come back around to their guild reset time. Once every 3 days makes that 71 years until it comes back around to happen to that guild again.

I think your definition of major flaw is different to mine, and I hope the devs don't waste any hours on this.

Setting to immediate is an adequate solution.

Here's my math in case I messed it up:
10 seconds delay per run slowly moving immediate launch.
24×60×60=86,400 seconds in a day.
86,400÷10= 8,640 number of runs to move immediate launch by a day with 10 second delay.
8,640×3=25,920 number of days to launch a raid that lasts 3 days 8,640 times.
25,920÷365=71 years (rounded down and not accounting for leap years).

This game has shown its got legs, but 71 years is crazy talk.

My guild has lost over 15k tickets because of it because our raid launch time was right before the guild reset. Rewards are eventually being delayed after TW or GAC lock. Problems happening to just 1% of guilds is a lot of people.

So over the 71 year period for this to happen to your guild again that's 15k÷71÷365=0.58 energy per day (across a 50 player guild, so 0.012 per player). Seems the definition of a negligible flaw to me.

Except this supposed 71 year period you keep mentioning happened within a week and a half of the raid being out. And again, this effects all guilds who were running raids just before the guild reset window. This effects every guild getting rewards pushed after TW lock and after GAC lock. This will very negatively effect guilds with less active officers who aren't noticing or catching the issue.

Quit being dismissive of something that is very clearly a design flaw that negatively impacts players and will continue to negatively impact players until it is resolved. As Scuba said, the fix for this is simple enough. Suggesting this be ignored is absurd.

/e Also, I have proof of raids missing the window by 4 minutes, so your 71 year period could be off by a factor of 24 and screwing guilds every 3 years is kind of messed up.

"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.