Valve deleted the "RPGMaker" user tag from Steam yesterday, and the developers most affected by that change are celebrating. The counterintuitive reason: the tag had become a filter for exclusion, not discovery. Players who auto-excluded anything tagged "RPGMaker" missed games they'd otherwise enjoy, while developers using the engine saw their work buried under prejudice against a tool rather than judged on its output.
Why the Tag Became a Scarlet Letter
Steam's tagging system works both ways. Players tag games to find them, yes, but they also use tags to eliminate entire categories from their browsing. The "RPGMaker" tag had curdled into something closer to a warning label than useful metadata.
The problem traces to a glut of low-effort releases. RPG Maker's low barrier to entry—drag-and-drop mapping, default asset libraries, minimal coding—made it trivial to pump out derivative games and list them for sale. Over years, "RPGMaker" became shorthand for shovelware: default character sprites, RTP (Run Time Package) music, corridor dungeons with no design intent. Players learned to filter the tag entirely.
But here's the asymmetry most people miss: the engine tells you almost nothing about the game's quality. A tool is not a genre. RPG Maker powers everything from 20-hour narrative experiments to mechanically intricate tactics games to horror titles like Corpse Party and To the Moon that defined their subgenres. The tag flattened this spectrum into a binary: avoid or don't.
Developers on Reddit and Bluesky noted the split in reactions. One RPG Maker MZ developer wrote that the tag "was probably doing more harm than good" because players with preconceptions would auto-exclude games they'd otherwise try. Another developer frustrated by the removal—"why would you remove rpgmaker are you fucking insane"—likely relied on the tag for genuine community building among engine enthusiasts. The majority sentiment, though, favored deletion.
The hidden variable: Steam's algorithm weights tags heavily in recommendation flows. Games carrying a stigmatized tag get suppressed not just in direct searches but in "More Like This" carousels, Discovery Queue placements, and curated event visibility. Removing "RPGMaker" doesn't hide that a game used the engine—store pages still list RPG Maker in system requirements or credits—but it stops the automated penalization.
What This Means for How You Actually Browse Steam
Without the tag, your discovery behavior needs to shift. Here's where to focus:
| Old Habit | Replacement Strategy | Trade-off |
|---|---|---|
| Excluding "RPGMaker" to avoid shovelware | Check screenshots for default RTP assets (repeated tilesets, generic character sprites) | Takes 10-15 seconds vs. instant filter; catches more good games |
| Assuming engine = genre | Read the actual tags: "Story Rich," "Tactical RPG," "Psychological Horror" | Requires parsing more information; yields better matches |
| Trusting tag volume as quality signal | Check review count-to-player ratio and recent review trend | More reliable but slightly slower |
The bottleneck now moves to you. Steam's 17 new tags include "Bullet Heaven" (settling the Vampire Survivors-like nomenclature debate) and others that describe what you do rather than how it was built. This is the correct hierarchy. You don't browse by "Unity" or "Unreal Engine" tags; RPG Maker shouldn't have been an exception.
For returning players burned by bad RPG Maker experiences: the shovelware didn't disappear. But its visibility mechanism changed. Default-asset games now compete on the same terms as everything else—screenshots, reviews, capsule art—rather than getting algorithmically quarantined. This means worse RPG Maker games may actually get less exposure, since they can't hide behind tag-based community sorting and must survive open competition.
For curious new players: this is your window. Games previously invisible to you because of tag prejudice are now surfacing in normal browsing. The psychological horror space especially benefited—RPG Maker's 2D constraints and built-in scripting created a distinctive aesthetic that many acclaimed indies exploited.
The Real Test: What Developers Do Next
The tag deletion forces a decision on RPG Maker creators. Previously, some leaned into the tag as identity, building communities around engine-specific techniques. Others fought against it, deliberately obscuring their tool choice in marketing. Now everyone operates under the same obscurity.
This creates two likely outcomes:
- Quality signaling shifts to demo quality. With no engine tag to serve as shorthand, developers must front-load proof of polish. Expect more robust Steam demos from RPG Maker creators, since the store page has to do heavier lifting.
- Asset customization becomes mandatory. Games using obvious default sprites and music will read as amateur faster without the contextual excuse of "oh, it's RPG Maker." The cost of entry—time, not money—rises for developers who previously relied on engine familiarity to excuse rough presentation.
The misconception to avoid: that this change "legitimizes" RPG Maker games. It doesn't. It removes an illegitimate stigma and replaces it with neutral evaluation. Some games will fail harder now, exposed to broader audiences without protective tagging. Others will succeed that previously couldn't break through algorithmic suppression.
For players, the actionable shift is simple. Stop filtering by tool. Start filtering by output. The 30 seconds you spend scanning screenshots and reading the first few reviews will catch more good games and fewer bad ones than any engine tag ever did.
What You Should Do Differently
Treat this as Steam finally aligning its tagging system with how games should be evaluated: by what they are, not what made them. Your next browse session, leave the engine assumptions behind. The game worth your time might look like something you'd have filtered out yesterday.
