Major Flaw in the Krayt Raid

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.

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

Given the new structure where everyone can just hit whenever they want, there no longer seems to be a reason to have a set time, especially not near reset. If launch time is set to say 6 hours after reset, then after launch it is updated to immediate, the processing should no longer be an issue and any movement caused by varying processing length should not run the risk of negatively interacting with guild reset.

This feels like a random edge case affecting you specifically. First of all, rewards timing doesn't really matter anymore. You have a steady income of tokens, use them as needed or save some up for "event locks."

Second of all, this timing issue doesn't actually change the amount of raids you do in a week, so I fail to see how it's an issue at all.

"StarSon;c-2423935" wrote:
This feels like a random edge case affecting you specifically. First of all, rewards timing doesn't really matter anymore. You have a steady income of tokens, use them as needed or save some up for "event locks."

Second of all, this timing issue doesn't actually change the amount of raids you do in a week, so I fail to see how it's an issue at all.

Considering someone else also posted a thread about raids not auto launching, I can guarantee it's not just affecting me specifically. And just because you fail to see how this is an issue, it doesn't mean it isn't one. If this has impacted one guild it can, and will, impact others. I'm trying to help before it becomes a similar problem for other guilds. How about you willingly delay your raids and waste tickets? No? Then it's a problem.

"iMalevolence;c-2423964" wrote:

"StarSon;c-2423961" wrote:

"iMalevolence;c-2423946" wrote:

"StarSon;c-2423945" wrote:

"iMalevolence;c-2423940" wrote:

"StarSon;c-2423935" wrote:
This feels like a random edge case affecting you specifically. First of all, rewards timing doesn't really matter anymore. You have a steady income of tokens, use them as needed or save some up for "event locks."

Second of all, this timing issue doesn't actually change the amount of raids you do in a week, so I fail to see how it's an issue at all.

Considering someone else also posted a thread about raids not auto launching, I can guarantee it's not just affecting me specifically. And just because you fail to see how this is an issue, it doesn't mean it isn't one. If this has impacted one guild it can, and will, impact others. I'm trying to help before it becomes a similar problem for other guilds. How about you willingly delay your raids and waste tickets? No? Then it's a problem.

Explain it then. How does a 6 minute delay actually affect anything? Let's say it launches "on time" and you don't "waste tickets". Do you get to run an extra raid this month as a result? Or does your raid still launch at the end of this raid regardless?

If I have 135k tickets and the raid doesn't auto launch and I waste 15k tickets, how is that not a problem?

The raid runs for 3 days and costs 90k tickets. Coincidentally, during the 3 days the raid is running, you earn 90k tickets. So, unless you somehow start only gaining, like, 15k tickets, it won't be a problem, because a raid is always on.

If other guilds get 6 minute delays regularly and also waste tickets, is that not a problem? Those are tickets that would have granted extra wiggle room with participation, maybe it does eventually equate to an extra raid at some point.

Regardless, it's something that SHOULDN'T be happening. It's a design oversight that should be reasonably easy to rectify.

Again, how about you delay your raids by a day and waste tickets? Then keep doing that once for every guild that has the issue. And you'll finally see that a little bit of a problem for lots of people is a problem.

The 6 minute delay is meaningless for any guild that existed when the raid launched, because you will always simply have enough tickets. Whether you "waste" all 30k or 1k or you timed it differently so you launch before reset and never "waste" any. It's simply never going to be an issue for you guild because, except for those 66 minutes every 3 days, you will always have a raid going.

You are incredibly wrong and I'm not sure how I can explain it in a more simple way.

Guild start raid
Raid not finish and start exact same time, 72 hours later.
Guild raid timer pushed back
Raid timer passes daily reset and guild earns 4 days worth of tickets during a 3 day raid window
Guild has up to 30k earned tickets that get deleted from existence THROUGH NO FAULT OF THEIR OWN.
Up to 30k tickets could have been used to start a raid sooner down the line when people eventually miss 600 tickets
Guild shafted

Let's say you manually start the raid to avoid the 6 minute delay. You drop from 135k tokens to 45k tokens. You do the raid. Raid is over again. Now you're at 135k tokens. You start the raid. You're at 45k tokens. For infinity.

Let's say you miss it, and it starts "late." You hit 150k tokens. Raid starts, you're at 60k tokens. 3 days later, raid is over. Now you're at 150k tokens. You start the raid. You're at 60k tokens.

Now, obviously I can see that you have a different amount of tokens at the start and end here. But so what? In both scenarios you will immediately start the raid in perpetuity. Therefore, there is no issue here, and at best this is a minor "flaw" in however CG has this process setup.