Major Flaw in the Krayt Raid

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

"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 wastingspending time on threads like this.

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.

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 ;)

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

"herd_nerfer;c-2424309" wrote:

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

VERY well said!!

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.

Yes it’ll happen once and that’s it. Unless you continue to try to have the raid end right before your guilds reset. I’ve yet to hear an important reason why it is significantly better to push for raids ending then.

"Drathuk916;c-2424345" wrote:
Yes it’ll happen once and that’s it. Unless you continue to try to have the raid end right before your guilds reset. I’ve yet to hear an important reason why it is significantly better to push for raids ending then.

That i don't know. I was just sharing the data on the pushing of the time. maybe CG will fix it but i won't hold my breath.

"scuba;c-2424340" wrote:
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.

If I'm understanding your math correctly, your guild will see this issue in a little less than 6 months - and then it will take another 72 months for it to happen again - and that's making a large assumption that your guild (or any guild) will maintain 50/50 members at all times and all 50 members will always get their 600 tickets per day - for three years straight. Now that's not impossible to do, but I doubt even the most dedicated guilds can claim that they've done that across any given span of 72 months since launch.

You're the first person to post these numbers in a way that's easy to follow and understand, so you have my sincere thanks for that. And thanks for taking the time to look into it and post your data.

To reiterate - I do think they should fix it, and it's nice to have a heads up about it. I don't think they should prioritize it ahead of other things.