From 517dadaa4e1a0077da3554560247ac5a07c607f6 Mon Sep 17 00:00:00 2001 From: suspect15 <106546659+suspect15@users.noreply.github.com> Date: Tue, 21 Jul 2026 06:44:28 -0400 Subject: [PATCH 1/2] update: clarifies PCT candidates --- docs/guidelines/content/player-compatibility-testing.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/guidelines/content/player-compatibility-testing.md b/docs/guidelines/content/player-compatibility-testing.md index c1b32e1c..a668edf0 100644 --- a/docs/guidelines/content/player-compatibility-testing.md +++ b/docs/guidelines/content/player-compatibility-testing.md @@ -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 game play such as wide screen 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. From 041b3579bfc25c221d0468e5de3b7af591d720d2 Mon Sep 17 00:00:00 2001 From: suspect15 <106546659+suspect15@users.noreply.github.com> Date: Tue, 21 Jul 2026 06:46:58 -0400 Subject: [PATCH 2/2] Update docs/guidelines/content/player-compatibility-testing.md Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- docs/guidelines/content/player-compatibility-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guidelines/content/player-compatibility-testing.md b/docs/guidelines/content/player-compatibility-testing.md index a668edf0..d40bd661 100644 --- a/docs/guidelines/content/player-compatibility-testing.md +++ b/docs/guidelines/content/player-compatibility-testing.md @@ -7,7 +7,7 @@ description: Describes the process for players to conduct 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 game play such as wide screen patches, or expanded save slots. Graphical overhauls or cosmetic patches will not be tested for compatibility. +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.