CC no auto boot out at end.. and no shards given.. sucks

[Grace_ana]

Breathe. It really wasn't a huge deal; we just picked up barrels and it worked okay. Would be nice if it was fixed, but if anyone else has that issue, try the barrels.

[Sikita]

Happened to me as-well. It was me that had a DC and when i came back the bug OP mentioned occured.

[smatt]

Two issues were previously mentioned above. I just chose the closest post to respond to.

(shame on me. I'll go harvest hundreds of crystals for my transgression of laziness.)

You should be sentenced to 12 hours straight of Kobold Assault!

(No Dev buttons)

[Wutinni]

Same thing happened in our run

[Calebro]

This happened to my group earlier as well. Kind of.
The notification for receiving the green dragonshards occurs when you get kicked out, but you actually receive them upon completion, as opposed to receiving them when you get booted out. Even if you don't get a notification for it, you get them.
I know this because when it happened to us, one of our guildies in the group was only on his second run in the Cove, and he had a total of what we would have received from both rather than just the first run.

So despair not. You got your dragonshards. All you didn't get was the notification and the auto-boot from the instance.
At least that's what happened for us anyway.

[Produktion_Malphunktion]

And please check your ingredients bag. I thought I had a repro, but they were auto gathered into the crafting ingredients bag--

[mystafyi]

And please check your ingredients bag. I thought I had a repro, but they were auto gathered into the crafting ingredients bag--

reproduce with a member of the group lagging, or about to dc. since ya'll test on a dev-box with a 1ms latency 100Mb/sec data throughput you wont reliably be able to reproduce.

[Produktion_Malphunktion]

reproduce with a member of the group lagging, or about to dc. since ya'll test on a dev-box with a 1ms latency 100Mb/sec data throughput you wont reliably be able to reproduce.

We have that part, but people without a decon event is what I'm curious about, and we do not test on a 'dev box' in QA that would just be...wrong.

[Palantyr]

Had this happen today. One player disconnected while the quest was going, twice actually. The first time the kobolds stopped moving while he was dc'ing. The second was close to end and he reconnected with less than a minute left in quest, I didn't notice kobolds not responding that time but I wasn't close to any either. We got the completion for quest but did not auto-exit and no one in group received any shards, perhaps because he hadn't fully loaded in yet?

[Calebro]

I'm fairly certain we had no decon during the incident with my group. My group only had one decon during the event. It was earlier in the evening, and it didn't affect the instance at all.

[mystafyi]

and we do not test on a 'dev box' in QA that would just be...wrong.

LOL you crack me up.... I know you wanted to say something other then "wrong".
your the best thing to happen to Turbine QA in .... years

[aradelothion]

Same thing happened to us; we didn't realize that something was wrong as it was our first time in, but upon completion we didn't get booted, no shards either.

EDIT: There were no disconnections, or anything else that was weird. Kobolds were active, we just didn't get any shards.

[Chette]

Same thing just happened to me.

With about a minute left we had a major lag spike and the kobolds went crazy. The quest completed, but didn't give us any crystals or XP. I DCed and when I reconnected we were still in the cove, but not crystals or XP.

Submitted a ticket. Got the following response.

The issue you have described is either not a currently known issue that the In-Game Support team can assist with, or cannot be resolved with the information you have provided. We recommend that you take a moment to submit a formal bug report at this url: http://forums.ddo.com/new_bug.php?. Be sure to fully review the information at the top of the bug report form to understand how bug reports are handled.

[Delwyn_Stone]

A similar thing happened to us a bit ago.

My wife's computer crashed with about 2 minutes to go in the quest. (Her computer crashes relatively frequently.) The timer ran out and we did not get the notification of the dragonshards, nor did we get booted from the quest.

After about another minute or two, the rest of the party got the notification that she had disconnected. Right after that we got spammed with hundreds of lines of Kobold chatter, and several hobgoblins spawned and started attacking.

It did look like the scripting in some way paused or froze while she was "disconnecting".

We eventually recalled and definitely did not get any shards for that run. I checked all bags, etc.

[DrenglisEU]

Oooooboy..... (Doom time) seems that CC will go shut again. I honestly think that the drop rate of shards should be increased since with this speed we will have CC coming and going for the rest of the year. I just need my 900+ shards and I'm a done deal with CC. Want to get back to normal raiding and keeping guild favor rising.

Get the bl**dy CC to work.... you did it last time after small adjustments.

[Ascendius]

This just happened to the group I was leading. We were running at level 25 and got the full crystal bonus.

The game hiccuped (around 4am eastern time as usual) and one of our members disconnected. That same team member then reconnected the very second before the quest finished, however; they did not respond for several seconds after the finish due to loading. The quest completed and our experience report stated 100% crystal bonus. We did not get forced out of the quest, and we did not receive our crystals. We submitted a ticket and made sure no one left the quest. After ten minutes, a GM responded that they were not aware of the issue and can't help us.

Don't GMs have the power to force a finish of a quest? Our quest log and experience report was hard proof that we were running at level 25 and had 100% crystal bonus. I find that very unfair.

If GMs cannot help us in this matter, then I will have to kick members if they disconnect close to finishing time in order to make sure at least some members receive crystal rewards.

I did submit a bug report.

[Yvonnel-1]

we need WHIPS !!!!!!!!!

[bvermeul]

Two issues were previously mentioned above. I just chose the closest post to respond to.

(shame on me. I'll go harvest hundreds of crystals for my transgression of laziness.)

Feel free to deposit the hundreds of crystals in my inventory. I wouldn't want you to have to lug them around when I can do that for you. I'll keep them safe for you, honestly.

[Voldomar]

Got to the end. We collected 254. Quest window said completed. Waited.. waited.. waited...

No shards given. Not auto-booted out of quest.

Eventually recalled.. no warning about not complete.

Didn't get any shards.

Nice bug.

Same here. Quest window said completed, no shards, mobs kept spawning
One party member nearly lost connnection right before the time ended. We weren't booted and didn't get any shard

[7-day_Trial_Monkey]

It does seem that barrels are the cause of frozen kobolds. I had a group of them standing on the ramp for no apparent reason. Then I noticed a barrel that was hanging in the air, just under the upper part of the ramp.

I was able to grab it and the kobolds went back to work right away.

It seems that if they detect a barrel nearby, but can't calculate a path to it, they freeze.



I had no repeat of the crystal issue. I ran the cove 12 times total and only had the problem once. Since it was my second run, I am certain that it was not just a display issue. I knew how many crystals I had from the 1st run and that's all I had after the bugged ending to the 2nd run.

Before starting the 1st run I turned off auto-gather on my bag as I find it easier to keep all the cove stuff on a page in my pack. And there's still no cove items in my pack now at the end of 12 runs.