Azahar is an open-source Nintendo 3DS emulator that welcomes contributions from the community. Whether you want to improve the code, help translate the interface, or document game compatibility, there are multiple ways to get involved.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/azahar-emu/azahar/llms.txt
Use this file to discover all available pages before exploring further.
Code contributions
You can contribute code to Azahar by opening a pull request on GitHub. Before you start writing code, review the guidelines below to make sure your contribution is set up for success.Open a Feature Request issue first
If you are contributing a new feature, open a Feature Request issue on GitHub before writing any code. This lets maintainers confirm that the feature fits the project’s direction and prevents you from spending time on work that won’t be accepted.The Feature Request form asks you to describe what you want to add and explain why it would make Azahar better. Search existing issues first to avoid duplicates.
Write your changes
Follow the existing code style in the repository. A
.clang-format file is included at the repository root — use it to format any C++ code before committing.Open a pull request
When you open a pull request, confirm in the description that you have read the AI use policy and disclose any AI use if it applies under those terms.
Language translations
Azahar accepts language translations through Transifex. If you are fluent in a non-English language that is already listed on the Transifex page, you can contribute translations directly.Azahar is not currently accepting new languages or language variants. Do not request additions for languages that are not already listed on the Transifex project page.
Compatibility reports
You do not need to write code to contribute to Azahar. Reporting game compatibility data is a valuable way to help other users understand what the emulator can run and how well. To submit a compatibility report, read the CONTRIBUTING.md file in the azahar-emu/compatibility-list repository and follow the instructions there. Submitting a report after you complete a game is especially appreciated, as it keeps the list current.Bug reports
If you encounter a bug, file a Bug Report issue on GitHub. Tech support questions do not belong in the issue tracker — only report something if you believe it is a genuine bug in Azahar.What to include in a bug report
What to include in a bug report
A complete bug report requires the following information:
- Affected build(s): The build number where you observed the issue.
- Description of the issue: A brief explanation of what went wrong, including any screenshots or video if relevant.
- Expected behavior: What you expected to happen instead.
- Reproduction steps: A step-by-step explanation of how to reproduce the issue. A save file that triggers the bug is helpful if you can provide one.
- Log file: Attach an Azahar log file. Logs help maintainers diagnose and fix issues faster.
- System configuration: Your CPU, GPU and driver version, RAM, and operating system. If you are on Linux, note whether you are using the Flatpak or AppImage build.
What to include in a feature request
What to include in a feature request
A feature request requires two things: a description of the feature you are suggesting and an explanation of why it would make Azahar better.Search existing issues before filing a new one. If a discussion for your idea already exists, add your input there rather than opening a duplicate.
AI use policy
Azahar has an explicit policy on the use of large language models (LLMs) such as ChatGPT, Claude, and DeepSeek in contributions. This policy applies to all code submitted on or after March 20, 2026.Acceptable uses of AI
Acceptable uses of AI
- Using AI to help you discover or understand problems in the codebase, provided you independently verify any finding yourself before acting on it.
- Using AI to write small, generic code snippets (up to approximately 5 lines) that are not reasonably copyrightable, with disclosure in your pull request description. Maintainers evaluate these cases individually.
Prohibited uses of AI
Prohibited uses of AI
- Submitting AI-written code without disclosure.
- Using AI to write the entirety or a significant portion of a contribution.
- Using AI to write code snippets large enough to be reasonably copyrightable.
- Using AI to rewrite incompatibly-licensed code for submission to Azahar.
- Using AI to autonomously submit pull requests or issues on your behalf.