Ever hyped up a big reveal only to watch it crash and burn? That's basically what happened to Jagex at this year's RuneFest, when the studio unveiled its Reignited characters for RuneScape. The idea was to let both new and existing players experience the sandbox MMORPG in a fresh new light, with several refinements promised. Sounds great on paper, right? Well, the veteran community didn't exactly roll out the welcome mat.
Instead of cheers, the reveal sparked a full-blown backlash. Long-time players were enraged, and it didn't take long for the negativity to spread across forums and social media. Jagex clearly felt the heat, because the studio has now issued an apology and a set of promises aimed at calming the storm.
So what exactly went wrong? The source material doesn't give us a blow-by-blow breakdown, but the core issue seems to be how the Reignited characters were presented. What was meant to be an exciting new way to play turned into a PR headache, with veterans feeling like their concerns were being ignored.
Jagex's response? An apology, plus commitments to address the community's frustrations. The studio hasn't just said sorry and moved on—it's promising action. That's a smart move, because RuneScape's veteran player base is the backbone of the game, and losing their trust is a risk no developer wants to take.
For now, details on what those promises actually entail are still thin. But the fact that Jagex is publicly acknowledging the misstep shows they're at least listening. Whether that translates into meaningful changes for Reignited characters remains to be seen.
If you're a RuneScape player, this is one to keep an eye on. The Reignited concept could still turn out to be something special—if Jagex can win back the community's confidence. For newcomers, it might be a chance to jump in fresh, but only if the veterans give it their blessing.
What do you think? Can Jagex turn this around, or has the damage already been done? Will you be giving Reignited characters a shot when they arrive? Let us know in the comments.
Comments (0)
Log in to join the discussion
Log InNo comments yet