Players Argue Over Unity Limits And Scars’ 100-Player Ceiling — July 8, 2026

Players spent the day doing what MMO communities do best when the actual game is quiet: turning one technical claim into a full-blown philosophy seminar. The spark was a familiar one — how many characters can Scars of Honor really put on screen before the whole thing starts wheezing — and the answer, at least in chat, settled into a rough neighborhood around 100 to 120 players.

That number wasn’t treated like gospel so much as a practical ceiling, the sort of thing you can imagine a raid leader squinting at while the battlefield turns into particle soup. From there, the thread veered into Unity, server optimization, and the eternal question of whether the bottleneck lives in the engine, the hardware, or the player who insists on casting every spell at once.

The Great Unity Ceiling Debate

The loudest argument of the day was less about the game itself and more about what the engine can realistically do. One player pushed back hard on the idea that Unity has some mystical hard limit on rendering multiple players, arguing that the real issue is practical performance, not a law of nature carved into the engine’s code. Another countered that, yes, there are limits — just not the kind that make for a neat, absolute number.

That’s where the conversation got gloriously nerdy. Players started tossing around the idea that a standard character model can sit somewhere in the 5,000 to 15,000 vertex range, which prompted the kind of panic math that only happens in MMO chat. If you take that literally, one player joked, you’d only fit a handful of characters on screen before the whole thing falls over. The reply was the obvious one: optimization changes everything, and a highly tuned model can be dramatically cheaper to render.

“If you get the character models down to super low vertice counts... you open up the cpu to render more things,” one player argued, which is basically the sort of sentence that makes a game forum feel like a late-night engineering lab.

The eventual compromise was almost comically reasonable: there’s a difference between what’s theoretically possible and what’s actually sensible in a live game. Players seemed to settle on the idea that Scars of Honor will probably live within a practical on-screen limit, not a grand, impossible dream of hundreds of fully animated bodies all doing spell rotations at once.

What “Optimization” Means When Everyone Uses It Differently

A lot of the friction came from people using the word optimization to mean wildly different things. Some players were talking about rendering efficiency — fewer polygons, less CPU strain, less visual bloat. Others were talking about server-side efficiency — cheaper infrastructure, less expensive computing, and code that doesn’t make the backend cry into its coffee.

That split mattered. One side kept insisting that reducing server costs doesn’t magically let the client render more characters, while the other pointed out that better performance on one side of the stack often frees up resources elsewhere. The result was a surprisingly civil, if very technical, back-and-forth about how much of the game’s eventual scale depends on the engine and how much depends on the servers underneath it.

There was also a bit of optimism in the mix. One player said that if the team’s own server system goes well, that’s the real win — not because it would erase every bottleneck, but because it might keep the core from becoming a disaster. That’s not exactly a glamorous hope, but it’s the sort of hope MMO players understand immediately. Nobody dreams of “adequate backend stability” until they’ve watched a promising game melt under load.

The Self-Made Server System Has Everyone Watching

If the rendering debate was the brainy part of the day, the server talk was the anxious part. Players kept circling back to the idea that Scars of Honor is leaning on a self-made server system, and that alone was enough to make people sit up a little straighter. The mood wasn’t outright doom, but there was definitely a “please don’t be held together with chewing gum” undercurrent.

One player said the system had “crapped out,” which is the kind of blunt community diagnosis that lands harder than any formal bug report. Others softened that a bit, hoping the issue was more about what the server is running on than a catastrophic failure in the core architecture. In other words: maybe the engine isn’t cursed, maybe it just needs a better diet.

That hope was paired with a practical note about cheaper infrastructure. Players pointed out that doing more computing in-house can reduce the amount of money burned on outside hosting, which is the sort of sentence that sounds dry until you remember how many online games have been kneecapped by costs before they ever found their feet. Nobody in chat claimed this was a solved problem. They just seemed relieved that the team might be aiming for something leaner rather than something flashy and fragile.

Albion Online Keeps Getting Dragged Into The Room

No MMO performance argument is complete without somebody dragging in a comparison to another game, and today’s mascot was Albion Online. One player called it one of the best recent examples of pushing Unity beyond its limits, which immediately gave the thread a useful reference point: yes, Unity can do a lot, but only if the team knows exactly where to squeeze and where to cut.

That comparison helped ground the discussion. Instead of treating Unity like either a miracle engine or a broken toy, players used Albion as proof that the ceiling is real but movable. The engine can be stretched, but the stretch depends on how disciplined the developers are with models, animation, and all the invisible plumbing that keeps a crowded battlefield from turning into a slideshow.

The chat also briefly wandered into a clarification about the infamous “65k limit,” with one player noting that it applies to an individual character model rather than the total number of characters. That tiny correction did a lot of work. It turned a scary-sounding number into a more manageable technical detail, which is exactly the sort of thing that keeps a community from spiraling into myth-making.

AI Jokes, X Confusion, And The Usual Discord Chaos

For all the heavy lifting on engine theory, the thread still found time for the kind of nonsense that makes Discord feel alive. Someone joked that “the AI copy paste battle has begun,” which is a pretty good summary of modern internet arguments in general. Another player announced they were going to ask Claude Fable, then immediately dismissed Google Gemini with a “F,” because apparently even technical debates need a mascot race.

There was also a brief detour into the meaning of “X,” with one player asking who that even was and another replying, deadpan, “Formerly known as Twitter.” It’s the sort of exchange that has nothing to do with rendering limits and everything to do with the social glue of a community that can’t resist a side joke while arguing about vertex counts.

And then, naturally, the whole thing ended up in the classic MMO-chat place: everyone half-agreeing, half-arguing, and fully convinced they’d just uncovered the true shape of the problem. Which, honestly, is probably the healthiest possible outcome for a day spent discussing how many people can stand in the same magical fireball before the game starts to sweat.

The Number That Actually Matters

What mattered most today wasn’t the exact ceiling — 100, 120, maybe a little more with enough wizardry and caffeine. It was the fact that players are already thinking about Scars of Honor in terms of scale, stability, and how the game will feel when the screen fills up with actual people instead of test dummies.

That’s a good sign, even if the conversation came wrapped in jokes and technical hair-splitting. The community isn’t just asking whether the game can run; it’s asking whether it can hold together when the real chaos starts. And for an MMO, that’s the only question that ever really counts.