01What happened
The story, straight
Gotcha Gotcha Games announced on June 11 that the official RPG Maker forums at rpgmakerweb.com will close permanently in December, wiping out 14 years of community-built tutorials, guides, and troubleshooting threads dating back to 2012. The company is launching RPG Maker Maker as a replacement but has confirmed there will be no archive, migration, or backup of existing content. Hobbyist developers who relied on thousands of searchable threads — where users documented solutions to niche engine problems in precise detail — are now racing to scrape and preserve what they can before the shutdown.
RPG Maker's official forums are going offline in December and taking 14 years of community tutorials, guides, and troubleshooting threads with them. No backup. No archive. Gotcha Gotcha Games is replacing it with something called RPG Maker Maker but isn't moving any of the old content over. Hobbyist devs who spent over a decade documenting solutions to obscure engine problems — the kind of stuff you find at 11pm when you're stuck — are now scrambling to scrape and save what they can before it's gone.
02Spread timeline
Where it actually started
04What's solid, what isn't
Claims by status
- Gotcha Gotcha Games announced on June 11 that RPG Maker forums at rpgmakerweb.com will close permanently in December 2026.
- 14 years of community content dating back to 2012 will be deleted with no archive or migration.
- The company is launching RPG Maker Maker as a replacement platform.
- The exact date in December when the forums go offline.
- Whether independent archival efforts (e.g., Wayback Machine) have captured a meaningful portion of the content.
- Community members are working to scrape and preserve forum content before the shutdown deadline.
05Why it matters
The editorial take
This is a recurring pattern in platform governance: companies shut down community spaces without preserving the knowledge built there. Fourteen years of volunteer-authored documentation — the kind of precise, niche technical knowledge that doesn't exist anywhere else — is being treated as disposable. For indie and hobbyist developers who depend on institutional memory embedded in forum threads, this is a significant loss with no clear recourse.
Another company torching years of community-built knowledge because hosting a forum isn't profitable enough. Fourteen years of volunteers helping strangers for free, and the response is 'we made a new thing, good luck.' The indie dev community that actually used these threads is the one paying the cost.
