Scars of Honor Players Want Better Combat, Not Button Spam — May 14, 2026

For a channel that had just come down from a playtest high, this chat had plenty of fight left in it. The loudest argument wasn't about lore, raids, or some mythical endgame spreadsheet. It was about something much more immediate: whether Scars of Honor should make you keep hammering your basic attack key like you're trying to wake up a stubborn keyboard.

That one complaint cracked open a much bigger conversation about what players actually want from combat. Not easier combat, exactly. Not simpler, either. What people kept circling was feel — the difference between a system that asks for skill and one that just asks for repetitive strain. Around that, the rest of the day unfolded in classic MMO fashion: cautious optimism about the test, anxiety over messaging, side quests into Albion Online and Darkfall, and then the eternal genre blood feud over PvP and PvE. In other words, business as usual.

The Auto-Attack Debate Got Real Fast

The cleanest piece of feedback in the whole log was also the most relatable: one player said that after a few minutes in the test, they already wished they didn't have to keep pressing the basic attack key. The immediate fix proposed by several people was simple enough — keep auto attack on the bar, but make it a toggle by default, so you still have to initiate it without turning every fight into a finger workout.

That sounds modest, but the pushback was immediate because this wasn't really just about convenience. It turned into a fight over what counts as skill expression in an MMO. One camp argued that mandatory weaving and active inputs make combat more player-driven. The other side called forced basic-attack weaving "poopoo," which is not the most academic phrasing, but it gets the point across. If your combat depth comes from mashing one button between real abilities, players are going to ask whether that's meaningful execution or just busywork with a macro-shaped loophole.

And yes, macros came up almost instantly. One player dismissed the whole thing as easily macroable, while another went broader and said they hoped the final game wouldn't lean on macro infrastructure or addons at all, because those tools often sand away human error and expose weak design. That's a spicy take in MMO circles, but it fits the mood here: players don't want a fake skill ceiling built out of repetitive inputs that third-party tools can flatten anyway.

What made the discussion interesting is that nobody was really asking for combat to be dumbed down. Quite the opposite. One player flatly said the game has a chance to raise the combat ceiling and worried the genre usually caves to people who can barely type. Another argued that oversimplification dilutes expression and individuality. The disagreement wasn't over whether combat should reward mastery. It was over whether this specific kind of input actually creates mastery.

That's a useful distinction, and one Scars of Honor will need to get right. Players will forgive rough numbers in a technical test. They will not forgive combat that feels like a chore.

Players Can Already Read the Class Intent — Even Through the Jank

For all the arguing over clunkiness and scaling, one of the more encouraging threads in the chat was how clearly people felt the classes were communicating their intended roles. Even players who thought the numbers were all over the place still seemed able to read the design language.

One player laid it out neatly: Ranger looked built around lots of skill shots, Druid around healing over time, Mage around burst, and Paladin around engage tools and crowd control. That's exactly the kind of feedback a team wants from an early test. You can fix tuning. You can fix weird scaling. You can fix a one-second stun that feels too weak to matter. What is much harder to fix is a class roster that doesn't project any identity at all.

The chat kept coming back to that point. Several people said the class design had good bones, and when combat worked, it felt good. Battleground fights got singled out as fun, even by players who were otherwise pretty critical. Another player said the most important thing wasn't balance at this stage, but the team's ability to improve and fix bugs over the course of the test. That got repeated more than once, which tells you where expectations landed after the dust settled.

There was still plenty of skepticism. One player who rerolled classes late in the test said scaling felt wildly inconsistent, with some spells hitting absurdly hard and others barely doing anything without secondary talent investment. Another said that imbalance affects feel so much that it's hard to judge what combat will really be. Fair enough. If your toolkit alternates between wet noodle and orbital strike, you aren't exactly getting a clean read.

Still, the broader tone here was surprisingly generous for an MMO community fresh off a rough technical test. Players weren't pretending the build was polished. They were saying they could see the shape of something promising underneath the bugs.

The Test Ended, and So Did the Illusion That Everyone Read the Memo

A small comedy of errors ran through the chat after the playtest ended. People noticed the game disappearing from Steam libraries, launch buttons throwing up "not released" messages, and a general sense of "wait, why can some people still play?" The answer, of course, was mostly that the test was over, but not before a few confused souls briefly wondered whether they'd been singled out by fate, Steam, or science itself.

That confusion fed into a more serious point about access and expectations. One player wished the team would just sell a cheap package that guaranteed access to all testing phases, mostly because some invites apparently landed with less than a day left in the test. Another immediately pushed the other way, saying the lack of paid access was refreshing and felt like the old days of applying for a closed alpha and hoping the email gods smiled on you.

That split says a lot about where MMO players are in 2026. Plenty of people are tired of early access being used as a glorified cash register for unfinished games. Others just want a reliable way to get in and help test without playing lottery with their inbox. In this chat, the anti-paid-access side had a little more moral momentum. People described paid testers as more entitled, more likely to demand returns on their money, and often the first to leave when the novelty wears off.

There was also a smart suggestion buried in the middle of this: show progress between tests with before-and-after videos. A player pointed to Chrono Odyssey's social posts as an example and argued that split-screen clips of movement, UI, and combat improvements would keep discussion alive while proving that feedback is actually landing. That's the kind of low-drama, high-value communication strategy more studios should steal immediately.

Not everyone wanted more visibility, though. One person argued the opposite — keep tests smaller, rotate testers, and don't advertise so hard until the game is closer to beta. Another went even further and said the team should stop testing publicly until the game is near launch, to avoid giving players a bad taste too early and burning them out before 1.0.

That idea didn't exactly win the room, but it speaks to a real fear: when you show your game early, players don't just test systems. They start building a story about the project. If that story gets ahead of the build, you're in trouble.

Hype Is Helpful Right Up Until It Isn't

That last point hung over a lot of the conversation. More than one player suggested expectations had been set too high going into the technical playtest, especially by the way the game had been talked up beforehand. One person said the test was exactly what it claimed to be — a technical playtest, closer to proof of concept than alpha — but that the messaging around it had people expecting more.

Another player said they had low expectations and the game smashed them anyway, which is the other side of the same coin. If you came in braced for disaster, the test looked like a rough but encouraging foundation. If you came in expecting a near-finished MMO, it probably felt like a bucket of cold water.

The name that floated through this part of the chat was Armegon, with one player admitting his videos got them extremely hyped. Another replied that he had hyped the game so hard it kind of worked against him once the test arrived. That's not really a dunk on creators; it's just the old MMO problem. Enthusiasm is contagious, but it can also inflate a technical test into a promise it never made.

The sanest take in the room was probably the one saying the playtest had "good bones" and that something special might be cooking, even if it still needs a lot of work. That's a much healthier place for a community to land than either blind doomposting or full cult mode.

And yes, there was a reality check on timing too. Somebody confidently claimed the game would come out in Q4 of the year, and that got corrected on the spot. Elsewhere, one player guessed the project felt more like two to three years away from 1.0. That may or may not be right, but it matched the broader mood: interested, hopeful, and very much not under the illusion that this thing is about to ship next Tuesday.

The PvP vs PvE War Never Misses a Chance to Respawn

No MMO chat stays on one subject for long, and this one eventually did what MMO chats always do: it wandered into a full-scale ideological war over PvP and PvE. Scars of Honor was the spark, but the argument quickly pulled in Albion Online, EVE Online, New World, Dune Awakening, ESO, GW2, and half the genre's old scars.

The basic split was familiar. One side argued that PvP players are a vocal minority in MMORPGs and that successful games historically cater more generously to PvE while still giving PvP a real place. WoW, Guild Wars 2, and ESO got cited as the model: broad PvE appeal, with PvP as an important but smaller slice.

The other side pushed back hard on the idea that PvP-first players are some tiny fringe. They argued that PvP communities retain better, don't require constant content injection in the same way PvE players do, and often keep games alive long after the theme-park crowd has moved on. One player put it bluntly: in PvP, you are the content.

That led to the usual sub-arguments.

Flagging, Servers, and the Search for Peace

A few players tried to drag the conversation toward practical solutions instead of tribal warfare. Separate PvP and PvE servers came up. So did flagging systems. Then someone floated a more interesting idea: layering players so that opting out of PvP moves you into a PvE layer, preserving immersion for PvP players while still letting both groups share towns and social spaces.

It was one of the more genuinely constructive moments in the whole debate, right up until someone pointed out that such a system could wreck the economy if PvE players could farm without risk while feeding the same market. Which, to be fair, is exactly how these conversations always go. Every elegant solution lasts about thirty seconds before the economy guy enters the room.

The Numbers Fight

There was also a lot of amateur demography, some of it more convincing than others. One player argued for a rough 70/30 split in content focus, on the theory that around 70% of MMO players are PvE-first and 30% are PvP-focused. Another cited data from Funcom around Dune Awakening, claiming a huge majority of players never engaged with PvP zones at all. Others countered that opt-in systems muddy the numbers, because if PvP is avoidable, avoidance doesn't necessarily mean disinterest — just preference, time pressure, or risk aversion.

If you're wondering whether the chat solved MMO design forever, it did not.

What it did reveal is that players are deeply aware of the tradeoffs. They know forced PvP can shrink your audience. They know pure PvE can struggle with retention unless the content treadmill is excellent. They know every system choice creates a different kind of community, and not all of those communities can stand each other for more than ten minutes.

Albion, Darkfall, and the Ghosts MMO Players Still Chase

The PvP argument naturally opened the floodgates for side discussions about older and adjacent games. Albion Online got a lot of airtime as the current example of a PvP-oriented MMO that actually works at scale, even if players immediately started fighting over why it works.

One side praised its risk-reward structure, arguing that PvP is avoidable if you're smart, that gatherers and crafters can thrive, and that smaller skilled groups can beat larger ones. The other side saw the usual zerg problems, alt-account nonsense, island silver printing, and a system that still pressures players into dealing with PvP if they want the best rewards. Somewhere in the middle sat the practical truth: people clearly respect Albion more than they necessarily enjoy what it asks of them.

Darkfall inspired a different kind of nostalgia — the dangerous kind. Players reminisced about its absurd skill ceiling, its zerg issues, its licensing weirdness, and the way every conversation about it sounds like veterans describing a war that was both miserable and glorious. One player insisted no game will ever come close to Darkfall's skill ceiling. Another replied, essentially, yes, and that's part of why it failed.

That thread dovetailed with a smaller but more interesting design tangent: dangerous worlds. A few players said they'd love to see MMOs lean harder into night-time danger, roaming threats, and the possibility that ignoring warnings should get you killed. Dragon's Dogma was invoked as the kind of energy they'd like to see — not full survival-game sadism, just a world with actual teeth.

That idea feels more relevant to Scars of Honor than the endless Darkfall autopsy, honestly. Players aren't only asking for systems. They're asking for a world that can surprise them, and maybe punish them a little, without turning into a griefing simulator.

Even the Off-Topic Wandering Said Something About the Mood

The chat drifted, as game chats do, into what people were playing while waiting for the next test: SWTOR, Guild Wars 2, League of Legends, No Man's Sky, Baldur's Gate 3, tabletop campaigns, wishlist MMOs, and a lot of dwarf enthusiasm. There was a whole side conversation about necromancers, tieflings, duergar, and a D&D character who made enough chaotic life choices to become an NPC. Frankly, that part ruled.

But even the digressions told you something. People weren't rage-quitting the idea of Scars of Honor. They were parking themselves in the broader MMO and RPG hobby while they waited. That's a very different energy from a community that feels burned beyond repair. The jokes about the Discord going quiet, the missing key beggars, and everyone returning to real life all carried a note of comedown, not collapse.

And when someone asked what people liked most from the test, one of the answers was simply: the community. That's cheesy in a vacuum. In context, after a technical test and a day full of arguments, it's actually a decent sign.

The Real Test Starts Now

What mattered in this chat wasn't whether every take was right. Plenty weren't. MMO communities are basically perpetual motion machines powered by half-remembered patch notes, personal trauma from 2009, and one guy who still thinks his preferred ruleset would save the genre if only the cowards listened.

What mattered is that Scars of Honor got players arguing about specifics. Not vague hype, not logo worship, not desperate key begging. Combat feel. class identity. testing strategy. PvP structure. World danger. That's the stuff people argue about when they can already see a game taking shape.

The next step for the team is pretty clear: tighten the feel, communicate progress better, and don't let the hype machine write checks the build can't cash. If they can do that, this test won't be remembered as a messy first impression. It'll be remembered as the moment players started taking the game seriously enough to fight over what it should become.