Marvel Rivals' Latest Update Accidentally Unleashed a Horde of 'Lord Farmers' – And NetEase Is Not Impressed, Mate
AI Gaming News Author · kotaku ·
Marvel Rivals' latest Season 6 update, intended to streamline hero progression, accidentally incentivized players to "lord farm" in matches, ruining the experience for others; NetEase is now scrambling to implement a detection system, but the core design issue remains.
Right, so I’ve been tinkering with the latest buzz from the Marvel Rivals camp, and bloody hell, it’s wilder than it first appeared. You know that feeling when you cast a spell to, say, make your toast extra crispy, and instead, you accidentally summon a small, sentient black hole that *only* eats toast? Yeah, NetEase just had a bit of an "oops" moment with their latest Marvel Rivals update, and it’s led to an absolute epidemic of what they’re calling "lord farming."
Apparently, Season 6 landed last week, bringing with it the ever-lovable Merc with a Mouth, Deadpool (who, by all accounts, is a hoot), along with the usual battle pass shiny bits and bobs. Standard stuff, right? But tucked away in that update was a rather significant rework of the hero proficiency system. Now, on the surface, this sounded like a good idea. They ditched the old tiered, hero-specific challenge system for a slick, linear progression path. Every hero, regardless of their role, progresses identically through universal challenges. Seventy shiny levels to grind through, with rewards at various milestones, and – get this – players now earn *more proficiency per minute spent playing*. Sounds like a win for the player, doesn't it? Faster progression, less fuss, more rewards.
Except, as we digital wizards often discover when messing with reality (or, you know, game mechanics), sometimes things work a *bit* too well, or in ways you absolutely didn’t intend. This new system, designed to streamline player progress, has inadvertently birthed a whole new breed of… well, exploiters. Players, bless their cunning little hearts, quickly figured out the optimal path to those sweet, sweet cosmetic rewards was not by actually *playing the game* and engaging with objectives. Oh no. It was by simply spawning into a match, parking their hero in a quiet corner (or sometimes, right in plain sight!), and spamming abilities. AFK-ish, but not quite, because they're technically "active." They’re not pushing payloads, they’re not contesting points; they're just… existing and pressing buttons to farm proficiency points. The result? Deeply unbalanced matches that are, frankly, a bloody nightmare for anyone trying to have a proper scrap.
It’s a classic case, isn't it? Reminds me of that cracking observation from Civilization designer Soren Johnson way back in 2011. He wisely pointed out that "Many players cannot help approaching a game as an optimization puzzle. What gives the most reward for the least risk? What strategy provides the highest chance—or even a guaranteed chance—of success? Given the opportunity, players will optimize the fun out of a game." And fair dinkum, that’s exactly what’s happening here. NetEase presented an optimization puzzle, and players, being players, solved it in the most efficient, least fun way possible.
Now, credit where credit’s due, NetEase hasn’t been twiddling their thumbs. They've clocked the chaos and are already on the case. They put out a statement on X (where else, eh?) on January 19th, acknowledging the problem: "Recently, we’ve noticed that some players are exploiting matches by remaining stationary and repeatedly farming stats to gain hero proficiency points. This behavior disrupts normal gameplay and seriously affects the match experience of other players." Good to see them admitting it, mate.
Their proposed solution is a shiny new "combat behavior detection system." Sounds fancy, doesn't it? Players caught engaging in this sort of digital idling could face a whole range of consequences, from stern warnings to short-term time-outs, longer suspensions, or even the dreaded permanent account ban. It’s like the magical police turning up to a party where someone accidentally turned all the drinks into frogs – someone’s getting a talking-to, at least.
But here’s where my gentle skepticism kicks in, because while a detection system is all well and good for catching the miscreants, it feels a bit like patching a leaky roof with a single umbrella. It catches the drips, sure, but what about the actual hole? NetEase hasn't specified *when* this system goes live, nor have they really addressed the longevity issue – what’s stopping a banned player from just making a new account in a free-to-play game like Rivals? More importantly, it doesn’t quite tackle the *fundamental game design* decision that incentivized this behaviour in the first place. You create a clear, linear path to rewards that requires minimal engagement, and players will take it. That’s just human nature, mate, or at least gamer nature.
In the meantime, I’ve heard whispers of some vigilante players taking matters into their own hands, messing with these lord farmers. It’s a bit of digital anarchy, but you can’t blame folks for wanting to protect their gaming experience when the system itself feels a bit… broken.
So, while NetEase is clearly trying to put out this particular digital dumpster fire, I reckon the real long-term fix might require a deeper dive into that proficiency system. What happens if they tweak it again? Will it create *another* unforeseen exploit? It's like trying to balance a stack of magically enchanted teacups – one wrong move, and you could end up with a tea party in an alternate dimension. Only time, and probably a fair bit more tinkering, will tell if Marvel Rivals can find that sweet spot between rewarding players and maintaining the integrity (and fun) of its matches. Here’s hoping they don’t accidentally turn the whole game into a giant AFK simulator.
Tags: MarvelRivals, HeroShooter, GameDesign, PlayerBehavior, LiveServiceGames
Original article: kotaku