Skip to main content
DatabasePlannerTalentsMapGuidesBlog
Tools
Compare loadoutsTwo gear planner builds — slot by slot and combined affix totalsCompare itemsSide-by-side BeastBurst database items (stats & affix pools)Blog iframeEmbed a post on another siteTalent treeChronicle talent planner — pick a class and share builds from the URLNickname generatorGenerate character-style nicknames for Scars of Honor

Artisan

Crafting calculatorWill be added soonRecipes trackerWill be added soonAll artisan
All tools
Discord
KnowledgeScars of Honor knowledge base — guides, lore, referencesMedia galleryOfficial trailers, screenshots, and wallpapers (mirrored from scarsofhonor.com)AboutAbout SoH Chronicle — the project, contact, credits
LanguageENUA

Site

  • Home
  • About
  • Blog
  • Knowledge base
  • Guides
  • Planner
  • Nickname generator

Database

  • All items
  • By type

    • Equipment
    • Mounts
    • Consumable
    • Valuables
    • Other
  • Slot, rarity, and search controls are on each list page.

Artisan

  • All artisan
  • Crafting calculator
  • Recipes tracker

Tools

  • All tools
  • Compare loadouts
  • Compare items
  • Blog iframe
  • Talent tree
  • Nickname generator
Scars of HonorChronicle

Scars of Honor Chronicle is an unofficial fan project and is not affiliated with the game or its publishers.

Official Scars of Honor website

Contact: aocmerchant@proton.me

Privacy Policy·Terms and Conditions

© 2026 Scars of Honor Chronicle

Database
Planner
BuildsSaved snapshots when signed inEquipmentSlot-by-slot gear & statsTalentsChronicle talent tree plannerScarsLocked Scar roll preview by class group
AugmentationComing soon
CraftingComing soon
  1. Home
  2. /Blog
  3. /The Under-35 Panic and a Community Feeling Thin — June 25, 2026
ENUA

2026-06-25 · Discord Summary

The Under-35 Panic and a Community Feeling Thin — June 25, 2026

A short burst of chat turns into a pointed mood check for Scars of Honor: players worry about younger fans leaving, older regulars carrying the room, and the long shadow of the last playtest. Even side jokes about GGG and Bethesda land like coping mechanisms.

  • discord
  • ai-summary

Some community check-ins arrive with charts, roadmaps, and carefully staged optimism. This one showed up as a handful of blunt messages, a couple of repeated warnings, and the kind of awkward joke-making people reach for when they don't love the mood in the room.

The immediate spark was tiny: a reminder that you can mute announcement notifications because Scars of Honor "isn't coming online in a while." But that throwaway bit of practical advice opened the door to something heavier. Players weren't really talking about notification settings. They were talking about drift — the sense that people are leaving, the last playtest still stings, and nobody seems sure who the game is still holding onto.

The Under-35 Debate Got Weird Fast

One of the sharpest threads in this short exchange was a worry that the project is losing players "under 35" and, with them, its future audience. It wasn't framed delicately. It was framed like a warning siren.

That kind of age-bracket panic can sound a little absurd when you isolate it, but the feeling behind it is easy enough to read: if younger players bounce off early, a community starts to feel older, smaller, and more static in a hurry. In MMO spaces especially, people don't just count bodies; they count momentum.

The pushback was immediate, and a little chaotic. One reply dismissed the concern outright, arguing that younger players are the easiest to lose anyway because they "come and go," and that the real priority should be keeping the few players over 55 who are still around. That's not exactly a data-driven retention strategy, but it is revealing. Different players aren't even arguing over the same problem. One side sees a failure to attract the future. The other sees a failure to value the loyal survivors.

And then came the social snapback: "No, bad Mara," repeated for emphasis, followed by a baffled "what? why was it bad" and someone else simply calling it a "hot topic." That's the whole thing in miniature. A community trying to talk about decline, but tripping over tone before it can even settle on substance.

The Last Playtest Is Still Doing Damage

The most consequential line in the log might also be the bleakest: "All people leave the project / discord about the last play test." Hyperbole? Probably. But hyperbole doesn't come from nowhere.

When players keep circling back to the last playtest as the point where enthusiasm cracked, that's not just nostalgia for a better week. It's a sign that the test became a reference point for disappointment. Maybe it exposed technical problems, maybe it cooled expectations, maybe it simply failed to give people a reason to stick around afterward. Whatever the exact cause, the chat treats that event less like a milestone and more like a wound.

That's a nasty place for any online game community to sit. A playtest is supposed to create stories, class chatter, wishlist posts, and a little healthy overanalysis. If the enduring memory is instead that people left afterward, then the test didn't just fail to build momentum — it may have spent some of the community's remaining patience.

Community Management Is the Subtext, Even When Nobody Says It Cleanly

"Its time to Doo something cm or we lose all futur player" isn't polished English, but the message lands just fine: somebody wants community management to step in and do something before the room gets any emptier.

That plea matters because it sits right between two kinds of frustration. On one side, there's the practical reality that the game isn't coming back online soon. On the other, there's the emotional reality that silence makes every gap feel bigger. When players start asking for CM intervention in a chat this small, they're not necessarily demanding miracles. Often they're asking for signs of life, sharper communication, or simply a reason not to mentally move on.

The opening note about muting announcements accidentally underlines the problem. It's useful advice, sure, but it also carries a grim little implication: if updates are sparse and the wait is long, players are already being coached on how to tune the project out more comfortably. That's not fatal on its own. It is the kind of vibe that can settle over a community if nobody actively counters it.

Jokes About GGG and Bethesda Sounded Like Escape Hatches

The final turn in the chat swerved into job-talk: maybe apply to Grinding Gear Games, maybe go test Bethesda's ES6. On paper, that's just off-topic banter. In context, it reads like the sort of gallows humor game communities produce when they don't know what else to do with the lull.

People joke about leaving when staying feels uneventful. They joke about working somewhere else when the current project isn't giving them much to chew on. That doesn't mean everyone is packing their bags for New Zealand or trying to QA the next Elder Scrolls. It does mean the conversation had already drifted away from playing the game and toward imagining other places where game development might actually be happening.

Even the little one-word reactions — "sensitive," "soft," "emrmagerd" — add to that picture. Nobody here sounds locked into a productive argument. They sound restless, prickly, and a bit punch-drunk from waiting.

This Was a Tiny Chat, but Not a Trivial One

Small logs can still tell on a community. This one did.

What mattered here wasn't a big reveal or a dramatic fight. It was the shared assumption underneath almost every line: the wait is long, the last playtest didn't leave people buoyant, and retention now feels like a live issue rather than a theoretical one. Whether the concern is younger players vanishing, older regulars hanging on, or the need for someone official to steady the ship, the throughline is the same — people are measuring absence.

That's the kind of mood a game can survive, but not by accident. If Scars of Honor wants this conversation to stop sounding like a headcount in a half-empty tavern, it needs more than patience from its remaining faithful. It needs a reason for them to keep the notifications on.

← Back to blog