Skip to content

Developer's Code of Conduct

This document lays out for developers the rights, responsibilities and rules for fairplay.

If you are not a dev check here how to become a developer.

See Also: Users Code of Conduct.

Golden Ruleslink

  1. Respect your fellow developer and communicate through any issues you have civilly.
  2. Make room for other developers to get a chance to work on games they like, in their own way.
  3. Anyone can become a developer if they put in the effort.
  4. All achievement sets are open for improvement.

tl;dr - Developers must do the following to keep in good standinglink

Developing a new achievement setlink

Before you begin working on a new achievement set go through the new achievement set checklist.

Reserving a game for achievement developmentlink

1. How to Reservelink

The only way to reserve a game is by clearly stating your goal to create achievements in the official forum topic of the game on a new post.

  • No other declarations, plans or lists posted anywhere else are to be considered in this.
  • Code notes do not reserve a game (if you have added notes but not reserved the game in the forum, any other developer is free to work on it).
  • It is recommended that post a list of planned achievements, so the community can review your work and give you feedback.

2. Concurrent Reservations Limitlink

As in the maximum number of achievement sets one developer can have reserved at once.

  • Junior Developer: 1.
  • Developer: 4.
  • Veteran Developer: 8 (a Veteran Developer is someone who is Developer for at least 18 months and has published at least 20 achievement sets).
  • Note: Working on an approved revision or joining another developer in a cooperative effort does not reduce from this total.

3. Reservation Timinglink

  • Only reserve a game for development when you start working on it. In other words, do not reserve games just to block others from working on it.
  • Please reserve the set as soon as you begin working and not as you are finishing your work.

4. Reservation Renewalslink

You can renew your reservation every three months (+/- 2 weeks) if you've not finished your set.

  • To renew the reservation, post about it on the official game's forum topic.
  • Do not edit your previous declarations, but make a new post talking about your current progress.
  • Avoid locking down a set indefinitely. If it appears a developer continues to delay development on a set with little or no progress the staff may intervene.

5. Respecting Reservationslink

Do not ask, pressure or discourage anyone from working on any game, in public or in private (of course, assuming the person is already following all other standards on this Code of Conduct).

6. Reservation Cool-Downlink

After the time you've reserved a set wait at least 48 hours before you publish it. This allows reservation review and to clear up any possible reservation disputes.

Important Noteslink

  • If you post a complete plan, be open to suggestions; you can get excellent input and suggestions this way.
  • You must adhere to the Basic Achievement Design Guidelines, otherwise your set won't be allowed.
  • When you publish your work you are giving it over to the community to be reviewed and reworked over time.

Collaborationlink

  • Let others know if you welcome collaborators.
  • If you've recently reserved a set and someone else voices desire to work on a set that you've reserved within the last 72 hours (beyond suggesting ideas), consider ways in which you can collaborate with them.
  • If someone reserved a game you're interested in before you, don't get frustrated. You are encouraged to request collaboration. You can post your desire to collaborate in the forum or send them a message to get permission from them to publish your contributions. You can also wait and go through an Achievement Set Revision after the set is published.

Basic Achievement Design Guidelineslink

Unwelcome Conceptslink

You can (and should) be as creative as you can, but there are some concepts that are NOT welcome for achievements, such as:

  1. Require glitches (acceptable in Bonus sets).
  2. Require two players.
  3. Require perfection all game (maybe acceptable in Bonus Sets).
  4. Dying (simply), or playing bad without any purpose.
  5. NSFW content in text or image.
  6. Achievements popping frequently with little effort from the player (including multiple achievements for doing the same task, such as one for beating a boss and another one for getting the item left by the boss, etc.)
  7. Achievements obtainable with zero effort for no meaningful purpose (example: start the game as character X, collect one coin). It's acceptable if there's something fun/historical/interesting you want to address.
  8. Require excessive repetitive grinding, such as reaching level 99 in an RPG, for no meaningful purpose (maybe acceptable in Bonus Sets).
  9. Rely entirely on randomness, especially when there are extremely low odds. However, for games where the randomness is a major aspect, it may be appropriate.
  10. "Secret Achievements", where the players have no indication of what they're going after. If you want to prevent spoilers give at least a clue on the Achievement Title/Description. Otherwise the players will start to search on web or mess with Achievement Editor/Memory Inspector, and in the process they can stumble across even worse spoilers.

Note: With every rule, there's an exception. This is especially true with unwelcome concepts. All unwelcome concepts have some wiggle room. when in doubt consult with the admin team.

Every Achievement Set MUST Havelink

Protection for situations where the players can get achievements without effort, such as:

  1. Demo mode;
  2. Ingame cheat codes;
  3. Battery saves;
  4. Passwords.

See also: Achievement Templates and Real Examples for some well known protection techniques.

Every Achievement Set SHOULD Havelink

  • At least basic Rich Presence;
  • Game Badges for each achievement;
  • All game page information filled out, and game images uploaded.

Note: Rich Presence, Leaderboards, and game page images/information can only be added by full developers

  • Leaderboards for scores and time challenges.
  • Missable achievements flagged, especially for RPGs and long games.
    • Use [m] in the end of achievement's title to flag it as missable.
  • An achievement guide. Guides can be created and posted here.
  • For games with text-triggered achievements (especially RPGs) it's recommend to find an event flag instead of hooking onto text or text ID. Text presentation varies between regional versions making multi-region support difficult.

Achievement Scoringlink

When scoring achievements match your scores to one of these 5 tiers. There is no achievment set point cap.

  • 0-5 Easy / Minor Significance
  • 10 Medium / Intermediate Significance
  • 25 Hard / Major Significance
  • 50 Very Hard / Completion Level Significance
  • 100 "Impossible" (Typically for bonus sets)

When scoring there are other factors to be considered, such as achievement spread and game length.

Tools to Help you Succeedlink

We have a roadmap you can use as a guideline to create a good achievement set.
We also have an achievement design guide on how to design good achievements, not the technical side but the conceptual. Creating a balanced set is one of the most difficult aspects of development, we have a set balance guide which will help you in thinking about how to create a set that flows.

It is preferable and recommended to work on one set at a time. But if you have more, be open for a teamwork or even delegate the set creation if another dev contacts you.

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 in the #revision-voting channel in Discord. Not all changes need approval. See Achievement Set Revisions for details.

Code Noteslink

Leave accurate code notes for each address you use for achievement conditions. This helps you and others maintain the set, keeping it free of bugs.

You're free to add any code notes you discover to any set without declaring intentions to work on the game. Just be careful to not delete previous notes added by someone else.

Handling Ticketslink

After you've published achievements be prepared for bug reports.

You're expected to keep your work bug free by appropriately resolving tickets. Respond to all tickets as soon as possible. The sooner you respond the better, cause the problem is fresh in the player's mind and you can use them to help you to resolve the problem.

While resolving tickets, leave a brief summary of what you did. If you have an indication of false report leave a message showing what conclusions you've made, and then close the ticket. Closing/Resolving a ticket without leaving any comments is an unwelcome attitude.

Do not declare your plans to work on a game if you have open tickets.

If you want to resolve tickets or fix bugs on achievements made by another developer, it's always a good practice to try to contact them and check if they are still active before changing their work. An inactive developers is someone who have have 10 or more open tickets that are older than two months (you can see their open tickets from the Ticket Manager).

If the developer is active, you can assist them in the resolution.

If the developer is inactive you can freely resolve their tickets. However 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.

Developer Status Extended Inactivitylink

If a developer is inactive for two years or longer, meaning within two years they have not created any new achievements or resolved any incoming tickets, their developer status will expire.

If this happens to you, you are very welcome to come back to the scene if you want to create new content for our community. First you'll want to review and understand this document (the Developer Code of Conduct). When you feel ready to adhere to it, message us to user RAdmin (a shared admin mail account) here on site or speak to the admin or mod users on the RetroAchievements Discord server to check how to get your developer status back.

Achievement Ownershiplink

When you publish your work you are giving it over to the community to be reviewed and reworked over time - see Achievement Set Revisions.

While the original developer does not own published achievements they are still the caretaker in terms of bug fixing and maintenance. If another developer revises the achievement they are the new caretaker of that achievement.

Feedback about the Developer's Code of Conductlink

Although the Developer's Code of Conduct is the result of an intense debate, it's not an immutable document. If you have suggestions for improvements, contact us on our Discord server or send a message to RAdmin.

Changeloglink

Last 10 changes on this page:

  • [2019-08-17 14:37] meleu: fix markdown formats
  • [2019-08-13 19:50] Kvon: Code of conduct: text hooking tip
  • [2019-08-01 14:50] Kvon: Developer Code of Conduct: Slight rewording of "important notes" added a "collaboration" sub-section.
  • [2019-08-01 14:44] Kvon: Developers code of conduct: Added a point encouraging collaboration
  • [2019-07-11 08:46] Kvon: DevCoC: Added achievement scoring, put back in reservation time limit (48 hours instead of 72), formatting and titles
  • [2019-07-07 20:53] Kvon: Dev CoC: 3 changes to simplify reservations for devs. 3 months instead of 2 for renewals; reservations do not REQUIRE set plans; 72 hour waiting period is removed. Moved "before you begin" to a new page. Few other minor edits/typos.
  • [2019-06-19 16:05] Kvon: added developer inactivity timeout (2 years)
  • [2019-05-14 12:40] Kvon: made some headings linkable. (especially for citing rules.) If there's a better way to format these please go for it.
  • [2019-02-28 16:39] Kvon: The words "on a new post" for reservations is essential because sometimes devs will edit the top post and the change will not be noticed in forum activity.
  • [2019-02-27 10:01] Kvon: typo