doesn’t make any sense playing a class and getting a bunch of of the same class applying
also, would be nice to X out a certain class from applying if you dont want to play w/ that
3 Likes
I think that would only be a temporary fix. The real problem lies in the Havoc mode itself and the extremely unbalanced state of classes and weapons.
As it stands, skills like Bubble and Chorus have become almost mandatory, effectively forcing certain classes to be used while practically excluding non-meta classes.
As a result, party composition loses flexibility, and gameplay tends to become monotonous.
In other words, improving the Party Finder feature may help in the short term, but the true solution is to first address enemy scaling and the balance of classes and weapons in Havoc.
1 Like
The world doesn’t spin around DT balance dude. What balance even has to do with class stacks on quickplay?
can get behind a “no dublicates” options,
excluding entire classes complete seems 1. too tryhard and 2. too anti community
at the point where people would rather leave in droves than to play with anyone using a certain class its a balance issue
before that point its a personal issue
This is about the Party Finder, not Quickplay.
Havoc is a mode that challenges players’ skill limits, and weapons or builds should not take priority.
In HiHavoc, gameplay is dominated by spamming Chorus and Bubble, which makes it boring and quickly tiresome.
Every player should be able to use the classes and weapons they like, and no one should be kicked or excluded just because their choice is meta or non-meta.
Such an environment encourages players to make toxic remarks like, “We lost because you didn’t bring Bubble or Chorus.”
2 Likes
Host should decide himself about composition if they want to see specific ability or build, or class. It’s okay if other people don’t want to bring something that was asked (all about being tolerate and polite, obviously, and for record, with my experience, people usually tend to bring what you’ve asked, and so far I never met a truly toxic player who would whine about player without safety ability or build), but then it’s also okay for host to leave party because of that if they seek specific class with specific build. That’s why mods like inspect from party finder and inspect from social is so useful. You might call it gatekeeping, thought it’s normal for people to seek something specific. Because they have a choice.
Havoc is not a quickplay, players can communicate before entering mission to plan their actions or implement other builds/weapons or ask about it at least. Ultimately host should have kick button in mourningstar lobby, after the session launched kick button goes off mode and inaccessible.
To be clear, if I host my game, I don’t really care what other players bring and why, because I won’t demote anyway and it might be interesting to see their performance. If I join someone’s party, I would prefer to bring what they ask.
What I want to say is that the balance should be fixed so that Havoc doesn’t require forcing specific classes or weapons just to win. Of course, it’s natural for hosts and participants to do so in order to raise their chances of success, and it’s also perfectly fine to refuse or move to another party.
However, the process before starting the game is just far too troublesome. You join a party only to get rejected, then join another and get rejected again, and you can end up being bounced around for tens of minutes just trying to find a group you’re allowed into. I know quite a few people who stopped playing Havoc because of this.
The best solution would be for Havoc to allow joining parties just like Quickplay, where players are not gatekept by their class or weapon choice, but only by their actual skill.
Add it to Quickplay filters too. I would like to only join games with at most one arbite player in them, I’m tired of going through the loop of “leave mission → run all the way to mission terminal → Quickplay → leave mission etc”
terrible idea
this is literally an imagined problem
don’t want a specific class? don’t invite them
there is this weird misconsception going around that having duplicate classes is by DEFAULT a bad thing
yes it can be a bad thing, but it can also be a good thing (depending on builds)
1 Like