{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/24/2014 8:56:47 PM
7
A bug is a legit part of a game until fixed. Get over it. BTW, I don't have a warlock, I don't use this, so don't tell me to get good. Here is the original post from the OP. I can confirm it works from multiple clan mates using it.
" As a warlock sunsinger with full special and fireborn on, jump off a cliff or die however you do.
While dead and you see the "use special to revive" go into your menu and into your sunsinger subclass and switch your fireborn to another option like the cool down for allies.
Close out the menu and the prompt to revive should be gone. Use your special buttons to revive anyways without using up your special
Then switch back to fireborn while maintaining your full special bar for the next death
Enjoy for whatever reason until it hopefully gets patched."
English
-
Wow, I feel stalked o.o;; am I to be flattered or scared? Anyways they already posted a reply saying they knew about it and were looking into it (at which point everyone felt obligated to reply to them telling them to fix error codes). But yeah, enjoy the glitch til it gets patched. Warlock master race!
-
Be flattered. I scour the forums daily for useful info like you posted and I communicate it back to my clan. I saw Bungie finally acknowledged you so I decided to repost your info. Let the haters take a swing at me; ill poop on those scrubs. Next time don't let the haters scare you off. Thanks for posting positive and useful stuff on here, it is the only reason I even read these forums anymore.
-
Thanks for the feedback. I wouldn't say they scared me out of posting, more so they just got annoying because they are whiny little cry babies about everything. People are starting to catch onto the checkpoint saving between weekly resets it seems as well. So expect that one to be out soon.
-
And the nightfall cheat where you go to orbit and rejoin rather than risk your team going down to revive. LOL
-
My buddy last night said a friend left to orbit to rejoin in a weekly heroic and it kicked them to the previous checkpoint. I hope it was just a random occurrence though cause that would be evil with the state destiny servers are in with their random disconnect errors.
-
I know what you are describing. There are not checkpoints as you are thinking. Rather, each sub-area within a larger respawn restricted area has a respawn point. So, if you run towards the end of a strike then run back and die you won't spawn forward. Instead you'll spawn to the respawn point associated with the area in which you died. The condition your friend described occurred because they retreated far enough back to be in a different respawn area. The areas are often doorways, so getting killed on one side or the other can really impact where you respawn.
-
No, he said when she left it reset the other 2 left to a previous checkpoint. Not the spawn in.
