DevQuests

What are DevQuests?

They're achievement development-related quests that developers can take part in at any time. Each one has a specific goal and upon reaching that goal, the achievement developer will earn the badge.

General Rules

1. For Set-Creation achievements other than DQ15, please announce your DQ pick in devquest or via the DevQuest inbox on site early on in your development. This will give us time to make sure any issues with the choice can be sorted out early. Late requests may not count.
2. For Maintenance achievements (i.e.: DQ1, DQ5, DQ14, etc), just create a column in the DevQuest Remastered sheet to the left of completed entries and fill it in as you work. Contact the DevQuest team when you are complete with all entries for review.
3. For Revision achievements (i.e.: DQ2 and DQ13), make sure your choice is already on the corresponding approved list. You will need to satisfy the repair plan. These quests should be more than simple one-achievement revisions. If a repair plan seems to be overly simple, contact us first to ensure it will qualify.
4. Unless otherwise stated in a DevQuest's description, collaborations are not allowed.
5. Standard set quality or better is expected for DevQuest sets. If a set appears to be of insufficient effort or a copy/paste set, it may be rejected at the DevQuest team's discretion. Rich Presence is required for DevQuest sets. The DevQuest team is happy to suggest improvements for qualification.
6. New sets may only be applied towards one DevQuest. No double-dipping.
7. Always contact the active authors on sets whose content you will update or add to.

Reporting

• Contact the team using the DevQuest team on site or on in #devquest on Discord.

Schedule and Announcements

• DevQuests do not have a specific release schedule. Typically, they are announced shortly after their badge has been completed.
• New DevQuests and any updates to existing DevQuests will be announced in #developer-news on the RetroAchievements Discord and site news

The Quests

Badge	Number	Name	Info
	001	Ticket Massacre (Maintenance)	Resolve/close 50 tickets • Falsifying ticket closures will result in disqualification • The following do not count toward the total: Network issues, tickets for achievements you developed, tickets you opened, tickets closed on behalf of Junior Developers, and tickets closed as a result of ticket spamming. • May not overlap with DevQuest 2 or with any completion requirements for DevQuest 13. • Tickets for users banned from development count for double credit. • This quest can be done multiple times (current limit: 3)
	002	Retro Renovator (Revision)	Repair 3 sets from provided batch 1. Pick a game from the list of approved DQ2 sets and then post your claim to the #devquest channel on discord or send to DevQuest inbox 2. Do the revision process as normal: Post plan on the forum, make a revision vote if any changes aren't on the "no need for approval list," make a revision claim if adding achievements. 3. Resolve any open tickets for achievements kept in the set, Tickets for achievements being left demoted can be simply closed with reason of demotion cited 4. Revisions must fix everything specified in the repair plan. Contact the DevQuest team for any clarifications to what is included in the repair plan. 5. Contact the DevQuest team with any questions you have. 6. When the set is ready mark it down on the doc under your name to be signed off by a DevQuest Member. • If you identify a set you believe should qualify for DQ2, notify the DevQuest team for addition to the list and development of a repair plan prior to claiming. All claims must be on the list. • This quest can be done multiple times (current limit: 3)
	003	Singles In Your Area (Maintenance)	Tighten up the logic for 20 single-condition achievements 1. This is a chance to tighten the code up, do not just add a bad line of code 2. You do not need a revision vote to tighten 3. Achievements cannot be your own, you should just fix these anyway! 4. PLEASE LEAVE Comments on each achievement on what you changed for log purposes 5. May not overlap with the required repair plan for DevQuest 2 or with any completion requirements for DQ13
	004	Veteran Developer (Stat-Based)	This DevQuest consists of several passive goals, each one being their own achievement, which are as followed: 1. Has published at least 1000 achievements and worked on at least 25 sets as the sole or majority developer 2. Has created achievements for at least ten different console IDs 3. Has been an active developer for at least two years 4. At least 85% of sets have dynamic rich presence (Vet Dev I required) 5. Yielded unlocks have exceeded 50,000 6. As a sole developer, submitted one or more sets for code review and received an overall grade of at least 22 7. Has used at least 75% of all currently available flags and features (Vet Dev I and VI required)8. Has obtained at least two DevQuest badges 8. Has obtained at least two badges through DevQuest 9. Has obtained at least five badges through DevQuest •Note: A constantly evolving toolkit means that these requirements are subject to change at any time
	005	Trigger Happy (Maintenance)	Update 20 sets with the Trigger and Measured flags 1. Must put measured and/or triggered where it makes sense. Do so on all appropriate achievements in the set. Achievements with unnecessary use will not be counted. If you hit 50 and there is more in a set to update, you must update the rest of the set. 2. You can do achievements in your own sets at half credit. Put both achievements on the same line, with a / between them. Link each achievement ID to the achievement's page. 3. You must leave comments on set page for what you changed for log purposes 4. May not overlap with the required repair plan for DevQuest 2 or with any completion requirements for DQ13 5. TEST all changes. Ensure triggers appear when they should, and do not appear when they should not. Ensure the achievement can still trigger when expected. 6. Subscribe to tickets on the updated sets so you can catch any Trigger or Measured related tickets
	006	The Unwanted (Set Creation)	Develop a set for an unpopular system assigned to you at random • Eligible systems: PC Engine CD, Sega CD, 32X, Atari Lynx, Neo Geo Pocket/Neo Geo Pocket Color, Atari Jaguar, MSX/MSX2, Apple II, 3DO, ColecoVision, Intellivision, PC-8800/PC-8000, Atari 7800, Wonderswan/Wonderswan Color, Odyssey2, PC-FX, Amstrad CPC, Arduboy, WASM4, Nintendo DSi • No hacks or homebrew unless those are the only types of games left without sets. 1. Must be a full set, not just progression. Badges will be denied to those who make incomplete sets. 2. You may respin one time. Respins cannot occur until three months have passed since a wheel spin 3. Tasks are available to restore your respin. See the Wheel Respin Token Tasks for more details.
	007	Most Wanted (Set Creation)	Develop a set for one of the most requested games. Must be in RANews at the time of claiming it • If you already have one claimed when the game becomes eligible, you must be under 50% progress for it to count. • Any games listed in the console specific bonus section in RANEWS will only be eligible to be claimed in the month it was featured in but the set doesn't need to be released in the same month.
	008	World Traveler (Set Creation)	Develop two sets for games that never had an English release. • An English release is considered a game released in English in US, Canada, UK, or AU. 1. All claims intended for this quest must follow normal procedure. 2. They must be full sets. Fodder for the Progression Only hub won't count. 3. Sets intended for World Traveler do not stack with other quests based around developing new content. 4. English translation patches will not disqualify a game from this quest. 5. Hacks and homebrew do not count towards the quest. Unlicensed titles may count as long as they aren't blatant bootleg ports or hacks of another game. If you're unsure if a game is valid, ask! 6. If a game was released in English but was ported to another platform with no English version, half credit may be granted. 7. Games that only released in English on unsupported platforms will receive full credit.
	009	Launch Party! (Set Creation)	Develop a set for a newly supported console within 6 months of RA support • Must be a full set (to the extent of the games capabilities, See Watara vs PSP) Current Promotion Windows: • Neo Geo CD: 2023-11-15 through 2024-05-15
	010	It Takes Two (Set Creation)	Join forces with other developers to publish two collaboration sets 1. Set must have a fair share of the work done by each dev - Sets like Animal Crossing DS would not be approved. 2. Must be a full set covering every aspect of the game 3. Each Dev must publish at least 20 achievements each. 4. Achievements must make sense, no fluff to fulfill requirement. 5. Must Follow Dev CoC as per usual.
	011	The Genesis of RA! (Set Creation)	Develop a set for the Mega Drive/Genesis to celebrate the anniversary of RA's first achievement 1. All claims intended for this quest must follow normal procedure. 2. Must be full sets or a major/significant revision. 3. Sega CD and Sega 32X games are not eligible. 4. No prototypes or hacks. 5. Quest is available year round. 6. Collabs are allowed so long as the work is visibly split. 7. Not stackable with other quests and not retroactive!
	012	Hacker's Habit (Set Creation)	Create two new sets for robust hacks 1. Sets intended for this quest must be complete and encompass all notable content specific to the hack. 2. Acceptable hacks must be either complete overhauls that drastically change the level design, or introduce new mechanics that greatly change how you progress through the game. 3. Meme hacks, single-level hacks, and other small modifications aren't eligible. 4. You are limited to one point (full game credit) per franchise. Examples: If you create a set for a good-sized SMW hack for a full point credit, you can't do a Mario 64 hack for any points. If you do a small Mega Man 2 hack, you can get at most half credit for a Mega Man 3 hack, etc.
	013	complete.me (Revision)	Provide significant content to three sets that are progression-only or were demoted due to being incomplete. 1. Choose from a provided list or grab one from a hub, just make sure you let us know when you start so we can mark it! 2. Must go through the revision process as per usual! 3. Make sure you take care with the set and don't just throw in a bunch of filler 4. Don't hestitate to contact us with any questions or suggestion • This quest can be done multiple times (current limit: 3)
	014	Laudable Leaderboards (Set Creation)	Create leaderboards for 10 games that currently do not have any! • Cover different game modes/difficulties when applicable. • Try to cover leaderboards that make sense for the game. Some examples: - For Arcade-type games it is fine to just add High Score leaderboards, possibly highest in a single life - For Racing games time trials for tracks are pretty standard - Speedruns for Platformers - Minigames that track high scores or time are good candidates - And so on. Reach out if you have any questions about a specific game • You can do your own sets for half-credit as long as they were published prior to this DevQuest (2022-03-02) • Please leave comments on set page for what you added for log purposes
	015	Console Conqueror (Special)	Publish a set for every supported console on RetroAchievements • Each console ID will have an achievement associated with it. Newly supported console IDs means new achievements! • Contact us to opt-in to being tracked for this. There will generally be no need for reports. • The only requirement for an unlock is that you are the sole or majority developer of a set on that console ID. Collabs require at least 20 achievements made. For the more dire consoles, specific requirements are in the achievements themselves. • This DevQuest is 100% retroactive! Potential future revisions of your work will not count against you, so no worries about losing eligibility for an unlock.
	016	Wish This Set (Set Creation)	Publish a set for a game that has been featured in RANews' Wish This Set feature at any point in time and does not currently have a set in core. 1. All claims intended for this quest must follow normal procedure. Collabs are fine as long as both contribute equally to the set. 2. Must be full sets containing all content and challenges appropriate to the game. 3. The person that wrote the Wish This Set cannot be one of the devs making the set. 4. Quest is available year round, and gets new games eligible every release of RANEWS 5. If you already have one claimed at the time the set becomes elligible for this DevQuest you must be under 50% progress for it to count. 6. Once a game has been featured it remains eligible until the game gets a set. 7. This does not stack with any other quests.
	017	RA World Cup (Set Creation)	Publish 2 Sets for 2 different sports games, 1 must be a physical sport 1. That means both sets must be DIFFERENT SPORTS. You cannot do two baseball games, or two soccer games. 2. All claims intended for this quest must follow normal procedure. 3. This does not stack with any other quests. 4. Must be full sets containing all content and challenges appropriate to the game. 5. No Homebrew/Hacks/Unlicensed 6. New sets only: No Multi Set or Revisions 7. Other picks are subject to DQ team approval if they fall on the 50/50 line 8. Collaborations must be approved by the DevQuest team; games done via collaboration must have sufficient content or modes to justify qualifying.
	018	Subset Station (Set Creation)	Publish 2 Subsets 1. Read through Subsets document to learn more about subsets. 2. Subsets not approved by default always need Developer Compliance approval. Seek this by sending a DM to DevCompliance on the site. Include as much detail as possible explaining why it fits as a good subset idea. 3. If you are not the author of the core set for the game, you will need to pass a revision vote with your subset plan. This is in addition to any necessary Developer Compliance approval. 4. Subsets must be from two different games, but can be from the same series. 5. Subsets must be two different types of subsets (i.e.: Can't do two Bonus sets, Can't do two Professor Oak Challenges, etc) 6. A subset worked on at the same time as the core set is permitted, but only one of your subsets may be done this way. 7. If you are already working on a subset at the time this DevQuest goes live, you must be under 50% progress when informing the DQ Team for it to count.
	019	Wheel of Genres (Set Creation)	Develop a set from a specific genre or subgenre as determined by a spin on the Wheel of Genres! 1. You must have an open claim as you will need to claim your set 2. Must be a full set, not just progression. Badges will be denied to those who make incomplete sets. 3. Games chosen should have a decent amount of content. Small games like short hacks, homebrews, and demos may be rejected at the discretion of the DevQuest Team. If in doubt, ask when you ping to choose the game for the quest. 4. You may respin one time. Respins cannot occur until three months have passed since a wheel spin 5. Tasks are available to restore your respin. See the Wheel Respin Token Tasks for more details.
	020	Genre Conqueror (Special)	Publish a set for every genre! 1. You must opt in to this quest. Make a copy of the opt-in google sheet linked here and submit it to us to get started 2. This quest is awarded in sweeps; do not ping claims or completions. Any set will count as long as it meets the requirements, even if used for another DevQuest or if it was made while a Jr. Dev. 3. This DevQuest is 100% retroactive! Potential future revisions of your work will not count against you, so no worries about losing eligibility for an unlock. 4. Genres used for this quest are the main Genre hubs. We'll contact you to ask which genre is preferred. 5. If a set belongs to multiple top-level genres, we will ask you which genre to count for that set; if later on you do that same genre, you may ask us to reassign the set to the other genre. 6. Please fill out the Genre field in all sets for you wish to be credited and also assign it to the correct hub(s). Sets with unfilled Genre fields will be skipped. 7. Falsifying a genre or subgenre field will bar you from this DevQuest 8. Sole or Majority Dev will be credited. If it is a collaboration, you may also receive credit if you reach 20 achievements, even if not majority dev. 9. Excluded Genres: Other and Literature 10. Added Genre: Party and Minigame subgenres combined as Party or Minigames Genre
	020 Subset	Subgenre Conqueror (Special)	Publish a set for every subgenre! 1. You must opt in to this quest. Make a copy of the opt-in google sheet linked here and submit it to us to get started 2. This quest is awarded in sweeps; do not ping claims or completions. Any set will count as long as it meets the requirements, even if used for another DevQuest or if it was made while a Jr. Dev. 3. This DevQuest is 100% retroactive! Potential future revisions of your work will not count against you, so no worries about losing eligibility for an unlock. 4. Genres used for this quest are the Subgenre hubs. 5. If a set belongs to multiple subgenres, all will count. Exception: Compilations will only count for Subgenre - Compilation 6. Please fill out the Genre field in all sets for you wish to be credited and also assign it to the correct hub(s). Sets with unfilled Genre fields will be skipped. 7. Falsifying a genre or subgenre field will bar you from this DevQuest 8. Sole or Majority Dev will be credited. If it is a collaboration, you may also receive credit if you reach 20 achievements, even if not majority dev. 9. Excluded subgenres: 4X, Pachinko, Specific Extreme Sports subgenres (each will count towards Subgenre - Extreme Sports), subgenres of Board Games and Card Games (Each will count towards their Board Game or Card Game subgenre parent), Literature subgenres 10. Subsets will not count unless approved by DevQuest. Ping DevQuest team for approval request.
	021	Homebrew Heaven (Set Creation)	Publish three new sets for homebrew games! 1. Sets intended for this quest must be complete and encompass all notable content specific to the homebrew game. 2. Sets for homebrew systems (like WASM-4, Arduboy, and Uzebox) are worth half credit. 3. Collaborations are allowed. Credit will only be given to collaborators with 20 or more achievements in the set. At DQ Team suggestion, overly inflated sets may be disallowed. 4. Homebrew that is essentially the same as another you've done will not count (i.e. multiple Flappy Bird clones can only garner credit once) 5. One set per large homebrew collection maximum (i.e. One Net Yaroze 2014 Collection set allowed)

Suggestions

• If you have suggestions for a DevQuest, send a message to the DevQuest account with the following info:
  • Quest Name
  • Award Type - If there is one specific goal then you would want a badge-based award. If there are multiple goals then you would want an achievement-based award.
  • Game Type - State whether hacks, homebrews, prototypes, unlicensed, and/or subsets are allowed.
  • Goal(s) - A brief description of the DevQuest. Examples: "Develop a set for such-and-such console," "Develop a Holiday-Themed Set," "Create Dynamic Rich Presence for 10 Games," etc.
  • Rules - List any specific guidelines and criteria that submissions must meet. Is there a minimum achievement count? Are there minor exceptions that result in half-credit? Do submissions need to be pre-approved? The more simple they are, the better!