Reece.

@yPantho @SyncroV2 @LanzaGB @AIexApe @engels_stan @Ddraig94 @grok Another kickers incident

@SyncroV2 @LanzaGB @AIexApe @engels_stan @Ddraig94 Why is Alex shorter than Lanza @grok

Having a wonderful time with the boys 😎

@pkiyox @AIexApe @Destiny2Team @DestinyTheGame You just didn't read the tweet hahahahaha

@AIexApe @Destiny2Team @DestinyTheGame You do realise that all teams had the same experience with the glitches right.

.@Destiny2Team @DestinyTheGame really think The Desert Perpetual needs to be released on contest again. There were far too many bugs, almost too many to name - we had weapon bugs affecting multiple guns (Tlord, LoW etc), the slow bug affectively killing runs, rally banner bug, immortal eye bug for the hydra, the portals not working properly for damage extension on hobgoblin. These are just the ones I can name from the top of my head. For the first time that I can remember the World's First Race was DIRECTLY affected by this, due to ANOTHER mechanical bug on the final boss stopping @Tyraxe and his team being able to clear, which I'm sure everyone at bungie is just as annoyed about. This bug was so impactful due to other teams not getting it at all, resulting in the playing field most certainly not being fair. This sucks to see not just from a player's perspective, but also a viewer's one as well. There were more bugs that seemed to miss out on other teams as well, for example my own team had a bug in the boss damage arena where the poles/buffs would spawn in irregular places making it almost impossible to start damage unless we somehow guess our way through the mechanic. I have asked around, speaking to many teams that have cleared the raid - only one other team to my knowledge had even heard of this bug. Again, making the playing field not fair. You did a really good job with this raid bugs aside, having 4 boss encounters that were all uniquely difficult made this a very fun and challenging experience. What I'm trying to say is that ALOT of time was wasted for many teams, and it was completely out of their control. It would be a shame to have to look back at the edge of fate in a year's time and having nothing to say but "oh it was incredibly buggy" and that "the raid race meant nothing". You've extended the contest time for SD and VoTD before, and I think it should done for The Desert Perpetual because of the before mentioned reasons. Thanks for reading xx

@ItsDinok @AIexApe @Destiny2Team @DestinyTheGame I'm just speechless that they didn't delay it a couple weeks to try and fix through as much as they could, rather than forcing it out so soon. The issues created a completely unfair experience.

@AIexApe @Destiny2Team @DestinyTheGame I am torn on this. One the one hand people certainly don't have the emblem because of bugs. On the other hand it devalues the emblems for people who got them

@722Bird @AIexApe @Destiny2Team @DestinyTheGame was strange for us. Just fixed itself out of nowhere, such a ridiculous time waste tho.

@ReeceRTS @AIexApe @Destiny2Team @DestinyTheGame We reinstalled, and rebooted, and it still happened. We just happened to notice it always occurred whenever it was a perfect run. So we started doing the 2-2-1-1 method and it never happened again lol.

@722Bird @AIexApe @Destiny2Team @DestinyTheGame We didn't always dunk 2-2-2. It just stopped after multiple instance resets and host changes. Took away 2 hours in total 🤠

@AIexApe @Destiny2Team @DestinyTheGame We encountered the same bug you encountered. We did find a foolproof workaround though. Whenever we dunked all 6 buffs 2 at a time, it occurred. Whenever we messed up and had a rotation where only 1 person was able to dunk the buff, we did not get the bug. So we dunked 2,2,1,1.

@D2Nuke @Destiny2Team my team did 979,982, no clear. I guess it all comes down to final stand, but I guess this level of difference could impact final quite alot. Has to be a visual issue surely?

@MavisD2_ @AIexApe @Destiny2Team @DestinyTheGame They just want to gatekeep the emblem. I would be doing the exact same hahaha.

@AIexApe @Destiny2Team @DestinyTheGame The replies under this post are Just showing how retarded this community really is, everything you said Is valid and giving another 24 hours of contest would only bring benefits

@SoDeceptive @niksurs @AIexApe The joystick operator

@niksurs @AIexApe @ReeceRTS look who it is

what did i do to these poor fellas to deserve this😭

@xCaaa__ @mazokvmo @kerbos76 @Destiny2Team @A_dmg04 in which case it was justified.

@mazokvmo @kerbos76 @Destiny2Team @A_dmg04 And it was retard

ws ban evasion deceptive... or are you recoving? either way both against ToS @Destiny2Team @A_dmg04

@SoDeceptive I've just watched him lose every single penny in 15 minutes.

PART 2

@SoDeceptive This is a Nigel approved message

Almost got dark matter 💯 been running the qs up with MuslimDave53 who is a 0.001 K/D, im helping him get better at the game everyday!

@47romar Bang out of order that mate

well well well… 🦍

@iSilence07 @SurreyTrader21 Hahahaha

@SurreyTrader21 @ReeceRTS

HSTIKKYTOKKY AND GENERAL G CRASH MCLAREN

@LostFxwn @ZizuSwift @ZizuSwift is this that girl you told me you caught feelings for over twitter?

@ZizuSwift @SnakeOsaurus

@ZizuSwift get on bo3 #rapetrain

@SoDeceptive @ZizuSwift @LostFxwn @Scare_51 @2Cramz @Atuvi6 @Jqkick 🏳️‍⚧️

@ZizuSwift @LostFxwn @ReeceRTS @Scare_51 @2Cramz @Atuvi6 @Jqkick

@ZizuSwift @MolliexMackay @Scare_51 @SoDeceptive I knew you were faking it the whole time, you love willy Jacksonville.

@iSilence07 @LanzaGB @Bungie Took the words out of my mouth Finerald.

@LanzaGB @Bungie Why have you resurrected this Fede? Lmaooo

BattleEye's already working lads. Great stuff @Bungie 👍

@SoDeceptive - Get Cancer

Step by Step guide on how to be Deceptive - Always be naked - Wear a durag - 0 filter Voice lines: - Unreal - 50 cal - Get shot - Tree