{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Big Ox:
10/1/2017 2:50:30 AM
244
Guided Raid - Oathbreaker Penalty - Everyone Like to get this fixed
Five in my clan (myself included) running a Guided Raid to help a random. One member lagged out and tried to get back in immediately and got an Oathbreaker penalty... ... ...the game would not let him back in due to this.
Kind of a problem. All of us voted after to Abandon without Penalty so we could all leave and then finish the raid with the random anyways. However, we do not get any rewards as a clan or as a player for this.
There has to be a way to fix this or why would a clan risk anything negative by running any Guided Games/Nightfall/Raids.
I understand the concept behind why Bungie has this but...an accidental lag out and locked out of getting back in is wrong.
I've never asked for a like, but if you read this and could like it so it gathers some attention from Bungie to come up with a way around this. (cough...cough...a timer to get back in the game).
Ended up going back in the raid after going out to orbit with the random (Silvermain1066) and back into the raid and found out we also didn't have our checkpoint, that's shitty. We are starting the raid fresh anyways again, no big deal, we are still going to clear this for him.
Members Involved
Big Ox 83
Buster Skull
NVIED
Matt Rose 4
xhop3less
Update: I just want to thank everyone for the support, over 1200 bumps and a lot of great suggestions that I hope Bungie takes into consideration. I'm hoping Bungie will acknowledge it at least and help us all get this addressed :)
-
A timer to get back in the game is a great idea. Let's face it ANYBODY who has completed a raid has had a connection issue before
-
Exactly why I never signed up for this. Was waiting for forum feedback. I am in UK and most of players from US have lag issues with this side of pond. Bungie cannot track network due to their model ao honest problems of lag will cause issues. Was hosting a NF with my friend and the random from Germany got similar issue and beetled out. He wasn't able to join back and had to go back in queue. Bungie is swift in penalizing people this way when D1 lag manipulation was just swept under the carpet. Surely there is a better way... I hope.
-
35 RepliesWow a post with general acceptable critism in a format easy on the eyes and presented in a non whiny crybaby way. Didnt know they existed on these forums.
-
-
-
Bump ✊
-
-
Fix this shit
-
2 RepliesHow many vanguard tokens do you get for doing the nightfall?
-
-
I'll like for you.
-
2 RepliesI have been booted more in D2 than in the entirety of D1.
-
Bungie kinda sucks at the raid infrastructure. Fite meh
-
4 RepliesReported for name and shame
-
Yup bungie servers suck and the players pay the price.
-
I agree a fix is needed. It happened to me trying to do the nightfall last week and that was irritating
-
I shouldn't get a loss in trials either when I "lag out" with a 300 mb/s connection
-
Upvoted. I haven’t used Guided Games yet, but this would definitely be upsetting.
-
If raids kick you like in D1 this is a huge issue, upvote
-
1 ReplyBungie need to put a "Vote back in" function. That should also wipe any Oathbreaker score gained from the d/c.
-
reported for name and shame
-
Edited by SkinPoppeR: 9/30/2017 12:21:53 AMI don't how they could accurately tell if it's lag or someone unplugging the connection though in the end. They could however put some code in the GUI to where it logs logout keystrokes. So if someone backs out or closes the game and exits to dashboard or desktop or whatever, Destiny servers will know that much. I agree this issue should be fixed. Not just for lag. But first as it is intended. To penalize only quitting. I had a similar experience only I was the random. And the clan didn't communicate with me at all. Not in game chat or maybe not even have mics. As such the whole experience sucked. Eventually someone quit. Now I didn't get penalized but was sure thankful to know the quitter did. Wasted my entire night of gaming for that clans bad behavior.
-
We were doing a guided game and beat the gauntlet but after completing it the elevator wouldn't descend. We all decided to vote to leave and rejoin in orbit. I was the last to leave and as my screen faded to black the elevator started to move. We re-entered the raid only to find out that we had to redo the gauntlet because it was outside of the guided game so we didn't get the checkpoint.
-
But if you look up the error code (any error code because they all say exactly the same thing) after you get booted you will clearly see that the problem is on your end and not Bungie's. So why would the need to fix it? For those that don't seem to get it...this was meant to be sarcastic.
-
Personally I think they should have made it like if you had a gg ticket and joined a guided games the whole partyfinder for it would work like regular strikes and match a player up with other gg users and just remove the whole oath and penalty thing. And they could make it so there's a chance to get gg tickets from heroic events and plunder monsters. Simplicity is best, these occuring problems with guided games is because they designed it in a way that it is unnecessarilly convaluted.
-
6 RepliesHonestly this guided games feel like a missed opportunity. All it should be is an in game lfg. No need for the fancy oaths and so on. Lfg has worked since the game came out, and occasionally there are some assholes out there. That's why we have a *hopefully* active reporting system.
