{{
`${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 :)
-
Yep same happened to me, after I disconnected and became an "oathbreaker" my clanmates and the randoms voted to leave and we repeated from the start (outside of guided game), that way I was able to participate, we gained checkpoints and did it over a couple of sessions (recruiting a new clan member along the way). I will try it again and support the GG idea, just needs optimising in implementation to avoid punishing people providing support.
-
-
Bump for awareness, this is why the system is still in beta, to vet out problems like this.
-
Had a similar thing happen on the NF. A clan mate and I queued up and started with our GGer when his PSN ran out and he had to buy some more. He left the game then couldn't get back in so, seeing as the NF is timed we decided to wait in orbit to group back up. I then got the oathbreaker debuff. This system seems like it had minimal testing and was a poorly thought out, bandaid fix for solo players that wanted in game LFG.
-
Yep. This needs to be fixed ASAP.
-
Liked. That's BS
-
Liked, bumped. And good on you for helping them out anyway.
-
You can get bad feedback, when kicked..... Wtf
-
3 Repliescould be as simple as a timer, from the moment you lag out of a raid, you have X amount of time to rejoin.
-
-
Hope this gets more attention
-
Yeah that is sucky. Defies the whole point in GG really. Bungie need to think about this otherwise their GG system won't even be used
-
1 Reply...This... wow... Well, it does make sense, considering Bungie's servers, which, although are slightly better, and I say slightly in a fractional sense, are actual potatoes. Sorry Bungie. I tried to be positive for your servers. Disappointed... welp, back to Overwatch then.
-
How do they miss on such obvious implementations? It's very unnerving that they have zero hindsight when tackling such decisions as this. Here's hoping that feedback like this gets to the right people. I'd love to be helping guardians through activities, but I'm not committing to a broken system yet.
-
1 ReplyJust 2 man the raid. https://youtu.be/r59KUoc-_Bc
-
Bump.
-
I don't bump anymore, but I like carrying people and it would suck if this happened to one of us. So take this bump.[spoiler]bump[/spoiler]
-
This is why I haven't tried GG nor any of my clan members.
-
Bump* thats bull this needs to be addressed
