Skip to main content

​
Get Involved

Hydra is an open-source project that thrives on community involvement. Whether you’re looking for help, want to report a bug, or interested in contributing, there are several ways to engage with the project.

​
Community Resources

GitHub Repository

View source code, report issues, and contribute to development on the official repository

Discord Server

Join the official Discord for real-time discussions, support, and development updates

GitHub Issues

Report bugs, request features, and track known issues

GitHub Releases

Download the latest stable release and view changelog

​
Getting Help

If you’re experiencing issues or have questions about Hydra:

​
Discord Community

The Discord server is the best place for:
  • Quick questions and troubleshooting
  • Real-time support from community members
  • Development discussions
  • Feature suggestions and feedback
  • Casual conversation about Switch emulation

​
GitHub Discussions

For longer-form discussions, use GitHub:
  • General questions about usage
  • Configuration help
  • Sharing tips and tricks
  • Compatibility reports
  • Technical discussions

​
Documentation

Before asking for help, check the documentation:

​
Reporting Bugs

Found a bug? Your reports help improve Hydra for everyone.

​
Before Reporting

1

Search Existing Issues

Check if someone has already reported the same issue on GitHub Issues
2

Verify the Issue

Ensure you’re using the latest version and that the issue is reproducible
3

Gather Information

Collect relevant details: error messages, logs, system specs, and steps to reproduce

​
Creating a Bug Report

When opening a new issue, include:
  • macOS version (e.g., macOS 14.0 Sonoma)
  • Hardware specs (CPU, GPU, RAM)
  • Mac model (e.g., MacBook Pro M2, iMac Intel)
  • Hydra version or commit hash
  • Build configuration (SDL3 or SwiftUI frontend)
  • Installation method (release binary or built from source)
  • Clear description of the problem
  • Expected behavior vs. actual behavior
  • When the issue occurs (startup, during gameplay, etc.)
  • Step-by-step instructions to reproduce the issue
  • Specific game or homebrew app affected
  • Configuration settings used
  • Error messages or crash logs
  • Screenshots or videos demonstrating the issue
  • Related issues or similar problems

Report a Bug

Open a new issue on GitHub to report bugs and compatibility problems

​
Contributing

Contributions are very welcome! Whether you’re a developer, designer, or documentation writer, there are many ways to contribute.

​
Ways to Contribute

Code Contributions

Submit pull requests with bug fixes, new features, or performance improvements

Testing

Test games and report compatibility issues with detailed information

Documentation

Improve documentation, write guides, or translate content

Community Support

Help other users on Discord or GitHub Discussions

​
Development Workflow

  1. Fork the Repository Fork SamoZ256/hydra to your GitHub account
  2. Clone Your Fork 
    git clone https://github.com/YOUR_USERNAME/hydra.git
cd hydra
git submodule update --init --recursive
  3. Create a Branch 
    git checkout -b feature/your-feature-name
  4. Make Your Changes Write code, add tests, and update documentation as needed
  5. Test Your Changes Build and test locally to ensure everything works: 
    cmake . -B build -G Ninja -DMACOS_BUNDLE=ON
ninja -C build
  6. Commit and Push 
    git add .
git commit -m "Description of your changes"
git push origin feature/your-feature-name
  7. Open a Pull Request Go to the original repository and open a pull request from your branch

​
Contribution Guidelines

While there’s no formal CONTRIBUTING.md file in the repository, following these best practices will help your contributions get accepted:
  • Code Quality: Write clean, readable code following the project’s style
  • Testing: Test your changes thoroughly before submitting
  • Documentation: Update docs if you add or change features
  • Commit Messages: Write clear, descriptive commit messages
  • Discussion: For major changes, discuss on Discord or GitHub first
  • Pull Requests: Keep PRs focused on a single issue or feature

​
Getting Started with Development

New to Hydra development? Start here:
  1. Read the Building from Source to set up your build environment
  2. Browse open issues for beginner-friendly tasks
  3. Join the Discord server to ask questions
  4. Review existing pull requests to understand the review process
  5. Start with small improvements or bug fixes to get familiar with the codebase

​
Project Information

​
Repository

SamoZ256/hydra - Official GitHub repository

​
Statistics

  • Stars: 379+ on GitHub
  • License: GPL-3.0 (GNU General Public License v3.0)
  • Platform: macOS only
  • Status: Experimental / Early Development

​
License

Hydra is released under the GPL-3.0 license. This means:
  • You can freely use, modify, and distribute the software
  • Any modifications must also be released under GPL-3.0
  • The software is provided as-is with no warranty
  • See the full LICENSE for details
Tools that complement Hydra:

hydra-patches

Game patches required to prevent crashes in official games

switch-extract-macos

Convert NSP to NCA and decrypt firmware files

herakles

Convert NSP files to NX format

​
Stay Updated

Keep up with the latest Hydra developments:
  • Watch the repository on GitHub for notifications
  • Star the project to show support and stay informed
  • Join Discord for immediate updates and announcements
  • Check Releases for new versions and changelogs
Remember: Hydra is experimental software. Expect bugs, crashes, and frequent changes. Always use the latest version for the best experience.

​
Code of Conduct

When participating in the Hydra community:
  • Be respectful and constructive
  • Help others when you can
  • Follow Discord and GitHub community guidelines
  • Report issues professionally with helpful details
  • Credit others for their contributions
  • Focus on improving the emulator for everyone
Thank you for being part of the Hydra community!

Build docs developers (and LLMs) love

Get started for freeTalk to us