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 times. It is screwing up the schedule and we've capped tickets because of it. This built in flaw has lowered our return through no fault of our own.

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

Major Flaw in the Krayt Raid | EA Forums

tvsfrink
2 years ago
"iMalevolence;c-2424038" wrote:
"herd_nerfer;c-2424034" wrote:
"iMalevolence;c-2424031" wrote:

Yeah, I know you weren't. I was just pointing out where I got my worse case. I'm also just absolutely disgusted with the other people who are because this is very clearly a problem that should be addressed.

Is it really a MAJOR FLAW though? If you rename the thread to say "minor hiccup" instead of "MAJOR FLAW" maybe people might be more inclined to agree with you.

A potential 33% loss in rewards is a MAJOR flaw.

It would be if there was no way to avoid it.
NotRealUltra
Seasoned Newcomer
2 years ago
"LordDirt;c-2423976" wrote:
Such an easy fix yet so many just ignore it. Shows how some just want to argue and not actually get a solution.

This forum isn’t to report bugs but for discussing bugs, people can agree or disagree

If iMal wants to get this resolved or addressed by CapitalGames he needs to create and submit a ticket to AnswersHQ
scuba75
New Rookie
2 years ago
"Ultra;c-2424079" wrote:
"LordDirt;c-2423976" wrote:
Such an easy fix yet so many just ignore it. Shows how some just want to argue and not actually get a solution.

This forum isn’t to report bugs but for discussing bugs, people can agree or disagree

If iMal wants to get this resolved or addressed by CapitalGames he needs to create and submit a ticket to AnswersHQ

So you say
notthatguybefor
2 years ago
Personally I don’t feel like this is a problem, my guild has it set to launch immediately and it seems to be working fine.

That being said there does appear to be a natural solution based on something already in game. Why not allow raid tickets to go above 150k, but not be increased further beyond this point. This would be akin to buying an energy refresh which takes you above the maximum allowed, so you accrue no further at that point, but where you still have the excess in your meter.
RagingMonkey057
2 years ago
"scuba;c-2424083" wrote:
"Ultra;c-2424079" wrote:
"LordDirt;c-2423976" wrote:
Such an easy fix yet so many just ignore it. Shows how some just want to argue and not actually get a solution.

This forum isn’t to report bugs but for discussing bugs, people can agree or disagree

If iMal wants to get this resolved or addressed by CapitalGames he needs to create and submit a ticket to AnswersHQ

So you say

So say we all!
M0st1yHarm1ess
New Spectator
2 years ago
"Notthatguyfrombefore;c-2424108" wrote:
Personally I don’t feel like this is a problem, my guild has it set to launch immediately and it seems to be working fine.

That being said there does appear to be a natural solution based on something already in game. Why not allow raid tickets to go above 150k, but not be increased further beyond this point. This would be akin to buying an energy refresh which takes you above the maximum allowed, so you accrue no further at that point, but where you still have the excess in your meter.

I can totally get behind any of these easy solutions even just to not have everyone ~~wasting~~spending time on threads like this.
frieste33
New Spectator
2 years ago
i'm not sure it's wasted, necessarily. is it a "why did my account get banned?" thread? no, but it was still entertaining from a certain point of view.
RagingMonkey057
2 years ago
"effbro;c-2424301" wrote:
We have the raid set to a fixed starting time and almost lost tickets today. Thanks @iMalevolence for pointing this out, it's a ridiculously easy fix that possibly costs a non negligible amount of resources.

Before the crowd cries out again: there are several good reasons for a fixed start time. I'll name just a few: continuity, pings at fixed times - officer QoL, historical reasons, mere availability of the option, personal preference, dislike of odd numbers in start time.. Before y'all come at me: I'm going to set it to auto launch tonight. Just sad it doesn't work as intended.

I really enjoy reading these kinds of threads with my morning coffee, people just not willing to acknowledge a problem... I'm sure your guilds, friends, and workplaces love you for it ;)

I think most of the people "crying out" recognize that this isn't working as intended. Many of us take exception to the idea that this is a major flaw and will have a major impact on anyone, considering that the work-around is so absurdly easy and makes no appreciable difference to anyone in any respect. Op highlighted a bug, then proceeded to use hyperbole and edge case scenarios to make it seem like a much bigger issue than it is.

Your reasons for a fixed start time all come down to personal preference and ultimately have 0 impact on guild rewards - which is fine - I'm not saying your reasons aren't valid. They are, but it's unlikely that any of them rise to the level of importance for CG to actually do anything about it. There are plenty of personal preference and QoL issues that actually do have a major impact on the game play experience (fleet loadouts for instance). For this issue to steal dev time from genuinely major issues would be really unfortunate.

It's great to have the heads up about the problem - OP wasn't wrong in bringing it here to talk about it and make it known - it's not great to blow it so far out of proportion that the community at large actually starts to believe that it's a serious problem. Not everyone is going to bother doing the math but they'll be quick to jump on the band-wagon when people start throwing shade on CG. That's damaging to the game, damaging to the community, and distracts from actual issues that need to be fixed.
scuba75
New Rookie
2 years ago
So here is some math, and if i remember I will update it later
Autolaunch is set to immediate (the "workaround" for this issue)
Guild Reset is 19:30 EDT
Raid ended Monday, May 22, 2023 5:48:52 PM EDT (1684792132 epoch)
Raid start Monday, May 22, 2023 5:50:53 PM EDT (1684792253000 epoch)

There was a push of 2 minutes
Data says the duration was 255698 seconds which is 71 hours and 98 seconds

So right now it looks like it is pushing the start time 2 mins every time, if this holds true you are looking at about Assuming 10 runs you are looking:
20 min push every month
or
1 hour push every 3 months

so my guild for instance will hit the issue in less than 6 months of the raid start pushing out past my guild reset time

I will try to give a new number when the the raid restarts today.
Knewonce
Seasoned Novice
2 years ago
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.