-
Notifications
You must be signed in to change notification settings - Fork 10
Badge and Icon Creation
Badges and Icon are used across the site, and are a good way to represent achievement in the game.
Badges are the images for the achievements of a game. They are stored on site in the following manner and place: i.retroachievements.org/Badge/00136.png; the number coincidences with the badge ID found in the Achievement editor.
Icons are stored on the site in the following manner and place: i.retroachievements.org/Images/000705.png, stored in the same folder as other game images such as the game box and game screenshots.
When uploaded, your file is converted into the following:
- 64x64 32-bit colour PNG
- 64x64 greyscale and blurred PNG
It's not entirely important how the file is formatted before uploading, but as long as it's square, the file will upload and be converted pretty easily. Naturally it is important not to break any copyright law, or upload anything vulgar, offensive or pornographic, with the possible consequences of being cautioned, potentially reported and potentially removed from RetroAchievements.
When uploaded, your Icon images are reduced to a maximum 96x96 32-bit colour PNG. If you upload an Icon that is smaller than 96x96 the image uploaded will retain it's original size.
Places and sizes Icons are displayed:
- On leaderboards: 96x96
- Game Pages: 64x64
- User Pages: 48x48
- Currently Playing and Global Feed: 32x32
Same thing as with badges, the actual image is not being resized only the display size, if you use android or increase your browser zoom you will see the images more clearly.
-
Uploaded images for badges should be square, as an equal number of x & y, otherwise the resulting image will be distorted and ugly.
-
It's recommended to make Badges at 64x64 for sharpest clarity. Icons should be made in a way that the subject is clear even when sized at 32x32.
-
Badges should refer in some way to what the achievement is about, i.e. a picture of the boss, level or collectible that the achievement requires the player to get to.
-
In the cases of low-resolution games' achievements, it can be hard to get a badge looking good without it looking blocky or blurry, in these cases the blocky look is often preferable, so that the images have a retro feel to them.
As the site does not in most cases have a permanent changelog/git-style-rollback/wiki-style-rollback for all actions taken on a set it's recommended that when a developer makes changes of any kind to a set that they make a note of it in the forum for that game.
Taking this into account, in relation to badges, post in the Game's forum page one of the following:
- leaving an old copy of the badge in the game thread (example:
[img="http://retroarchievement.org/badge/1234]
) - annotating the old badge ID (number displayed on the badge image's URL)
is recommended, to help keep everything orderly so that in cases when rollbacks or change backs are appropriate it is much easier to do them.
- 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