Skip to content

Achievement Set Revisions

Revisions - Working on Sets with Existing Achievementslink

Revisions, as in working on a set that has existing achievements typically requires community approval by presenting your plan in the forum and presenting your plan in the #revision-voting channel in Discord.

You do not need approval to rework achievements or achievement sets where you are the only author. A major aspect or revision voting is getting permission to change the work of others. There are other cases where you might not need to make a revision plan as well.

Note: Replacing existing Game Icons and Badges is handled through a community vote in Discord. See Game Icon Gauntlet.

Preparing your planlink

Any developer wanting to revise a set need to:

  1. Prepare a plan for each (where you're not the original author)

    • Addition
    • Demotion
    • Achievement rework
    • Change to leaderboards
    • Update in rich presence
  2. Resolve the open tickets for all achievements that will be kept in the set.

  3. Present the plan

    • In the game page forum thread in full
    • In #revision-voting post a link to it

Getting Community Approvallink

Anyone in the community can express their concerns or objections. Allow time for discussion and for the developer to adjust their plan if they decide to. If any concerns or objections were expressed, regardless of the developer adjusting the plan, a vote will take place.

Once the discussion has settled a vote should be posted by a developer in the #revision-voting channel.

The vote is approved/rejected after 48 hours. It is pass/fail by simple majority.

When making a revisionlink

  • Do not make copies of existing achievements, or clone and demote existing copies. If there are issues with current achievements make fixes to the existing ones.

  • If you are adding a similar concept to one found in the set, where possible reuse the old concept and update it rather than make a new one.

This prevents players from needing to unnecessarily re-earn achievements, restricts needless changes to sets, and preserves good quality developer work and concepts.

After approvallink

If producing the revision is taking a longer time, every two months (+/- 2 weeks) make a new post in the official forum topic explaining your current progress and renewing the revision. Not doing so will invalidate the revision; the revision plan will need to get new approval.

If you are making a major revision and the set is has not be rescored since July 2019, include a new scoring using the new tier-based scoring system.

No need for approvallink

  • Adding rich presence or leaderboards to an entry that doesn't have them.

  • Making changes to an achievement or to an achievment set where you are the original author and no other developer has revised it; it is still a good idea to post the plan for your changes in the forum.

  • Resolving tickets or bugs on achievements made by developers who have have 10 or more open tickets that are older than two months (you can see their open tickets from the Ticket Manager). This developer is considered inactive in their tickets. In these cases you're only allowed to fix the achievement to match the description; do not change the intention of the achievement without going through the revision process above. If you find a problem with an achievment that has an active developer either create a ticket or contact them to assist in resolution.

  • Adding battery save, cheat code, or password protections to achievements where the developer is inactive. (be sure to properly test your changes). If they are active, either create a ticket or contact them to assist applying the improvements.

  • Making updates to game page information and title / screenshot, but not the game Icon or Badges. For those check Game Icon Gauntlet process).

Changeloglink

Last 10 changes on this page:

  • [2019-08-08 04:04] Kvon: Achievement Set Revisions: Updated policy for replacing badges to go through the icon gauntlet
  • [2019-08-05 16:03] Kvon: Revisions: Made it clear that if you are the only dev of a set you do not need to post a revision
  • [2019-08-01 15:51] Kvon: Set Revisions: posting a proposal to reduce the length of a revision from 72 hours to 48 hours
  • [2019-07-03 22:06] Kvon: Set Revisions: Added a reminder to re-score revised sets (staff vote)
  • [2019-04-16 22:35] meleu: fix markdown format
  • [2019-04-10 17:36] Kvon: Made changes to others RPS as requiring revision. Removed the requirement to contact the original dev as this doesn't follow status quo common practice, and seems (to me) unnecessary.
  • [2019-02-22 20:00] Kvon: slightly changed the wording from the last edit
  • [2019-02-22 19:55] Kvon: developers should only make fixes when the developer is inactive in resolving their tickets.
  • [2019-02-07 00:38] Kvon: Added a complimentary rule to set claims rules (Dev CoC), requiring a dev to renew plans that have not been completed.
  • [2019-02-06 16:37] Kvon: grammar / formatting