RPG Maker’s forums shut down, but Gotcha Gotcha Games won’t archive 1.4 million posts

Gotcha Gotcha Games is shutting down the official RPG Maker forums, and its closure FAQ makes the part that stings most clear: there are currently no plans to provide a public archive or backup of the current forum once it has been closed. The timing is real, too. New account registrations have been disabled, the forum will go read-only on June 18, and access is set to end on December 11.

This matters because the RPG Maker forums are not some small corner of the internet. Eurogamer notes there are 1.4 million posts across the community, including 280,000 posts over 45,600 threads in the Legacy Engine Support forum, plus 276,000 messages across 34,700 threads in the JavaScript Plugins forum. If you have ever solved an infuriating, niche technical problem by finding a years-old thread where someone else already suffered through the same workaround, you already understand why people are reacting strongly.

Here is the headline deal: Gotcha Gotcha Games says it is launching RPG Maker Guild, aiming to provide a welcoming space where RPG Maker creators can connect, share projects, exchange ideas, and continue growing the community together. That is the good news. The bad news is that the old forums are not being archived. In plain terms, the company is moving the “front door” but choosing not to preserve the “library.” And the difference is more than sentimental. Forum posts often function like distributed documentation, bug trackers, plugin catalogs, and institutional memory rolled into one.

The closures also land at a moment when every platform operator is grappling with the same problem: how to maintain institutional knowledge when communities outgrow tools, platforms, or moderation models. Bigger companies have been blamed before for wiping out user-built knowledge bases, and the source explicitly points to EA closing the BioWare forums as a comparison. The through-line is consistent. Users do not just want a place to talk; they want a place where answers stay searchable.

The practical and cultural stakes are showing up in the public reaction. Forum users quoted in the coverage call out that “no proper archive” essentially means years of community knowledge, including plugins, tutorials, bug fixes, troubleshooting threads, scripts, resources, devlogs, and historical context are being erased because users did not manually download everything in time. Another user says they would not have completed their game, One Fenix Down, without these forums. The sentiment is not abstract. It is about games that exist today because someone found help in the past.

Gotcha Gotcha Games is offering two bright spots in the meantime. First, the old forum is not instantly disappearing. New posts are stopping on June 18 when it switches to read-only mode, and the forum stays online until December 11. Second, the company is encouraging users to save any posts, guides, resources, or other content they wish to keep before the closure. That is better than nothing, but it still shifts the burden onto creators to do what archivists normally do, on a timeline that favors the company’s transition over the community’s needs.

Meanwhile, there is an external backup effort that could partially cushion the blow. The source notes that Jason Scott, described as perhaps the online world's foremost archivist, said (or at least unmistakably implied) help is on the way from Internet Archive, with Archive Team crawlers targeting rpgmakerweb. That is a real lifeline for preservation, but it is also a reminder that the community may be relying on third parties rather than receiving an official archive from the platform owner. For executives, this creates a reputational risk: when users feel the organization is outsourcing memory rather than stewarding it.

So what are the second-order implications for decision-makers, founders, and operators running community platforms or developer ecosystems? You can launch a new community space. You can moderate differently. You can change UX. But if you do not preserve the knowledge that made the ecosystem valuable in the first place, you do not just remove old posts. You raise the cost of problem-solving for new users, you reduce the discoverability of prior work, and you increase the likelihood that the same bugs, plugin conflicts, and engine gotchas will be rediscovered and relearned the hard way. In ecosystems like RPG Maker, where community-created content can directly determine what games get shipped, that loss can be felt far beyond the forum itself.