From d92342408d796fb6abddde6c0ce52636a3f5fa17 Mon Sep 17 00:00:00 2001 From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com> Date: Wed, 29 Jul 2026 10:59:15 -0400 Subject: [PATCH 1/4] Update claims-system.md Adding rules for Claiming Multiple Ports of the Same Game --- docs/guidelines/developers/claims-system.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/guidelines/developers/claims-system.md b/docs/guidelines/developers/claims-system.md index ccd1bd78..2c790aeb 100644 --- a/docs/guidelines/developers/claims-system.md +++ b/docs/guidelines/developers/claims-system.md @@ -139,4 +139,18 @@ Upon completion of a rollout, compilation sets for that system shall become elig ::: info REASON FOR SPECIAL RULES These rules are in place to ensure a fair chance for any developer to work on these compilation sets immediately as they become available, rather than whomever happens to be awake when the rollout ends. They are designed to give everyone interested a chance to work on these sets. -::: \ No newline at end of file +::: + +### Claiming Multiple Ports of the Same Game + +Letting other developers work on other ports of a game is encouraged. For this reason, developers cannot hold claims for two ports of the same game at the same time. + +Moreover, for the 6 months following the publication of a set for a game, developers have to make sure no other developers are interested before making a claim on a port of the same game. This is done as described below: + + 1. Contact DevCompliance and express your interest in claiming a second port. + 2. DevCompliance will privately reach out to developers that have the game on their Want to Dev list on-site. + 3. The other potentially interested developers will explain how likely they are to claim the game before the cooldown finishes. For example, if 4 months have passed, they will say how likely they are to claim in the remaining 2 months. + +Note that collaborations are exempt from this cooldown as long as the repeat dev does not do a majority of the work. + +For the sake of this rule, different ports of a game are releases on different platforms where the gameplay is largely replicated. Differences in presentation, theme or license is not enough to be considered different games. Content being cut in one port due to technical limitations such as lack of space doesn't make them different games either. When in doubt, contact DevCompliance before claiming. From 6079d0252627781f9a9e1872dc13a595b09265d1 Mon Sep 17 00:00:00 2001 From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com> Date: Wed, 29 Jul 2026 11:17:07 -0400 Subject: [PATCH 2/4] Update set-plagiarism.md Remove self plagiarism exception Add design guidance for ports --- docs/guidelines/content/set-plagiarism.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/guidelines/content/set-plagiarism.md b/docs/guidelines/content/set-plagiarism.md index 30ff7294..bd878c37 100644 --- a/docs/guidelines/content/set-plagiarism.md +++ b/docs/guidelines/content/set-plagiarism.md @@ -21,7 +21,9 @@ Achievement titles should be unique from other sets. This may not always be poss ### Design -The design of an achievement is open to the community. You can use an idea from other sets so long as the achievement badge and title differ. However, an exact copy of the achievement list from another set is prohibited. +The design of an achievement is open to the community. You can use an idea from other sets so long as the achievement badge and title differ. + +When working on a set for a game that already has a set for another port, developers should put effort into differentiating the sets. While progression can often be similar between sets, one should use different challenges and different set structures whenever possible. For some games, the possibilities to differentiate sets are limited, and the design can end up fairly similar despite the developer's best efforts. Before releasing a set that is not clearly distinct from one of another port, consider requesting feedback from other developers or set designer, and if the design remains very similar, run the plan by DevCompliance for approval. ## Acceptable Copying @@ -38,10 +40,6 @@ Copying Rich Presence and Leaderboards are allowed. When copying a Rich Presence Copying the logic of another achievement is acceptable. Developers are encouraged to look at how other sets are coded and incorporate it into their own sets. -### Self-Plagiarism - -You are allowed to copy anything you created from one set to another set. However, it is preferable to let another developer work on a port for a set you have already created. - ### In-Game Achievements Some games incorporate a set of in-game achievements that were released with the game. Any of these achievements can be used as long as they are not Unwelcome Concepts. From 86433423bd49022d9da317090a9d408da2bef1a5 Mon Sep 17 00:00:00 2001 From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com> Date: Fri, 31 Jul 2026 08:54:41 -0400 Subject: [PATCH 3/4] Update claims-system.md Adjusted writing --- docs/guidelines/developers/claims-system.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guidelines/developers/claims-system.md b/docs/guidelines/developers/claims-system.md index 2c790aeb..7d317331 100644 --- a/docs/guidelines/developers/claims-system.md +++ b/docs/guidelines/developers/claims-system.md @@ -145,12 +145,12 @@ These rules are in place to ensure a fair chance for any developer to work on th Letting other developers work on other ports of a game is encouraged. For this reason, developers cannot hold claims for two ports of the same game at the same time. -Moreover, for the 6 months following the publication of a set for a game, developers have to make sure no other developers are interested before making a claim on a port of the same game. This is done as described below: +Moreover, for the 6 months following the publication of a set for a game, developers shall ensure no other developers are interested before making a claim on a port of the same game. This is done as described below: 1. Contact DevCompliance and express your interest in claiming a second port. 2. DevCompliance will privately reach out to developers that have the game on their Want to Dev list on-site. 3. The other potentially interested developers will explain how likely they are to claim the game before the cooldown finishes. For example, if 4 months have passed, they will say how likely they are to claim in the remaining 2 months. -Note that collaborations are exempt from this cooldown as long as the repeat dev does not do a majority of the work. +Collaborations are exempt from this cooldown as long as the repeat developer does not do a majority of the work. For the sake of this rule, different ports of a game are releases on different platforms where the gameplay is largely replicated. Differences in presentation, theme or license is not enough to be considered different games. Content being cut in one port due to technical limitations such as lack of space doesn't make them different games either. When in doubt, contact DevCompliance before claiming. From 09e528e1296cb5782da21cb1b5454ab36761aa97 Mon Sep 17 00:00:00 2001 From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com> Date: Fri, 31 Jul 2026 09:05:12 -0400 Subject: [PATCH 4/4] Update docs/guidelines/developers/claims-system.md Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- docs/guidelines/developers/claims-system.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guidelines/developers/claims-system.md b/docs/guidelines/developers/claims-system.md index 7d317331..e1185e98 100644 --- a/docs/guidelines/developers/claims-system.md +++ b/docs/guidelines/developers/claims-system.md @@ -145,7 +145,7 @@ These rules are in place to ensure a fair chance for any developer to work on th Letting other developers work on other ports of a game is encouraged. For this reason, developers cannot hold claims for two ports of the same game at the same time. -Moreover, for the 6 months following the publication of a set for a game, developers shall ensure no other developers are interested before making a claim on a port of the same game. This is done as described below: +Moreover, for the 6 months following the publication of their set for a game, developers shall ensure no other developers are interested before making a claim on a port of the same game. This is done as described below: 1. Contact DevCompliance and express your interest in claiming a second port. 2. DevCompliance will privately reach out to developers that have the game on their Want to Dev list on-site.