-
Notifications
You must be signed in to change notification settings - Fork 10
DevJam
The first DevJam is currently in-progress.
- Selected Console(s): Sega SG-1000
- Start Date: 2023-07-01
- Launch Date: 2023-09-30
- Basic Info
- Time and Duration
- Guidelines
- The Badge
- Point System
- Quarterly Goals
- FAQ
- Selected Console Stats
- DevJam List
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.
DevJams will take place quarterly. The first one started July 1st, 2023 with a launch date of September 30th, 2023, the second one will be October 1st, 2023 through December 31st, 2023, etc.
- 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, like rollouts, these will be limited to one 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. Sign-offs will also grant the event host(s) permission to promote your set(s) to core on the launch date if 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.
- Each participant may obtain up to 6 achievements per quarter. These can be split up and 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.
This table details earnable points for this quarter:
Points | Set Submission | Limit |
---|---|---|
2 | Licensed Games | 3 |
1 | Collaboration • 1 point per dev • Must be evenly split |
1 |
1 | Subsets, Homebrews, Unlicensed Games | 2 |
1 | Hacks, Prototypes, Demos | 1 |
1 | Early Claims • Claim must be less than a month old and remain in unofficial until launch |
1 |
1 | Late Submissions • Sets can still qualify up until the following DevJam's launch date! |
1 |
While the main goal is to simply promote a bunch of a sets, there are secondary goals that we can work on as a group. If a goal is met, bonus points will be applied to those who helped reach it. Current quarterly goals:
Point Value | Quarterly Goal | Details |
---|---|---|
2 | Double the amount of existing sets | 26 sets |
1 | Develop sets for all SG-1000 games with set requests | • Bomb Jack • Elevator Action • Flicky • QBert* • Rock N' Bolt • Sinbad Mystery • Yie Ar Kung-Fu • Yie Ar Kung-Fu II |
1 | Develop sets for all SG-1000 games released in 1983 | • Borderline • Safari Hunting • N-Sub • Mahjong • Champion Golf • Serizawa Hachidan no Tsume Shougi • • Yamato • Champion Tennis • Star Jacker • Champion Baseball • Sindbad Mystery |
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!
as of 2023-07-01 (start date)
- Current number of sets: 26
- 18 licensed games, 4 homebrews, and 4 unlicensed games.
- Current number of achievements: 660 worth 5912 points.
- Current number of leaderboards: 168
- Current number of open tickets: 0
Number | Quarter | Console(s) | Number of Participants | Sets Promoted |
---|---|---|---|---|
01 | Q3 2023 2023-07-01 - 2023-09-30 |
Sega SG-1000 | In Progress | In Progress |
02 | Q4 2023 2023-10-01 - 2023-12-31 |
TBA | TBA | TBA |
- 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