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