{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/18/2014 9:42:18 AM
4
I believe the crota thing could be fixed as easy as reimplementing an already existing mechanic. If someone leaves, oversoul is activated, and kneel timer is reset based on host (optimally timer would be server based but well bungie...). This keeps crota standing/ stands him back up and wouldn't allow the swordbearer to spam him because he would just hulk smash the hell out of the guy. Doesn't matter if the shield goes down or not, no way to hit him if he is still standing without taking major damage or dying. Simple, easy, and the best part is that even if it happens to a legit raid group it won't matter that much cause you can still kill the oversoul, but it prevents the exploit by keeping crota from staying down too long.
English
-
I was thinking this!! Pretty simple really if someone leaves just make crota enrage. Most of he time if someone leaves on accident or for good reason you look for another person to fill his spot anyone so putting the enrage feature in really wouldn't bother the people playing the right way.
-
Exactly. Some pseudo-enrage. Ya it may make some groups unintentionally wipe. But I would rather this than a massive raid breaking exploit followed by another mythoclast situation. Idk how easy it would be to implement but its probably easier than a lot of potential fixes and at least would slow people down until a true patch could be made.
-
Yeah I mean the only thing I could think of is not letting people leave at all during the crota part. But this would force people to either beat him or turn the xbox off if they wanted to get off while shooting crota. Of course only not let them leave after the glass breaks.
-
There's absolutely no way of doing this realistically, but you could make it so that rewards don't drop when there is a person who leaves the fireteam, and that it wouldn't count as a completion so that it could be redone legitimately to get the rewards. Again, solving one problem can potentially cause 2 more. The more code you screw with the higher chances are that more things will go wrong. Case and point with the VoG patches.
