-
Notifications
You must be signed in to change notification settings - Fork 0
RA Achievement Set Revisions Change Proposal for Feedback Draft 1
Link: Existing Docs Page–It will be helpful to have the existing document open side-by-side when reviewing.
Any changes to a set with existing achievements is considered a revision. They typically happens after someone present a plan in the game's forum topic and in the #revision-voting channel on Discord and the plan is approved by the achievement creators community.
There are three types of revisions:
Standard Revisions - Changes to an achievement set that affect another developer's work. These include adding achievements, removing achievements, and reworking existing achievements.
Rescores - Changes to the point value of an achievement.
Icon-Gauntlet - Changes to a game page's icon that is awarded upon mastering a set and changes to the individual achievement badges.
Each are assigned their own Discord role:
| Type | Role | Getting the role | Who can get the role |
|---|---|---|---|
| Standard Revisions | @revision-voting | React with 🗳️ here | Achievement creators |
| Rescores | @rescore | React with 💯 here | Achievement creators |
| Icon Gauntlet | @icon-gauntlet | React with 🎨 here | Any verified discord user |
Permission can be obtained via site DM or Discord, and written permission will be considered binding. Should there be a conflict after obtaining permission, contact the Developer Compliance team and submit proof if possible.
Please limit approval requests for a specific revision to once per week to allow time for response.
Ignored requests shall be considered to be approvals. See rules under (Vetoing a Revision)<link> for details on when this occurs..
If any active authors veto your revision and you believe the veto to be unreasonable you may do one of the following:
Appeal the decision to the QA Team if you believe the revision addresses a necessary set quality issue.
Appeal the decision to the DevCompliance Team if you believe the revision addresses a developer code of conduct issue, such as an unwelcome content.
* Icon or Badges that have been changed via Icon Gauntlet after set release must always undergo an Icon Gauntlet vote to be changed.
An active author may veto a revision to a set.
It is expected that most requests for revision, especially additional achievements, will be granted by active developers. RetroAchievements is a community project, and while we want developers to be able to take pride in, and have control of, their work, proceeding in good faith and engaging with the community leads to the best results.
Active authors should try to reach a compromise with the proposer of a revision whenever possible.
Ignoring an approval request does not count as a veto.
Active devs shall respond to a request within a week.
A week without a response, while the dev has been active on the site, shall be considered as an ignored request.
If two requests are ignored, this will be considered as “approved” by the active dev ignoring the request.
Missables are done at the discretion of the set authors and their inclusion is not eligible to appeal should an active author veto them.
When authors are inactive or active authors all approve:
Resolving tickets or bugs on achievements made by developers who are listed as inactive in the list of developers.
See ticket handling for ticket-handling rules
Changing the description to clarify or correct it to match the logic that is already present.
Adding battery save, cheat code, or password protections to achievements.
Fixing misspellings, grammatical errors, and other typos in the achievement names or descriptions.
Note: In some cases, these are intentional, so be sure to make note of it in the forum.
Making updates to game page information and title / screenshot / box art images.
Adding a standard "beat the game" achievement if one is missing and there are no active developers on the set.
A standard "beat the game" achievement is an achievement for completing the game at its normal/default difficulty without additional requirements.
If uncertain how to proceed, please contact DevCompliance.
Adding icons or badges when none exist or when badges are default badges.
Updating the set icon or badges to a badge that displays the same content but are of better quality or correct dimensions.
Add the missable “tag” using standard notation and remove the non-standard notation only if the missable is already marked in some other non-standard fashion or all active authors approve.
Standard notation is to place [m] at the end of the title.
When you are the author, or are a collaborative author with approval of other active authors:
Changing the set icon or your achievement badges when the existing images were not the result of an icon gauntlet after set release.
Prepare a plan for each addition, demotion, or change. Include a before and after for rescoring.
Request any active author approval, if necessary and present the plan in the set’s forum topic.
NOTE: Be as specific as possible, but if you have only a vague plan, provide as strong of an idea of what you want to do as possible and don't go too far from that idea.
If revision vote is needed per table in <Revision Approval Process>, prepare a revision vote in the appropriate discord channel with a link to the set page and a link to the revision plan in the forum
Standard revisions post in #revision-voting and ping @revision-voting to vote.
Rescores post in #revision-voting and ping @rescore to vote.
Icon Gauntlets post in #icon-gauntlet and ping @icon-gauntlet to vote. See [Icon Gauntlet Process] below for further details.
You may message RAdmin or an Active Developer to create the vote on your behalf.
Once a revision vote is posted, the developer can address any comments, concerns, and objections the community may have to the plan. The vote is approved/rejected after 24 hours and is pass/fail by simple majority.
If a revision vote fails, changes must be made to the revision proposal before submitting a new proposal for that game.
After two failed proposals, 24 hours must pass after the failed vote before any new polls are permitted.
Keep this content
Add: When changing logic or another component of an achievement, please make a publicly-visible backup of the old logic, description, etc on the forum.
Revise this section based on current #icon-gauntlet process, which is partially subject to rule changes above as it is now more formally considered a revision and subject to the guidelines above.
Revision voting is currently dev-only. While voting is exclusive to Discord, please remember that anyone can express their comments, questions, concerns, criticisms, etc. in the forum thread in which the plan was posted. Criticism should be constructive and suggest ways to improve the proposal. The issues regarding Discord exclusivity will be addressed in a future version of the website.
If you vote against changes in an achievement set, please state your reasoning in the discussion channel. This is so potential compromises can be made for a broader acceptance of the changes.
Hijacking revision, rescore, or icon-gauntlet votes will not be tolerated. Votes from alt accounts will be discarded if discovered and repeated occurrences will result in the alt account being removed from the server. If the alt's primary account is confirmed, they will have their vote(s) discarded and may face suspension from future votes.
If a revision plan that involves the demotion of achievements is proven to contain misleading or false information regarding the in-game requirements, the current proposal will be considered invalid. If evidence of this is found after a vote has already passed, the demoted achievements must be reinstated until a new vote is held.
Link: [Existing Docs Page](https://docs.retroachievements.org/Achievement-Set-Revisions/)–It will be helpful to have the existing document open side-by-side when reviewing. Revision Types (No Changes) Any changes to a set with existing achievements is considered a revision. They typically happens after someone present a plan in the game's forum topic and in the #revision-voting channel on Discord and the plan is approved by the achievement creators community. There are three types of revisions: [Standard Revisions](https://docs.retroachievements.org/Achievement-Set-Revisions/#Standard-Revisions) - Changes to an achievement set that affect another developer's work. These include adding achievements, removing achievements, and reworking existing achievements. [Rescores](https://docs.retroachievements.org/Achievement-Set-Revisions/#Rescores) - Changes to the point value of an achievement. [Icon-Gauntlet](https://docs.retroachievements.org/Achievement-Set-Revisions/#Icon-Gauntlet) - Changes to a game page's icon that is awarded upon mastering a set and changes to the individual achievement badges. Each are assigned their own Discord role:
Type Role Getting the role Who can get the role Standard Revisions @revision-voting React with 🗳️ here Achievement creators Rescores @rescore React with 💯 here Achievement creators Icon Gauntlet @icon-gauntlet React with 🎨 here Any verified discord user
Standard Revisions (Remove) This section gets removed and synthesized into various things below. Rescores (Remove) This section gets removed and synthesized into various things below. Icon Gauntlet (Remove) This section is synthesized into various things below, but will have an Icon Gauntlet Process that describes how things work as currently handled by the art team.
Revision Approval Process All revision types are subject to the following: Revisor’s Authorship of Set Type of Revision Approvals needed. Plan in Set Forum Revision Vote Required Free Claim Eligibility
Existing Author, Only Active Author Own Achievements: Add, Demote, Rescore, Change Achievement, Change Badge* None Recommended No Eligible
Inactive Author’s Achievements:Demote, Rescore, Change Achievement or Change Badge*
None Required Yes, if not in pre-approved list
Existing Author, Other Active Authors Own Achievements: Add, Demote, Rescore, Change Achievement or Change Badge* All active authors Recommended No Eligible Other Active Author’s Achievements:Demote, Rescore, Change Achievement or Change Badge* All active authors Recommended No
Inactive Author’s Achievements:Demote, Rescore, Change Achievement, or Change Badge* None Required Yes, if not in pre-approved list
Not an Author, Set Author(s) Active Any All active authors
Required Yes, if not in pre-approved list
Not an Author, No Active Authors Any None Required Yes, if not in pre-approved list
Permission can be obtained via site DM or Discord, and written permission will be considered binding. Should there be a conflict after obtaining permission, contact the Developer Compliance team and submit proof if possible. Please limit approval requests for a specific revision to once per week to allow time for response. Ignored requests shall be considered to be approvals. See rules under (Vetoing a Revision) for details on when this occurs.. If any active authors veto your revision and you believe the veto to be unreasonable you may do one of the following: Appeal the decision to the QA Team if you believe the revision addresses a necessary set quality issue. Appeal the decision to the DevCompliance Team if you believe the revision addresses a developer code of conduct issue, such as an unwelcome content.
- Icon or Badges that have been changed via Icon Gauntlet after set release must always undergo an Icon Gauntlet vote to be changed. Vetoing a Revision An active author may veto a revision to a set. It is expected that most requests for revision, especially additional achievements, will be granted by active developers. RetroAchievements is a community project, and while we want developers to be able to take pride in, and have control of, their work, proceeding in good faith and engaging with the community leads to the best results. Active authors should try to reach a compromise with the proposer of a revision whenever possible. Ignoring an approval request does not count as a veto. Active devs shall respond to a request within a week. A week without a response, while the dev has been active on the site, shall be considered as an ignored request. If two requests are ignored, this will be considered as “approved” by the active dev ignoring the request. A note on Missable-Tagging Missables are done at the discretion of the set authors and their inclusion is not eligible to appeal should an active author veto them. Pre-Approved Revision Types When authors are inactive or active authors all approve: Resolving tickets or bugs on achievements made by developers who are listed as inactive in the list of developers. See ticket handling for ticket-handling rules Changing the description to clarify or correct it to match the logic that is already present. Adding battery save, cheat code, or password protections to achievements. Fixing misspellings, grammatical errors, and other typos in the achievement names or descriptions. Note: In some cases, these are intentional, so be sure to make note of it in the forum. Making updates to game page information and title / screenshot / box art images. Adding a standard "beat the game" achievement if one is missing and there are no active developers on the set. A standard "beat the game" achievement is an achievement for completing the game at its normal/default difficulty without additional requirements. If uncertain how to proceed, please contact DevCompliance. Adding icons or badges when none exist or when badges are default badges. Updating the set icon or badges to a badge that displays the same content but are of better quality or correct dimensions. Add the missable “tag” using standard notation and remove the non-standard notation only if the missable is already marked in some other non-standard fashion or all active authors approve. Standard notation is to place [m] at the end of the title.
When you are the author, or are a collaborative author with approval of other active authors: Changing the set icon or your achievement badges when the existing images were not the result of an icon gauntlet after set release. Proposing a Revision Prepare a plan for each addition, demotion, or change. Include a before and after for rescoring. Request any active author approval, if necessary and present the plan in the set’s forum topic. NOTE: Be as specific as possible, but if you have only a vague plan, provide as strong of an idea of what you want to do as possible and don't go too far from that idea. If revision vote is needed per table in , prepare a revision vote in the appropriate discord channel with a link to the set page and a link to the revision plan in the forum Standard revisions post in #revision-voting and ping @revision-voting to vote. Rescores post in #revision-voting and ping @rescore to vote. Icon Gauntlets post in #icon-gauntlet and ping @icon-gauntlet to vote. See [Icon Gauntlet Process] below for further details. You may message RAdmin or an Active Developer to create the vote on your behalf. Once a revision vote is posted, the developer can address any comments, concerns, and objections the community may have to the plan. The vote is approved/rejected after 24 hours and is pass/fail by simple majority. If a revision vote fails, changes must be made to the revision proposal before submitting a new proposal for that game. After two failed proposals, 24 hours must pass after the failed vote before any new polls are permitted. When Making a Revision Keep this content
Add: When changing logic or another component of an achievement, please make a publicly-visible backup of the old logic, description, etc on the forum. Icon Gauntlet Process Revise this section based on current #icon-gauntlet process, which is partially subject to rule changes above as it is now more formally considered a revision and subject to the guidelines above. Voting and Discussion Etiquette (Note: Additions in Bold) Revision voting is currently dev-only. While voting is exclusive to Discord, please remember that anyone can express their comments, questions, concerns, criticisms, etc. in the forum thread in which the plan was posted. Criticism should be constructive and suggest ways to improve the proposal. The issues regarding Discord exclusivity will be addressed in a future version of the website.
If you vote against changes in an achievement set, please state your reasoning in the discussion channel. This is so potential compromises can be made for a broader acceptance of the changes.
Hijacking revision, rescore, or icon-gauntlet votes will not be tolerated. Votes from alt accounts will be discarded if discovered and repeated occurrences will result in the alt account being removed from the server. If the alt's primary account is confirmed, they will have their vote(s) discarded and may face suspension from future votes.
If a revision plan that involves the demotion of achievements is proven to contain misleading or false information regarding the in-game requirements, the current proposal will be considered invalid. If evidence of this is found after a vote has already passed, the demoted achievements must be reinstated until a new vote is held.