Skip to content

Update: clarifies PCT candidates #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wescopeland merged 2 commits into from
Jul 21, 2026
Merged

Update: clarifies PCT candidates #402

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
517dada
update: clarifies PCT candidates
suspect15 Jul 21, 2026
041b357
Update docs/guidelines/content/player-compatibility-testing.md
suspect15 Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/guidelines/content/player-compatibility-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,9 @@ description: Describes the process for players to conduct compatibility testing
# Player Compatibility Testing
The biggest barrier to adding additional hash support to sets is the time required to test them. This document explains how players may request approval to conduct hash compatibility testing. All hashes linked to a set must be able to unlock all of the set's achievements.

## Hashes Appropriate for Compatibility Testing
The primary goal of the Player Compatibility Testing program is to test and hopefully validate additional language translation patches to achievement sets so more people can enjoy them in their native languages. Other types of patches may be good testing candidates such as photosensitivity removal patches, significant quality of life patches that do not impact core gameplay such as widescreen patches, or expanded save slots. Graphical overhauls or cosmetic patches will not be tested for compatibility.

## Process Overview
Players interested in conducting new hash testing should contact the set maintainer via site direct message and request to conduct compatibility testing. A set maintainer is any active developer who is an author on a set. If all set authors are inactive, [QATeam](https://retroachievements.org/user/QATeam) is the set maintainer.

Expand Down
Loading