Yeah, sort of. I'm annoyed that your "corrections" don't actually correct anything I said, and that your "facts" are links that are basically marketing material that are at best tangentially related to the post you were "correcting." My post was primarily about the general pressure devs face in the game industry, and how if your for profit software project fails to build the parts needed for actually generating profit, it tends to kill further development. If you want to correct me with an actual correction, post something that shows that GSF monetization per player is equal to or greater than that in the ground game, or that GSF participation in 2.x and 3.x was so low that even with monetization rates similar to the ground game in terms of income/player hour or income/players active in game mode per month the audience for it was too small to earn back what was being spent on it. That's information that would to some degree refute that claim that failure to build an effective monetization system into GSF was a major contributor to the end of its development. Just because YOU really wanted more of a JTL type experience and were advocating hard for it, doesn't make anything in my post incorrect. If you want to back your opinion up with facts, then go get facts that actually back it up. To be honest, if you manage to do that I would genuinely love to see it. I like insights into the development, design and production of products I like, probably because I'm a terminally incurable nerd. So if you find such insights, please share. Just don't expect me to accept marketing teasers as insights. One of the sad things about Bioware was how the institutional culture was dead set against sharing any information with the customers if it didn't absolutely have to be shared, unless it could be protected with an NDA. So I realize that asking you to back up with relevant facts may be impossible for you to achieve, and it's kinda unfair. But if you want to play the "Calling out your opinion with my facts," game please bring facts that are up to snuff.

Your official links are almost entirely devoid of meaningful content with respect to details of the development constraints. Yes, I read them in their entirety, even going to the trouble of figuring out the url of the one you mis-linked, which was the only one that mentioned development constraints at all. From that post we can infer something along the lines of: "JTL, Elite Dangerous, EVE, type sandbox games are too big and too hard, and would break the heck out of the game engine, but at least some people (maybe even a lot) have been asking about X-wing, and we think we can do a miniature simplified version of that, so that's what it's going to be." That's about all we can infer from the posts, since they're pretty vague and mostly serve as teasers for the Galactic Starfighter patches that were coming up. When a developer flat out directly tells you that they can't change something that both the players and devs agree would be a good idea because the guy who knows how to code that isn't allowed to take time away from higher priority projects, then inference isn't really needed. I could probably get away with ignoring the NDA at this point, but I'll keep it general enough to be in bounds anyway: When asking "This would be a great change, why can't you do it," the answer was almost always a variant of "not enough time." The engine's unsuitability basically makes all GSF content a clever workaround, and clever workarounds are labor intensive with expensive skilled labor. If they didn't have to fight the engine to make GSF happen, a lot more GSF development would happen. Having had a tiny glimpse of some of the things the devs were pretty sure that they could do from the list of cool stuff, "if we had time," I can tell you that the sad face is not sad enough. It needs ten or twelve sad-face friends. If that hypothetical GSF expansion hit then they could be a crowd of happy faces.

I mean, I was around during 1.x and 2.x, and I was one of the people asking for a better space experience than the ship class on rails stuff. In the threads I was in, X-wing lite was requested more often than JTL lite by a vast margin. JTL wasn't absent, but it usually came up in the context of having SWTOR endgame in general be a bit more of a sandbox once you got to endgame and ran out of story, or in terms of having more than just pure combat in the space experience. Maybe we were just reading different groups of threads at the time though. It's not like a GSF forum section existed at that point to concentrate space flight/exploration/combat wishlist threads in one place. From the design choices though, GSF is much more X-wing lite than JTL lite, so whatever the total balance of player requests was, X-wing lite seems to have won out in terms of design choices. That said, GSF is really only about 30-40% X-wing lite in terms of its design, and very much it's own peculiar little beast in the end. Engine limitations played a role, but also probably the devs' desire to put their own stamp on it and many choices that make it more accessible as a MMORPG minigame than a purist mini-X Wing mode would have been. Your references are all well and good, but they have very little content about the practical limitations on scope of developer intent. They're a very broad strokes sketch of GSF design and player progression in GSF that can be paraphrased as: "It's going to have to be a PvP mini-game due to limited scope and trends in player feature requests. No, it's not pay to win. Yes, F2P players will have access to it. Thank you for reading." Also both links are to the same post, but I can delete an i from ii and hit enter in a search bar, so yeah, I read both of the ones you meant to link. As far as the differences between "What we meant to build," and "What we were allowed the time and payroll to build," if you know a bit about software development, the tea leaves are not hard to read. How much well designed monetization is there in GSF? Not much. How much well designed tutorial is there in GSF? Not much. Was there tutorial material well within the scope of the sort of AI/script limits constraining GSF in one of the games that the designers clearly drew inspiration from? Yes, something like a hundred or so progressively harder levels worth of design template to draw on. Are there parts of the game that were mentioned in assorted developer posts or that exist as unfinished bits that can be seen in datamining (stealth ships say hi)? Yes. Also having been involved in some closed beta testing for GSF, I have the benefit of having read and participated in closed PTS forum posts with a dev who was explaining to testers what the scope of potential changes to GSF were, and why some of the limits were what they were. Some of it was engine limitations, but the primary limit was available developer time. The devs, at least the ones that worked on GSF, thought that GSF was pretty darn cool. They didn't leave bits unfinished because they were bored of working on GSF, but because they were told that they had to work on other more important (which in business speak means more profitable) stuff. Honestly, that thread was probably the best dev-player interaction I ever saw relating to SWTOR. There was shared passion for the project from both sides, and a really deep honesty about why things on the "we all wish it could be this way" list were not able to be done on their end. It was very different from defensive corporate-speak we usually see in official posts. Can't say about post 6.0, but from 2.0 through the end of 5.x I can confidently say that "Devs don't care about GSF" was not an issue. The programmers, artists, and designers were working on making a really awesome gameplay experience for a space combat mini-game. They focused hard on that, and they made a lot of progress and did pretty good work until their bosses told them to stop and do other stuff instead. Some of GSF's problems though, stem from neglect of aspects that don't fall directly into the gameplay category of game development. The monetization for GSF is basically: pay to mildly speed up gearing, pay for cosmetics that can't be flaunted in front of other players, pay for a few ships that are almost never available on the Cartel Market. It's poorly designed in terms of why SWTOR players tend to spend money on cosmetics, and it caps out after a fairly small number of purchases relative to the infinite CM cosmetic gear treadmill in the ground game. The beauty to players of the relatively short and easy to finish GSF gear grind is an Achilles heel for the GSF monetization scheme, when you're done you're done, and there's nothing left to spend on. It's more checking off a "has monetization" checkbox rather than a well thought out "how to make GSF have a self sustaining income stream." If monetization had gotten the same depth of thought and care in design as the gameplay, it might have earned enough to be worth some continued development. If I as a GSF enthusiast want to take my Clarion with 4 engines worth of pink-purple engine and flaunt it on fleet in a way that makes other players think, "Wow, I don't know what that is but I know that I want to spend however many cartel coins it takes so that I can have it too," there's no way for me to do that. GSF is excluded from what has been SWTOR's primary monetization driver pretty much since SWTOR went F2P. If that doesn't count as a design mistake, then I'm not sure what does. Especially when you consider that the devs already knew they were transitioning to a F2P cosmetics shop based revenue stream at that point. Tutorial levels with static or easy to code moving AI targets/opponents were another missed opportunity. If you're drawing from the X-wing game design anyways, you make a map, set a bunch of coordinates for target nodes, and each tutorial level is actually the same map but the number of nodes populated by targets increases with each level and the type of target may change to a more difficult/dangerous target. Fly through waypoints (recycled TDM powerups work), learn to use cover approaching targets, learn to use engine maneuvers against targets that fire missiles, learn about range and accuracy, it's all doable with existing assets (turrets and drones) or minor modifications of them and good map design. Technical limitations are not the reason GSF's tutorial is woefully inadequate, it's lack of time to design and build the right map with existing assets. Track the stats that the game tracks anyway, hits, kills, damage, etc. and it becomes easy to have a "personal best" and also to have leaderboards or performance-gated cosmetic rewards by which e-p##$ can be compared, which seems to drive engagement pretty reliably in MMOs. This all a "What might have been" conversation. It's true that there would still have been a chance of stranded development effort, but from a overall game design standpoint GSF might have been better served by starting with Battlescout TDM matches only, a highly functional infinite CM cosmetics treadmill for flaunting GSF swag in front of other players, and a scalable tutorial map with personal best records and a public high score leaderboard. The rest of GSF as we know it following on in stages. The point being that if you onboard and retain players well and convince them to pay money for that experience, then higher-ups are more likely to say "Yes" if you as a developer ask, "hey, can we spend some more time working on this part of the game?" Ultimately, that's what drives decisions in a for profit studio. The fault here I think might mostly lie with the higher-ups. It should have been their job to make sure that recruitment, retention, and income were given adequate attention in terms of design, and those are clearly areas that didn't get adequate attention, thus dooming any significantly large future GSF development. It's possible that both GSF enthusiasts and devs wildly overestimated the appeal of space battles, and that GSF as a whole was doomed to be a development mistake. A complete well designed mini-game can still be a failure if there just isn't the audience to generate sustainable revenue. That said, I think that paying enough attention to the features other than gameplay would have increased the chances of GSF not being an overall development failure. It's cool, and I love it, but GSF does not do the core task of a commercial computer game very well (earn money), and in my view there's a strong chance that the incomplete features that should have been there have a lot to do with that. Note: The devs' approach of building a core working game mode first, and then planning to build recruitment, retention, and monetization parts around that later is not necessarily a bad choice. For that to work though, you need to know that there are the resources and commitment to build those parts when "later" arrives. If not you should either scale back some components of the gameplay so that you have the time to build parts needed for sustainable future development, or make the painful decision to cancel the project as not currently viable. Ideally you make these choices and commit to them very early in the development cycle. GSF effectively is a cancelled development project, and it was cancelled a long time ago. Is it great that it got so close to gameplay complete before getting cancelled, or is it sad that overemphasizing gameplay at the expense of other aspects created problems that likely forced the cancellation of GSF? I'd say both. It ends up as a very niche game that's quite fun and engaging for players who fit that niche, and an instructive cautionary tale in some of the pitfalls you can run into during game development. At this point in SWTOR's overall design life and population curve, there's very little chance it will ever be anything more. It's too late to find out if any of the promising fixes would have done any good (from the devs' perspective, players would still benefit from for example a better tutorial, but there's no way a tutorial could pay for itself at this point even if it caused the retention of every new player trying GSF). It is what it is. Enjoy it until the queues die, the servers shut down, or you get bored of it. I mean, we can all hope that both the developers and executives at Broadsword go completely insane for a brief period during which they embark on a major GSF development binge, but realistically I think we're in a world where fixing the scoreboard enough to display medals correctly again counts as a stretch goal.

Just going to point out that bringing people in, and doing it so well that those people are willing to pay for the product, is LITERALLY the core mission of the employees at a game development studio. There are lots of things devs can do, but bringing people in is the only thing they have to do if they want to continue being game developers as a paid career. Of course, an individual employee might have a somewhat indirect effect on bringing players in, but if they don't contribute in some fashion the person doing staff planning should probably be asking themselves, "Why haven't we reassigned them to do something useful or fired them?" There are places to learn the mechanics, but unfortunately they're mostly not in SWTOR. GSF is a Frankenstein of MMORPG with classic RPG numerical combat rules that trace roots directly back to tabletop role playing games (roll to hit, etc.), an arcade style "flight model", and a very First Person Shooter gunnery UI. So basically you need proficiency in three very different genres of games, and then need to figure out how to integrate those proficiencies in GSF's specific blend, in a high pressure very fast paced game. It's not too bad if you happen to have solid experience in those genres especially games from the '90s and early aughts that the devs drew inspiration from, but if you're missing even one leg of the tripod it becomes brutal. There's no wading pool to learn in (the tutorial is pretty worthless) and beginner learning is slow, and slow in GSF is a recipe for fiery doom. GSF is an unfinished product. Players in 2.0 were asking for a "space combat" element that was better then the on rails class ship missions, with "something like the Lucasarts X-wing series" being really high on the wish list. The studio basically said "ok" and set out a budget and schedule for space combat. It wasn't enough to get the job done. Development ended with the combat system pretty badly imbalanced, an entire planned ship type missing, and basically no work on effectively monetizing GSF. It was pretty well received overall, but with no income being generated from it because monetization had been neglected, there was no justification for completing things like a worthwhile tutorial or the stealth ship class. So because the devs neglected doing a good job of making an on-ramp for paying customers for GSF in favor of just making something that's fun to play once you get the hang of playing it, GSF became permanently crippled because the thing that would have allowed for continued development was the part of GSF that was most badly neglected. As a playable game mode it's maybe 90% to 95% complete, but for monetization to justify further investment and new player experience/introduction it's maybe 10% to 15% complete. Disappointing that that's where it got stuck, but probably a good example of how "cool and fun to play once you've mastered it" are not enough to make a successful game mode. The boring and money grubbing parts are also important.

My suspicion is that it's an artifact of the start of the GSF development process basically consisting of opening the Warzone code and going Ctrl-C, opening a new file, and hitting Ctrl-V. I'm pretty sure that at some point there was supposed to have been a housecleaning of legacy PvP code effects on GSF, but it's easy to miss stuff. Haven't tested recently, but in the past certain DoT damage effects on a character would transfer to your ship if you accepted the match before the DoT was cleansed or expired. I once died very quickly in a match because I was doing the Pub side Heroic on Balmorra where you collect droid intel in the toxic sludge, and the DoT from the sludge kept ticking on my ship when I spawned in. It's not much on a character, but on a ship hull it's pretty rapidly fatal due to the small health pools. Honestly, our characters should probably all get wireless controllers, don spacesuits, and get out in front of the ships to intercept incoming damage. After all, if you and your spacesuit can soak up a few hundred thousand points of damage, why aren't you protecting the ship with it's paltry 2.5 to 4 k combined health pool instead of hiding behind the ship's shields? Spec as a tank, grab ten medpacs, slap Guard on your ship, and get out in front of it with a jetpack, and there you have it: an invincible* GSF ship safely hiding behind its pilot. *Offer not valid if your ship gets within 0 to 35 meters of another pilot and is one-shot by their class basic attack.

What engine ability and what upgrade level? Upgraded Power Dive for example should be free, and unless there's a lockout affecting you from Slicing or EMP should always work regardless of engine pool. Barrel Roll with no upgrades on the other hand is pretty power hungry, and it's easy even for an experienced player to get a bit low on engine pool try to Barrel Roll and then be unpleasantly surprised when it doesn't work. Though personally my favorite Barrel Roll error is forgetting that the Pike despite being shaped much like a Starguard does not have Retro Boosters and being very surprised when hitting the missile break catapults me forward into terrrain instead of catapulting me backward into terrain. Oh, BTW @Hefaiston, popping in here to ask questions and find out what's going on in a GSF match instead of automatically assuming it's hacks already puts you way ahead of a lot of GSF players. Keep learning and pretty quickly you should be a terror in the skies of SWTOR.

You forgot: 4) Lockdown crew skill. Drains 40 engine power, range 5 km, base CD 45 sec but possibly affected by Alacrity equipment on character. Hangar UI implies it is, but hangar UI is not always entirely trustworthy. Alacrity probably shouldn't affect GSF, but it's always possible that it slipped through (obviously it did in the UI, but not sure about actual matches). Note, given the scale of max alacrity gains, not sure an absurd alacrity gear set for about a 5 sec cooldown on Lockdown would be really worth it in any case.

There are multiple reasons people self destruct. There are multiple reasons that people chain self destruct many times in a single match. However, for the specific reason that you like to go on about at great length: people thinking that self destructing is a more time efficient way of getting non-GSF rewards from GSF than learning to play and winning, decreasing the peak respawn rate so that SDing is very obviously no longer time efficient literally removes the entire foundational premise of SDing to accelerate matches. I question the premise that switching to a medals based reward system would improve much. Not that I object to medals based rewards mind you, but these are already people not willing to put any effort into achieving victories in GSF. If you gate rewards behind effort in GSF more effectively, the likely outcome is that they decide that the Return On Investment is no longer worth the time spent, and they just shift to whatever the next best rewards/time activity is. Not sure anyone will be sad to see them go, but in terms of solutions for self destructors, vote kicks, respawn timers, and medal based rewards all ultimately use the same method of "solving" SDs. Driving those players just in it for low effort loot out of participating in GSF. If you wanted to change their minds about putting effort into GSF, you'd probably need: A high quality single player PvE series of tutorial missions for GSF. Otherwise the learning curve is just too brutal for most players. Hybrid maps that allow a mix of PvP and PvE goals so they can earn rewards beating up low challenge scripted objectives. Exhaust ports don't break your torpedo lock or shoot back after all. Vastly improved matchmaking that takes into account indicators of skill like: Average kills, Average damage, Average accuracy, K:D ratio, a grouping factor, and that actually double checks for horribly skewed teams before starting a match and rebalances the teams if they are. All of which would take considerable skill and effort, and are therefore unlikely to ever happen. If self destructs are taken on by the devs it's not so much a matter of whether they try to drive SDers out of GSF but how. The good solutions realistically aren't on the table, so it's a matter of picking which bad solution you want. Timer is relatively easy coding as far as the options go, and if the values are set correctly on the respawn delay a timer should be highly effective. So it's probably a "best" bad solution, or possibly second best after the, "do nothing," solution, from the dev perspective.

I figure that clusters of 3 to 4 deaths shouldn't be punished harshly, and that a good faith noob might easily die 6 to 8 times during a match. I didn't do any tuning on the math figuring a max of a 15 min match, but in that sort of tuning I'd probably look to not make getting nine plus deaths impossible, but to make it so that by death five or six you're spending some time twiddling your thumbs waiting for the respawn counter, if all five or six deaths are closely stacked on the timeline. One free death and then one additional un-penalized death every three minutes already puts you at up to 5 deaths with no consequences at all if you spread them evenly through the match. Depending on your rate of stacking the penalty, that means that 7, 8, or even 9 deaths may be fairly tolerable. Of course, you could also do non-linear penalty stacking along the lines of .25 min, .5 min, 1 min, 2 min, 4 min. You could also make the test condition be recent_deaths - 2, or recent deaths - 3, which gives the player more leeway on clusters of deaths before penalties start being implemented. So your counter is accumulating deaths, but it doesn't do anything about deaths until you've reached a threshold of deaths so quickly that the decrement hasn't had time to lower the counter. I mean, I feel like 6 or 7 deaths is something that an ace can carry to a win, provided it's just one or two people, it's the stacks of multiple double digit deaths from people who are faceplanting into the cap ship on spawn that really grate. So an equation that catches max rate deaths, but isn't that fussy about high average deaths seems like the best approach. Interaction with the non-participation timer is a valid concern, but really, spawn waits probably shouldn't count against that in any case, and as long as you're tweaking timers you might as well verify that spawn time isn't getting counted as non-participation while you're at it.

A more aggressive kick isn't the only way to do it. A stacking respawn time increase would do it. You die, and it increments a died_recently flag by +1 from a default value of 0. Every three minutes died_recently is decremented by -1 until it reaches 0 again. For each respawn you look at died recently, and evaluate died_recently - 1, then multiply that by a time delay say one minute, that then gets added to your respawn timer. So two freebee deaths, and then a ramping respawn delay that abates if you stay alive for a few minutes. Set the delay value as you please to rate limit self destructs without being too harsh on new players dying through sheer inexperience. Given how hard it is get people to focus on vote kicking a bad actor during a match, an automated rate limit may be a more viable approach. I think that's what ultimately drove the decision to have auto-kick for non-participation be implemented.

Those medals already exist and are properly awarded. The scoreboard doesn't show medals, and the legacy achievements don't do a great job of explaining medals, but the medals system works fine and registers almost all easily measurable aspects of good GSF play. I'll also point out that there is no factor that influences match outcomes more than skilled play. Throwing games just guarantees that you will likely have to play 1.5 to 2 times as many games to finish the daily and weekly, and SDs don't accelerate game outcomes enough to overcome that penalty in most cases, even in TDMs. From an optimization standpoint you're better off just finding a quiet asteroid to chill out near, and either dropping a healing beacon, or taking the occasional potshot at strays with a gunship. When the non-participation timer chimes in, charge into the fray and lob a torpedo, if it hits, run back to you spot, if not just plink at things until you hit or get shot down. Minimum effort, no real skill required, you don't piss other players off, and there's a reasonable chance that the rest of your team might be able to carry you to victory. It's win-win.

Most of the builds are pretty good, but I'm going to argue against charged plating and deflection armor, especially for beginners. Armor piercing is practically everywhere in the current state of game balance. Charged plating is basically signing up to equip "extra vulnerability to AP builds." There are a handful of niche applications for it still, but they're uncommon and based on fairly high player skill. For a new player at present, equipping CP is basically just asking to die quicker and more often. The reason being, that if you make a list of the deadliest weapons in GSF right now, almost everything except Light Laser Cannons has armor piercing, which means that against them Charge Plating provides 0 benefit, and comes with some penalties retained from when the distribution of Armor Piercing was significantly different than it is now. For the T3 bomber, Directional Shields beats Charged Plating by a huge margin in terms of suitability for the build, it's not even close. If worried about getting shields facing the wrong direction in the heat of battle, just don't press the button. Directionals, just sittting there, are still better than active CP use. For the minelayer, there's not really a great substitute, but Shield Projector, Reinforced Armor and Large Reactor at least let you scrape by without seriously penalizing your survival chances. Yes, it sucks that Shield Projector more or less cancels out Large Reactor, but effectively giving up shield regen, or giving all enemies a free 23% shield piercing on you and coupling that with damage reduction that doesn't work against most of that piercing damage are both worse than a wasted reactor component. It's a ship that could use some love from the developers on defenses. There are other places I'd probably recommend different choices, but none that make enough of a difference to felt performance for a beginner to meaningfully notice. Practice and learning how game mechanics like range, accuracy, evasion, tracking penalty, line of sight, etc are more important than getting the last few percent of performance out of your component choices at that stage.

SF is my home server, and the premades there don't worry me. There are 3 specific players that sometime play in groups (usually pairs or threes), that worry me, but it's entirely down to their personal skill, not to their grouped/not-grouped status. They also solo queue quite a lot. There are also some players that predominantly solo queue that worry me about as much. For the premades in general, you've got a decent shot at victory with two good players on your team and nobody at the bottom actively trying to sabotage the team. I should probably visit SS and DM at some point and see how they're doing GSF-wise these days. My understanding is that the queues are smaller, so a premade might tilt things a bit more on them.

This does not require a full premade. It just requires everyone on your team to be bad at GSF. I can think of at least 10 people who are active these days in GSF, who by themselves, are capable of pulling off this sort of thing against a really weak team. It's sort of diagnostic of crappy matchmaking where for reasons known only to devs that probably moved on from SWTOR years ago, the matchmaker decides that putting all the weakest players on the same team is the thing to do. It happens. Back when GSF and SWTOR had populations much bigger than now and a GSF Scoreboard Records thread was maintained, the record entries were mostly that sort of game, where one or two skilled people rampage over a team that contains zero players that know how to effectively counter them. I 100% guarantee that grouping is not needed to do this, because I've done it solo myself. I'm at the bottom of the ace level skill spectrum, so I need an especially weak team to fly against in order to pull it off, but this is doable by a solo player, and fairly easy for a pair at the right skill level. I'm curious though, what server and what times does this premade run? Cause I'd actually like to fly against a premade skilled enough to tilt the win/loss odds as much as you say they do. Small pool of players, players tend to play at routine times that fit their personal schedules, matchmaker uses the same algorithm for every match. It's not really surprising for teams to be more or less the same multiple matches in a row. You sir, are a true scholar of GSF history, as shown by this very accurate assesment.

I've had plenty of fun games solo queued against premades. I've had plenty of fun games where a purely solo queued team beat a premade. Pressing the Group Battle dialog button does not make players more skilled. I would be nice if it did, but it doesn't. Throw a bunch of noobs in a premade, and they're just as doomed as they were in the solo queue. There are 2 or 3 exceptional premades, none of which fly regularly anymore as far as I'm aware, where if you're not one of the other exceptional premades, then yeah, your team is probably doomed. For the more average guild or casual GSFer premades, the premade really isn't determinative of match outcome. There might be one or two people on the team to really worry about, but what matchmaker does in terms of filling the non-grouped slots on both teams is typically more important than the mere presence of a premade. Having the 3 or 4 people who are AFKing, or busy whining in Ops chat instead actually make a cursory effort to play well, is about as good having the average casual premade on your side. There's a world of difference between an ineffective player who dies 8 times vs 4 times, or who get 150 objective points vs 25. People who kinda suck but put in at least minimal effort can be carried against a premade. People fully dedicated to doing the "moping potato" style of play usually can't. Premades also aren't as common as some people think they are. Match maker is fairly consistently stupid. Given the same small pool of people in the GSF pool, it will tend to group them similarly from match to match. It doesn't learn from making horribly imbalanced matches, so it's happy to repeat the same team composition mistakes multiple times in a row. Seeing the same people in a team 4 matches in a row really doesn't tell you anything about whether there's a premade queuing or if it's just matchmaker being matchmaker. You have to actually message one of the players and ask in order to find out. The core complaint against premades really boils down to: "I want to win more games." To which the answer is legitimately: learn to play better. Get to the point where 80000 damage, 20 kills, and 50% accuracy (70% or better if in gunship), are fairly routine for you, and premades become not that much of an issue. You'll have a sporting chance of beating them on your own, and your team will have a sporting chance of winning by taking advantage of the premade focusing too much on you. I'm not quite there myself, but I'm close enough that aside from the 2 or 3 specific premades I mentioned, if matchmaker can throw me one other fairly decent player, and avoid lumbering me with people who are arguably flying more for the other team than for the one they're on, I'm not bothered by premades because two decent players + a remainder that aren't actively sabotaging have a reasonable chance of winning. The hard part is getting good at a game mode where there's not good in-game learning experience, you have to go out and pretty much literally do your own homework. Once you are good though, the barrier to beating a mediocre premade is not really that high. The crapshoot of matchmaker is still the crapshoot of matchmaker regardless. Besides, how would people explain away their losses if there weren't premades to blame? It could cause a mental health crisis for people who are convinced that their incredible loss rate doesn't have anything to do with their lack of comprehension of even the most basic GSF game mechanics.