How community issues in RA start: the Metroid Prime Trilogy case

[mark-wd]

I want to raise a broader community/process concern, using as a concrete example the recent Metroid Prime Trilogy discussion and how the game was eventually made unavailable for claiming.

I am using this case because it exposes a process problem, not to argue whether one game should receive a set. The point is about how decisions are communicated, how players are expected to react to them, and how avoidable distrust gets created in the process.

The Metroid Prime Trilogy case is useful because it shows a broader RA pattern. Player-facing policy decisions seem to move from internal discussion to public enforcement without any clear player-facing process around them.

In practice, the pattern looks like this:

1. There is visible player demand or interest in a certain approach to development.
2. A decision is made somewhere outside the public discussion.
3. If the decision is made public, it is usually announced in a non-interactive format: either through a role account such as DevCompliance, or, more rarely and usually more helpfully, by a named lead developer on Discord.
4. The rule basis is at times not immediately cited, linked, or explained.
5. Players ask mostly reasonable follow-up questions: whether the decision is temporary or permanent, which rule applies, whether exceptions exist, and who can clarify the outcome.
6. The process can stall at any point because there is no expectation that the announcing account or decision-making group will follow the case through to a clear conclusion.
7. Because there is no obvious path to challenge, interpret, or request revision of a rule or decision, the comments section becomes the only available venue.
8. Frustration accumulates there, and the discussion becomes more adversarial than it needed to be.

In this specific case, the initial message from DevCompliance was:

Due to its nature as a compilation set, the Rollout Team has determined that this set will not be eligible for claims. Metroid Prime 3: Corruption, as well as the New Play Control! versions of Metroid Prime 1 and 2, are available for claims.

That created several logical questions:

• Is this a rollout-only restriction, or a permanent restriction?
• Where is the rule that makes this ineligible?
• Does the rule apply equally to all compilations, or only same-system compilations?
• Are there exceptions for compilations that are not merely convenience bundles?
• Who decides whether an exception applies?
• How can players or developers request a policy clarification or rule change?

Later clarification exposed further problems. First, the issue seemed to be that compilations are generally excluded from rollouts but may be eligible later. Then the game was retired, and the explanation became that same-system multigame compilations are not allowed sets. Those may be internally consistent positions, but from the player side the process looks opaque and effectively unchallengeable.

Metroid Prime Trilogy is definitely not a clean example of a low-value compilation. It is not simply “three identical games on one disc.” It includes the Wii-control versions of Prime 1 and 2 in English, shares the Trilogy-era credit/unlock system across the package, includes quality-of-life differences, and is widely treated by players as a preferred or definitive way to play these versions of the games. People can still disagree on whether that justifies a set, but that is exactly why the process matters.

The larger concern is this: RA has many highly invested players, but the policy process often feels like it is happening entirely in an internal and out of reach manner. Players can request games, comment, and complain, but they do not appear to have a clear procedural role when rules affect what they can play or how. When decisions are announced through DevCompliance with no clear option for recourse, it creates complicated situations for no reason.

This is bad for players because they feel involved in the ecosystem but structurally outside the decisions that shape a project they invest massive amounts of time in.

It is bad for developers because they become the visible target of frustration that is really about unclear policy and governance, and in the past this has ended in hostility towards devs who attempted to join discussions.

It is bad for staff because opaque decisions create suspicion that the actual reason is personal preference or internal politics, even when the real reason may be much more defensible.

It is bad for RA as a project because comments sections become the place where unresolved policy frustration accumulates, instead of a proper structured venue.

I think RA would benefit from a clearer policy path for cases like this. For example:

• A clearer distinction between rollout-only restrictions and permanent restrictions.
• A short explanation whenever a requested game is retired or made ineligible; not just a silent icon.
• A visible appeal/clarification path for edge cases.
• A way for players to request rule review without needing to DM role accounts or start pressure campaigns in comment sections or forums.
• Some form of community-facing policy representative or process owner who can explain decisions in clear terms.
• One or a few users whose role is strictly player-side, with no development activity even in art or writing, entrusted with representing that strictly player-centric voice in internal discussions.

This does not mean every popular request should be accepted or that developers need to lose decision power. But when the outcome to a request is “no”, that lands very differently when people understand the rule, the rationale, the decision-makers, the scope, and the path for future reconsideration.

The current pattern creates predictable conflict:

• Staff/devs can read the reaction as entitlement or pushiness.
• Players can read the silence or opacity as contempt.
• Trust worsens.
• Then the same kind of conflict repeats under different circumstances, even though it could have been avoided with a better policy process.

That cycle is avoidable.

Metroid Prime Trilogy may be the immediate example, but the actual issue is that RA needs a better way to handle player-facing policy decisions before they become problematic. A clearer and more participatory process for decisions that are practical, rather than structural, would equally benefit staff, developers, and players from exactly this kind of recurring conflict.

[Yartarus]

I feel like RetroAchievements would definitely benefit from more transparency and clarity in these kinds of situations. When I first noticed the situation with Metroid Prime Trilogy, the initial DevCompliance comment announcing that the Rollout Team had determined that the set will not be eligible for claims had been buried because of more comments being added.

I tried to look for an official statement in the set's forum thread, but found that it didn't have one. Since I couldn't find anything, it became a pretty confusing situation to me and probably a few other people too.

[JohnMetroid]

Metroid Prime 1 & 2 are gamecube games, so it's incorrect for staff to blacklist an MPT set based on the current compilation rule. They're flippantly trying to pretend MP1 and MP2 are copies of the japanese versions, which is demonstrably false. Neither had North American or European releases, making MPT the only released versions of MP1 and MP2 in those regions. That's all before mentioning that a new english translation and backporting the in-game achievement system are not trivial changes to be ignored.

Ultimately, RA staff's inability to follow their own rules only serves to make them look ridiculous and unfit. Whoever made the decision should be overruled by senior staff, who need to make it very clear that intentional misinterpretation of RA's rules is unacceptable and will not be tolerated going forward.

[Kaiserlucas]

Thank you for this detailed writeup. I wholeheartedly agree with what has been stated so far. The opacity behind, and as a result, the difficulty to effectively challenge DeveloperCompliance decisions is the biggest structural issue I have with the site currently. Issues like these are not isolated to this instance and are in fact becoming more frequent. Even outside of the scope that regular players can see, we are seeing conflict such as subsets getting rejected with little to no explanation as to the reasoning, and other dev internal controversies that needed major pushback to be reverted.

It is worth noting that there are plans to at least slightly alleviate these issues and hold the DeveloperCompliance team more accountable, see #4519 . This will require subset approvals and rejections to take place in a much more public form, with a centralized place for developers and players to discuss disagreements with decisions made, and hopefully it should lead the DeveloperCompliance team to more diligently explain their reasoning for the decisions they make.

It is important to me that all volunteers to the site are treated with an appropriate amount of respect. This is typically seen as players being civil and not harassing developers and other contributors, but I believe it goes the other way around too, with teams respecting each other. Things like rejecting carefully crafted subset proposals with not as much as a reason given and not having any clear rules to cite for decisions they make that clearly impact developers negatively, do not appear respectful of the developer team's time to me. This is avoidable, and I hope that the DeveloperCompliance team can take all the recent criticisms, even outside the scope of just the Metroid Prime Trilogy, to heart, and work towards a state of the site that everybody involved will be more happy with. This discussion is exactly the right way to look at it, as I also see the Metroid Prime Trilogy case as a symptom, and not the core issue.

[TheDreadedAndy]

Fantastically said, this is a great summary of the current issues with the process.

One frustration I've had with this particular case is the decision to have a set for bit-trip complete, but not a set for trilogy. These games are similar in that they are a compilation of games on the same console; however in bit-trips case the games were all widely available in English, unlike trilogy where only the third game was released internationally. Without a clear view into the process behind these decisions, they feel arbitrary and non-nonsensical.

[CarnavalSines]

Not entering the discussion in itself but just wanted to explain that bit trip has never been discussed prior to being allowed (at least not on my level as a dev) but that it also has unique content in the form of the almost 200 new challenges and the whole bonus gallery including unique song remix. In that sense it's more of a MGS3 Snake Eater vs MGS3 Subsistence, with only the later being allowed since it was the objectively more complete version.

Maybe the same argument can be made for MPTrilogy but I dont know those games, hence once again staying out of it.