**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Comments
An alliance on the podium (dropped to Master 4 after that loss) facing & losing to a T2 alliance is just absurd.
That match should've never happened.
There is no denying that they are somehow manipulating the system. How are they doing it is for Kabam to figure out.
But I do feel they need to get docked as it's just not fair to other alliances.
Also they had total 151 deaths this season with an average of 12.5 deaths per war. That is not only the absolute worst in all Master alliances, but also worse than a lot of P1 alliances.
The 2nd & 3rd most deaths given by other Master alliances are 98 & 96. And NA.ON has 151 deaths.
And they claim they even have a CCP member playing with them, which makes this situation even worse.
It is known how they exploited matchmaking, several other master allies used it during the season.
Hopefully kabam have a fix for the matchmaking exploit which honestly shouldn't be that hard to implement.
Actually, another recent thread said it a couple days ago.
https://forums.playcontestofchampions.com/en/discussion/346554/nothing-impossible-matchmaking#latest
Still confused how they can “delay their enlistment” until higher teams have already been matched up, and then Enable their Enlistment at a later time when there are no longer any higher teams left for the matchmaking process to find a matchup for them with, resulting in them getting a lesser team remaining to be matched with ??
As far as I know, if your Ally is NOT Enlisted at the moment Matchmaking begins, then your Ally CAN NOT get a match for that war. You can NOT choose to Enlist at some point later during the 4 hour Matching Window.
(several screenshots from other Ally's since Persistent Defense has come out, mostly related to bugs with “how did we not find a match” or “how did we become unenlisted when we were clearly enlisted”, show example of what Message is on Enlistment Pane in those cases where you are not enlisted when matching begins).
So (as I asked in other smaller thread above), is it being claimed they are actually “Hacking” the servers/database to insert themselves into matching later in, after matching has taken place for top teams already ???
Is whatever they are supposedly doing something that is a new vulnerability in the system since Persistent Placement feature began ? Or has it always existed, even back when you had to Manually Enlist for every single war ?
(asking these questions, so Kabam has something to look at, if indeed there is a “hole” in the system)
But in summary, wondering just HOW they are doing it.
Breaking into the servers during the matchmaking process to insert themselves into the database ? BIG TIME BAD.
Otherwise, somehow just delaying WHEN they do their Enlistment (thru normal means) until after Matching has already begun, I didn’t think was even a possibility. If you don’t enlist until after matching has started (in theory) you don’t get a match for that war (enlisting for that war after process has begun isn’t possible, in theory).
But if that is the case (knowing full well they are exploiting it), ALSO BIG TIME BAD (just shouldn’t even be technically possible).
I think simply delaying when you enlist into matchmaking might work (hopefully kabam fixed that with their update yesterday), because I heard they missed 1 matchup last season, not sure how true it is though.
Noone piloted