-
Notifications
You must be signed in to change notification settings - Fork 10
DevJam
DevJam is an ongoing developer event that is heavily inspired by our console rollouts: Developers sign up, get locked into developing sets for a specific console, get signed off once completed, and then we release all the sets at once on the launch date. However, with DevJam, the primary focus will be rollouts for supported consoles that did not get them. Some DevJams will focus on a single console. Others may focus on two consoles.
Once we "break even" and run out of consoles, the focus will shift to quarterly goals, completing sets for hubs, genre-specific crunch times, etc.
A DevJam lasts three months. Some will go on longer if the situation calls for it (Saturn had an extra month due to site outages and multiple dev events going on at the time). Some may be shorter if all claims are signed off.
- Notify the event host(s) when you make a claim!
- Sets claimed for the event will be marked as "Free Rollout" claims so they will not count against a developer's claim total. However, they will only be "free" during that quarter! Early and existing claims won't be marked as "free" until the start of the quarter. If a set isn't done in time for launch, it will become a standard claim. Also, like rollouts, devs can only have one free claim at a time!
- Once a set has been signed off, it will be marked as "Release Scheduled" and is to be promoted on the launch date.
- Event host(s) may request permission to promote your set(s) to core on the launch date in case you are unavailable.
- If a set is promoted early, it will be disqualified from DevJam. The developer may make another submission if they wish.
- The event badge consists of 24 achievements and each achievement will be unlocked for every point earned at the end of the quarter.
- There will be at least 6 earnable achievements per quarter. These can be split up, which allows for devs to take part in the event at their own pace, but will require some dedication. They could get 1 achievement in the first quarter, 3 in the second quarter, 2 in the third quarter, etc.
- Point values may vary between quarters depending on the console(s) selected.
- A chart detailing the current quarter's point system is at the bottom of this page.
Are late submissions still eligible for bonus points from Quarterly Goals?
- They wouldn't be quarterly goals then, would they? No.
Can I double-dip with DevQuest, CL100, and other events?
- Yes.
Will there be a second badge?
- If this goes well and there's enough demand for a 'Round Two' badge, sure.
Can Junior Devs participate?
- The nature of the event goes against several aspects of the Junior Dev program so as of now, no.
- Junior Devs may feel encouraged to rush a set.
- The promotion of Junior Dev sets is a big part of the process so having a set be "Release Scheduled" would waste a lot of time.
- Code Reviewers would need to work around the DevJam schedule.
- The amount of Junior Devs that end up losing the role due to inactivity or do 1-2 sets and disappear far outnumber those who stick around to get full dev. This could result in locked claims!
Check the links here for console-specific guidelines and info:
Number | Time | Console(s) | Number of Participants | Sets Promoted |
---|---|---|---|---|
01 | 2023-07-01 - 2023-09-30 | Sega SG-1000 | 30 | 60 |
02 | 2023-10-01 - 2024-01-31 | Sega Saturn | 28 | 56 |
03 | 2024-02-01 - 2024-04-30 | PC Engine/PC Engine CD | 28 | 60 |
04 | 2024-05-01 - 2024-07-31 | Arcade | TBA | TBA |
Solo Console DevJams:
- 3DO
- PC-8001/8801
- Apple II
- MSX
- Famicom Disk System
Multi-Console DevJams:
- Sega CD | Sega 32X
- Master System | Game Gear
- Neo Geo Pocket | WonderSwan | Atari Lynx
- Atari 2600 | Atari 7800 | Atari Jaguar
- ColecoVision | Intellivision
End of the Line for Console-Specific DevJams:
- "Bottom of the Barrel" (Pokemon Mini, Virtual Boy, Magnavox Odyssey2, PC-FX)
- "The Magnificent Seven" (Mega Drive, Nintendo 64, SNES, Game Boy, Game Boy Advance, Game Boy Color, NES)
- User Guidelines
- Developer Guidelines
- Content Guidelines
- FAQ
- Setup Guide
- Emulator Support and Issues
- Ways to Contribute
- RABot, the RA Discord Robot
- Events
- Overlay Themes
- Useful Links
- Contributing with the docs
- About Us
- Tutorials
- Developer Docs
- How to Become an Achievement Developer
- Getting Started as an Achievement Developer
- Game Identification
- Achievement Design
- Achievement Scoring
- Difficulty Scale and Balance
- Progression and Win Condition Typing
- Badge and Icon Creation
- Achievement Development Overview
- Flags
- BitCount Size
- Alt Groups
- Hit Counts
- Delta Values
- Prior Values
- Value Definition
- Condition Syntax
- Minimum Required Versions for Logic Features
- Memory Inspector
- Real Examples
- Set Development Roadmap
- Achievement Templates
- Tips and Tricks
- Leaderboards
- Rich Presence
- RATools
- Console Specific Tips
- Emulator Hotkeys for Developers
- libretro core support
- Docs To Do List
- WIP User Code of Conduct
- WIP CoC FAQ
- WIP Content Guidelines
- WIP-Jr
- WIP---Dev-Tips---Code-Notes-En-Masse
- WIP-‐-Reauthorship-Policy
- Manifesto RetroAchievements
- Código de Conduta do Usuário
- FAQ - Perguntas Frequentes
- Como contribuir se você não é um desenvolvedor
- Tutorial para Jogos Multi-Discos
- Introdução
- Primeiros Passos como um Desenvolvedor de Conquistas
- Recursos de Lógica para Achievements
- Exemplos Reais
- Dicas e Truques
- Dicas Específicas de Console
- Modelos de Achievement
- Escala de Dificuldade e Equilíbrio
- Roteiro de Desenvolvimento de um Set de Conquistas
- Criação de Ícones e Emblemas
- Leaderboards
- Rich Presence
- Design de Conquistas
- Manifesto RetroAchievements
- Código de Conducta del Usuario
- FAQ - Preguntas Frecuentes
- Tablas Globales y Reglas para la Casería de Logros
- Mi juego no esta cargando los logros
- Como contribuir si no eres un desarrollador
- Por que no deberías utilizar la función de cargar estado
- Contribuyendo con los documentos
- Como funciona la Documentación de RA
- Descargas
- Intro
- Código de Conducta del Desarrollador
- Como convertirme en un Desarrollador de Logros
- Primeros pasos como un Desarrollador de Logros
- Un vistazo al Inspector de Memoria
- Características en la Logica de un Logro
- Ejemplos Reales
- Intro
- Utilizando Hit Counts como un Temporizador
- Utilizando Valores Delta y Hit Counts para Detectar un Incremento
- Un Ejemplo Simple en como evitar el Abuso de Estados de Guardado
- Evitar el Problema de que un Contador se Incremente Dos Veces en el Mismo Frame
- Creando un Temporizador con un ResetIf Hits basándote en la Velocidad de un Juego
- Plantillas para Logros
- Tips y Trucos
- Escala de Dificultad y Balance
- Diseño de Logros
- Mapa de Desarrollo de Set
- Revisiones en Set de Logros
- Creación de Iconos y Badges
- Tablas de Clasificación
- Rich Presence
- Trabajando con el ROM apropiado
- Identificación del Juego
- Guía para Sets Bonus
- Logros para ROM hacks
- Tips Específicos por Consola