Firstwatch closes as WoW Forever steals the week

The week in Scars of Honor Discord had two very different moods. On the official side, Firstwatch Recruitment slammed shut, with the team thanking nearly 700 applicants and promising to review every one before contacting selected players next week. On the community side, the place promptly did what Discord does best: turned that into a mix of hope, impatience, self-deprecating jokes, and a lot of people pretending they were definitely, absolutely, maybe going to be chosen.

Then the conversation wandered off into the weeds and came back wearing a different hat. By the end of the week, players were arguing about MMO history, old-school design, AI testing, and whether any game can still credibly call itself a “WoW killer” without immediately sounding like a man in a trench coat offering you a timeshare.

Firstwatch Is Closed, and Everyone Wants In

The only confirmed news this week was simple and important: Firstwatch Recruitment is now closed. The team said the response was huge, thanked the community for the interest, and noted that selected applicants should start hearing back next week. They also reminded people to keep Discord DMs open so they can be reached if chosen.

That announcement set off the usual blend of excitement and nervous math. Players kept asking when selections would happen, whether it would be via email or Discord, and how long the review process might take. The answer, repeated more than once in chat, was basically: read the announcement, then wait. One player pointed out that with nearly 700 applications, the team has a lot of reading to do. Another guessed it could take one to three weeks depending on volume. A few people were already trying to game the odds, joking about a “second wave” if they missed the first batch.

There was also a small but persistent undercurrent of caution. Some players worried about scam DMs pretending to be selection messages, and others asked who exactly would reach out if they were picked. The community’s best guess was that it would likely come from staff members, but the important part was the same old Discord survival rule: check the tag before you click anything.

“I actually thought more would apply,” one player said, sounding equal parts impressed and surprised.

That surprise mattered. For all the joking, the thread made it pretty clear that people still see Firstwatch as a serious chance to help shape Scars of Honor, not just a way to get in early and poke at the shiny bits.

The Firstwatch Wait Became a Mini Soap Opera

Once the initial announcement dust settled, the chat did what it always does: it started narrating its own anxiety in real time. Some players admitted they had only just noticed the recruitment had already ended. Others said they were still waiting for a DM and had started to feel like the chosen one was always someone else.

A few practical questions kept coming up. One player asked whether the team would notify people by email or Discord; another wanted to know whether there would be more testing cycles after this. The community response was mostly patient, but not exactly calm. People kept reminding each other that the team had a lot of applications to sort through and that no response did not mean rejection.

The funniest part was how quickly the thread turned into a self-aware little support group for people who wanted in. One player joked about being “the chosen” after getting a random DM, only to discover it was a scam bot trying to sell art. Another asked if they could just message the devs directly and “push” their application through, which is exactly the sort of thing that sounds charmingly unhinged in a game Discord and catastrophically unhelpful in any actual hiring process.

By midweek, the mood had settled into a familiar MMO waiting-room hum: hopeful, restless, and just a little bit ridiculous.

The WoW Forever Bombshell Hijacked Everything

If Firstwatch was the official story of the week, WoW Forever was the unofficial one. Chat absolutely ran away with it. Players pored over the new announcements, speculated about launch timing, and immediately started comparing Blizzard’s latest nostalgia machine to every MMO under the sun.

The biggest reaction was simple: people were hyped. Some were excited for the HD/SD toggle, transmog toggle, animation toggle, and the new class and racial changes. Others were already planning their characters around the new race/class combinations, especially the possibility of Undead Paladin, Tauren Druid, and other combinations that would have made older MMO designers reach for a stress ball.

The racials became their own little debate. Players talked about Human stun immunity, Troll healing, Orc changes, and the idea that some of the old meme specs might finally stop being memes. There was a lot of “wait, that actually sounds good” energy, especially around the new movement-speed and utility passives.

But the hype came with the usual MMO baggage. Some players were thrilled; others were wary of Blizzard’s habit of selling the same dream in a new box. A few people said the game looked good but worried about how much of the old design philosophy was being recycled. Others were blunt: they’d try it, sure, but they weren’t ready to declare it the savior of the genre.

The most telling part was how many people ended up talking about their own history with World of Warcraft instead of the new game itself. That’s the real power of a big MMO announcement: it doesn’t just sell a feature list, it drags twenty years of player memory behind it like a very expensive wedding train.

Nobody Can Stop Arguing About WoW Killers

The week’s longest-running side quest was the eternal MMO argument: can anything actually kill WoW? Chat had opinions, and as usual, they were delivered with the confidence of people who have seen every failed contender come and go.

One camp argued that the only thing capable of killing WoW is WoW itself. Another said the genre’s problem has always been that every “WoW killer” just copied the formula instead of pushing the genre forward. A few players pointed to older challengers like Rift and WildStar, saying they captured pieces of the magic but either mismanaged their momentum or spread themselves too thin.

There was also a lot of nostalgia for the older, rougher MMO era: Classic/TBC/WotLK, old battlegrounds, Alterac Valley before it changed, and the simpler days when the genre felt less like a checklist. One player said modern WoW has too much going on, while another joked that the only thing that can dethrone WoW is WoW itself, which is both a joke and a diagnosis.

The broader point, though, was pretty sharp. Players kept circling back to the same idea: the genre spent years chasing Blizzard’s shadow instead of building something new. That’s not exactly a fresh take, but it’s one that still lands because the evidence is sitting right there in the graveyard of ambitious MMOs.

Old MMO Stories, New Old-Man Energy

For a Discord tied to a fantasy MMO, this week got weirdly sentimental. A huge chunk of chat turned into people swapping stories about their first online games, their first PCs, and the various ways they convinced parents to let them keep playing.

There were tales of buying RuneScape memberships with lunch money, sneaking World of Warcraft time cards, dual-booting old Macs, and explaining to adults that some games can’t be paused. People reminisced about floppy disks, demo discs in magazines, CRT TVs, and the first time they realized that “back in my day” is not a joke but a warning label.

The thread had a nice, slightly chaotic warmth to it. Nobody was trying to be profound; they were just collectively discovering that half the server is old enough to remember when a 128MB RAM stick felt like wizardry. The jokes about being ancient were constant, but so was the affection. There’s something oddly comforting about a game community where people can argue about racials one minute and then bond over the fact that they all once had to explain to their parents why a game needed monthly payments.

AI, Security, and the Fear of the Wrong Kind of Automation

Another thread that kept resurfacing was AI testing and security. Players discussed a report about unsanctioned agent behavior during cyber testing, and the conversation quickly widened into a broader debate about how much trust you can place in automated systems.

Some people argued that AI can be useful for internal testing but isn’t a replacement for actual live-player testing, especially when bugs and exploits are the whole point of finding out what breaks. Others were more interested in the security side, talking about guardrails, exposed endpoints, and the nightmare scenario of a system doing exactly what it was told, just not what anyone meant.

The discussion got especially lively when players compared AI risks to the realities of DevOps and security work. One person described the constant pressure of keeping systems safe, while another talked about automated containment tools that isolate suspicious instances and call them in immediately. The mood there was less “robots are coming” and more “please, for the love of all that is holy, stop leaving the API open.”

It was one of the week’s more grounded conversations, oddly enough. Beneath the jokes, people were basically agreeing that automation is only as good as the humans who set the boundaries. Which is true in games, too, if you squint at it from the right angle.

ArcheAge Chronicles Split the Room

Late in the week, ArcheAge Chronicles became the latest shiny object for players to argue over. Some came away impressed by the graphics and the swimming, gliding, and general spectacle. Others hit the open world and immediately started bouncing off the technical rough edges.

The complaints were familiar to anyone who has watched a modern MMO test in the wild: rubber-banding, lighting issues, strange animation behavior, and combat that felt too light, too clunky, or too streamlined depending on who you asked. One player said it felt more like a pretty solo game than an MMO. Another thought it had promise but needed a lot more time in the oven. Someone else compared it to Chrono Odyssey and said the same sort of “looks great in screenshots, less great when moving” problem was all over it.

That split was useful because it showed the community’s real baseline. Players here are not automatically impressed by a glossy trailer. They want systems, class identity, and a world that feels like it can actually hold a population. A pretty shell is nice, but if the combat feels like right-click-left-click and the world feels empty, the shine wears off fast.

And, naturally, Scars of Honor kept getting held up as the comparison point. Several players said they preferred SoH’s more stylized look and seemed to trust that direction more than the hyper-polished-but-wobbly alternatives.

The Week’s Real Story: Hope, Patience, and a Lot of Tabs Open

What mattered most this week wasn’t just that Firstwatch Recruitment closed or that people got excited about WoW Forever. It was the way the community kept circling back to the same core MMO hunger: they want something worth investing in, and they’re tired of being sold the same dream with a different logo.

That’s why the Firstwatch thread mattered. It wasn’t just about getting selected. It was about wanting to be part of a game before it hardens into something else. And that’s why the side debates landed too, from old MMO nostalgia to AI testing to the latest shiny genre contender. Everyone was, in their own way, asking the same question: what kind of MMO is worth our time now?

For Scars of Honor, the answer this week was pretty clear. The community is still paying attention, still arguing, still hoping, and still ready to be called in when the team says the next step is ready. That’s a good place to be. It’s also a fragile one. The trick, as always, is turning that attention into something players can actually touch.