- gen1 recomp is a native Lua/LÖVE2D recreation, not a traditional Game Boy emulator.
- Official releases are published through the Gen1 Recomp GitHub repository and Releases page.
- ROM requirement: import a legally owned Pokémon Red, Blue, or Yellow ROM.
- Safe updates: back up saves, settings, and mods before replacing an installation.
- Mod caution: test the unmodified base program before adding community content.
gen1 recomp Download and Release Basics
gen1 recomp recreates Pokémon Red, Blue, and Yellow through a handwritten Lua engine powered by LÖVE2D. The project uses data extracted from a player-provided, legally owned ROM, but it does not distribute Nintendo game files. It is best understood as a native PC recreation or static recompilation-style project rather than an emulator or an assembly-code transpiler.
The safest starting point is the official Gen1 Recomp GitHub repository and its GitHub Releases page. Avoid unofficial mirrors, modified download pages, and sites presenting themselves as authorized project portals.
As of August 5, 2026, the supplied project information identifies v0.1.69, released on August 4, 2026, as the latest release. Always read the release notes before installing because package names, platform support, and upgrade instructions can change.
| Item | Recommended source or choice | Important note |
|---|---|---|
| Project repository | Official GitHub repository | Use it for documentation, issues, and project status |
| Latest build | GitHub Releases | Select the package matching your operating system and processor |
| Supported games | Pokémon Red, Blue, or Yellow | Use a legally owned, clean ROM dump |
| Engine | Lua and LÖVE2D | This is a native recreation, not a traditional emulator |
| Community support | Official Discord listed by the repository | Confirm the current invite through the repository |
Official Repository
Use the project repository for source information, documentation, issue reports, and links to approved community channels.
Release Assets
Download a normal platform release instead of a source-code archive unless you specifically need development files.
Legal Game Data
Provide your own supported Red, Blue, or Yellow ROM. The application does not include copyrighted game data.
Update Notes
Check each release page for known issues, changed files, compatibility notes, and save-preservation guidance.
The project information states that gen1recomp.com is not an official or authorized download source. Prefer the GitHub repository and the Discord link published there.
Step-by-Step Installation and First Launch
The installation process is similar across supported systems: obtain the correct official asset, keep its folder structure intact, launch the native application, and import your own game data. Complete the base setup before installing mods or changing advanced settings.
Open the Official Releases Page
Select the newest stable release from the official GitHub Releases page. Match the asset to Windows, macOS, Linux, Android, or another supported target. Do not confuse a source archive with a ready-to-run player build.
Extract or Install the Complete Package
Extract desktop archives into a writable folder and keep the executable beside its included libraries and data folders. On Linux, mark an AppImage or executable package as runnable when required. On Android, install the official APK asset and grant only the file permissions needed for setup.
Import a Supported ROM
Start the application and select a clean, legally owned Pokémon Red, Blue, or Yellow ROM when prompted. Choose the matching version and wait for the first import to finish before closing or moving files.
Verify the Unmodified Game
Confirm that the title screen, menus, audio, movement, and an initial save work correctly. Test this base configuration before adding visual, gameplay, interface, or voxel modifications.
| Platform | Package choice | First-launch consideration |
|---|---|---|
| Windows | Official Windows archive | Extract the full folder before opening the executable |
| macOS | Official macOS bundle or archive | Finder may require Control-click, then Open |
| Linux | Linux archive, executable, or AppImage | Check executable permissions and missing libraries |
| Android | Official Android APK | Enable temporary installation permission and use the file picker |
| Steam Deck or Linux handheld | Linux build | Desktop Mode is useful for initial file management |
| Windows handheld | Standard Windows build | Review controller mapping and small-screen layout |
Create a normal in-game save before installing any mod. This gives you a clean recovery point if a package, configuration change, or update causes problems.
The project outline also identifies builds or targets for macOS, iOS, RG34XXSP, and Switch. Availability and installation details may differ by release, so use the current official asset and notes rather than assuming that every target has the same package format.
Platform Compatibility, Saves, and Controls
Gen1 recomp is designed to provide a native experience across desktop, mobile, and selected handheld environments. The most important compatibility factors are the release package, the operating system, controller support, file permissions, and the location of application data.
| Platform group | Input methods | Save and file considerations | Common limitation |
|---|---|---|---|
| Windows | Keyboard, controller | User-data folder managed by the application | Security warnings may appear for unsigned community software |
| macOS | Keyboard, USB or Bluetooth controller | User Library application-support data | Gatekeeper may require first-launch approval |
| Linux | Keyboard, SDL-compatible controller | User data commonly stored under a local share path | Permissions and libraries vary by distribution |
| Android | Touch, Bluetooth, USB controller | App-specific storage and Android file picker | Uninstalling may remove locally stored data |
| Handheld systems | Built-in controls, Steam Input, touchscreen | Depends on the underlying Windows or Linux build | File selection and remapping may require extra setup |
Controls should be reviewed before a long play session. Confirm movement, confirm, cancel, Start, and Select independently. These original Game Boy menu functions remain important even when the program is played with a modern keyboard or controller.
Display settings are equally practical. Use a readable window size, verify that dialogue boxes fit on screen, and try windowed mode if fullscreen creates scaling or driver issues. For pixel clarity, integer or pixel-correct scaling is generally preferable when the build offers that option.
First-Launch Checklist:
- Use an untouched backup of your legally owned Red, Blue, or Yellow ROM
- Confirm the downloaded package matches your operating system
- Extract the complete desktop archive before launching
- Test movement, menus, audio, and an initial save
- Back up user data before updates or major mod changes
| Configuration area | Safe starting choice | Why it matters |
|---|---|---|
| Controls | Default bindings, then remap | Confirms the build recognizes input correctly |
| Display | Windowed or standard fullscreen | Simplifies troubleshooting |
| Scaling | Pixel-correct or integer scaling | Keeps the original-style image sharper |
| Game speed | Normal speed first | Helps separate timing issues from setup problems |
| Save management | External backup copy | Protects progress during updates and edits |
Keep save backups outside the installation directory. Before updating, changing major mods, or using the Save Editor, copy the complete active save and user-data folders to a dated backup location.
Mods, Mod Manager, and Voxel Features
The base project includes an integrated mod platform and Mod Manager, while the DramaticShape Voxel Mod is a separate community project. Treat these as different layers: first stabilize the native recreation, then add compatible modifications one at a time.
| Content type | Status | Recommended handling |
|---|---|---|
| Built-in Mod Manager | Built-in feature | Use it to import, enable, disable, and review compatible packages |
| Standard community mod | Community content | Check its target release, game version, dependencies, and load order |
| DramaticShape Voxel Mod | Separate community project | Follow its repository instructions and match the supported base version |
| All 151 without trading | Mod or project-specific claim | Do not assume it is part of the base application |
| Female protagonist or Gen 2 graphics | Mod-specific claim | Label as a mod only when a reliable project page confirms it |
A compatible mod should target Gen1 Recomp specifically. A conventional emulator patch, ROM hack, or modification made for another recompilation project is not automatically supported. When a ZIP package is expected, preserve its internal structure and avoid placing one archive inside another.
Check Compatibility
Read the mod’s target Gen1 Recomp version, supported game versions, dependencies, and installation notes.
Import the Package
Open the built-in Mod Manager and import the prepared package. Confirm that its name, version, and metadata appear correctly.
Enable One Change
Enable one mod, restart if requested, and test the title screen, a save, movement, and any affected feature.
Manage Load Order
Place framework or dependency packages before content that relies on them. Follow the author’s recommended order when multiple mods alter the same system.
Recover if Needed
Disable the newest package first. If the base game launches normally, re-enable mods individually until the conflicting package is identified.
For the DramaticShape Voxel Mod, verify the unmodded game first, back up saves, and then test the voxel overworld before enabling experimental camera modes, 3D battles, or optional model support. Voxel rendering can require more graphics performance than the standard presentation.
Gameplay, map, script, Pokémon, move, and battle-rule changes can affect saves or link play. For multiplayer testing, use matching Gen1 Recomp versions and compatible mod sets on both systems.
Troubleshooting and Safe Updates
Most setup problems can be narrowed down by returning to a minimal configuration. Test the latest official build without mods, use a clean supported ROM, verify the save location, and then restore optional features one at a time.
| Symptom | Likely area | Recommended action |
|---|---|---|
| Application will not launch | Incomplete extraction or permissions | Re-extract the full package and check executable permissions |
| ROM is rejected | Unsupported or modified game data | Test a clean, legally owned Red, Blue, or Yellow ROM |
| Save is missing | Wrong user-data directory | Confirm the active application-data location and restore a backup |
| Game crashes after mod install | Conflict or outdated package | Disable the newest mod and test the base application |
| Controller does not respond | Platform mapping | Open controls and remap every required action |
| Link Play times out | UDP, firewall, or address | Match the host port, permit the application, and test locally first |
| Android data disappears | App-specific storage or uninstall | Export saves before replacing or removing the APK |
Use the official GitHub Issues page for repeatable technical problems. Include your operating system, release version, reproduction steps, and relevant configuration details. Do not upload copyrighted ROM files.
Before installing a new release, preserve the working setup. Install the new build separately when practical, test it without mods, confirm that the ROM and save load correctly, and only then restore compatible packages.
| Update stage | Action | Result to confirm |
|---|---|---|
| 1. Backup | Copy saves, settings, and mods | Backup opens or remains available outside the install folder |
| 2. Install | Use the correct official release asset | New build starts without optional mods |
| 3. Import | Select the supported ROM again if requested | Correct Red, Blue, or Yellow title appears |
| 4. Test | Load a save and check controls | Progress, menus, audio, and movement work |
| 5. Restore | Add compatible mods individually | Stable profile returns without duplicated packages |
When reporting a problem, provide the release version and platform, describe repeatable steps, and explain whether the base application works with all mods disabled.
Recommended Setup Path and FAQ
A reliable setup path is intentionally conservative: official release, clean game data, base-game test, save backup, then optional tools and mods. This order reduces the number of variables when something goes wrong and makes future updates easier to manage.
| Setup path | Priority | Reason |
|---|---|---|
| Official release | Required | Reduces the risk of modified or incomplete packages |
| Clean ROM import | Required | Establishes a supported data source |
| Base-game save | Required | Provides a recovery point |
| Controls and display | High | Prevents avoidable input and visibility issues |
| Mod Manager profile | Optional | Adds community content after the base is stable |
| Voxel presentation | Optional | Requires extra compatibility and performance testing |
| Save Editor | Advanced | Can change persistent data and should use backups |
| Link Play | Optional | Needs matched versions, saves, network settings, and mod profiles |
Q: Is gen1 recomp an emulator?
No. It is a native recreation built with a handwritten Lua engine and LÖVE2D. It uses data extracted from a legally owned supported ROM rather than emulating the Game Boy hardware in the traditional way.
Q: Which games can I import?
The supplied project information identifies Pokémon Red, Blue, and Yellow as supported versions. Use a clean ROM dump from a copy you legally own, and keep an untouched backup.
Q: Where should I download gen1 recomp?
Use the official GitHub repository and its Releases page. The project information specifically warns that gen1recomp.com is not an official or authorized download source.
Q: Can I use mods and Link Play together?
Potentially, but both players should use the same Gen1 Recomp release, compatible game versions, matching mod versions, and the same relevant load order. Disable gameplay-changing mods when troubleshooting synchronization.
Start with the unmodified release, create a working save, and document your stable version before experimenting with the Mod Manager, Save Editor, Voxel Mod, or Link Play.