It’s Friday and you’ve had the most difficult week of work! All you can think about is loading up @GhostRecon #Breakpoint and playing some PvP to tame the beast! You get in the PvP lobby and hit search.... 1 minute, 2 minutes, 3 minutes go by with no games found. (1/10)

Finally at 12 long minutes of searching you find a game and you’re excited to have a chance to release your pent up aggression on some other players. Lets go! You load into the match, btw it only took an additional 2 minutes to load after finding the match, (2/11)
and find out your teammates are 17/18 kilometers off map? Invisible! What? How!? You also find out this has been going on since June 2020 and it’s February 2021. You saw, on another forum, (3/11)
you need to take steps to go to the @Xbox home screen and return to the Game at the very beginning of the match to “fix” this issue but you didn't do it in time. Now you’re running the match and you get killed by someone right in front of you but you can’t see them! (4/11)
Where are they? On that’s right! They’re invisible because the opposite team was also 17 kilometers away making their players invisible too! All because you couldn’t take some awkward, unwarranted steps, to try and correct the buggy game, you’re just losing the matches. (5/11)
You press on anyways! While loading into another match you choose a preset but because it’s bugged out too the perks are gone, you’re missing a rifle and now you’re in a match with half a setup, what was the point of a preset if it’s erased when you select the damn thing? (6/11)
Oh well you push forward and when the match loads you’ve unsuccessfully taken steps trying to eliminate the bugs and yet it fails and you die... again and again to an invisible player! (7/11)
Oh the frustrations but you’re a Ghost Recon PvP fan so you press forward and all of a sudden boom you’re injured so you use one of the syringes picked up and it fails getting stuck in your arm while you get waxed by... wait for it... an actual player. Lesson learned... (8/11)
delete the game... start a Twitter war against @Ubisoft and @GhostRecon for being criminals selling such an unfinished product. How can something be 1.5 years old and still be in an alpha state not even ready for a public test? (9/11)
#WarOnUbi #NotWhatWasPromised #NotEvenBeta #Wildlands2 #Crooks #Brokepoint #GhostFakeCon #ghostreCON (10/11)
@threadreaderapp unroll
@UbisoftSupport @Ubisoft https://t.co/fHifQA0N47

More from Gaming

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.