gen1 recomp gbc: Native Setup Guide for Gen 1 ROMs

Gen1 Recomp is a native recreation of the original Pokémon Generation I experience, commonly described as a Pokémon Gen 1 recomp or PC port. It uses a handwritten Lua and LÖVE2D engine instead of emulating the Game Boy hardware or directly transpiling the original assembly code.

The application does not include Nintendo game files. You must provide game data from a legally owned Pokémon Red, Pokémon Blue, or Pokémon Yellow cartridge. The project supplies the engine and supporting tools, while the player supplies the compatible ROM data.

The “GBC” wording in searches can point toward the broader Game Boy family, but the important setup requirement is the supported Gen 1 game version. Check the release notes if a particular build changes ROM detection or platform compatibility.

Start with the official release page rather than a reposted package. As of August 5, 2026, the reference materials identify v0.1.69 as the latest release, published on August 4, 2026. Always read the release notes because package names, platform support, and upgrade instructions can change.

Choose a normal release asset that matches your operating system and processor. A source-code archive is not the same as a ready-to-run player package. Extract desktop archives completely before launching them so libraries, data files, and folders remain beside the executable.

Keep the original installation until the new build has launched successfully. This makes it easier to compare settings, restore saves, or identify whether an update introduced a compatibility problem.

Gen1 Recomp includes a mod workflow through its built-in Mod Manager. Install packages made specifically for Gen1 Recomp; a conventional emulator patch, ROM hack, or mod from another recompilation project is not automatically compatible.

Import one package at a time and read its version notes. Preserve the original ZIP structure when the manager expects a packaged archive. An extra folder level or altered metadata file can stop the manager from detecting the mod correctly.

DramaticShape Voxel Mod is a separate community project, not a standard feature that should be treated as part of the unmodified base application. It adds a voxelized 3D interpretation of Kanto, configurable camera modes, 3D battle presentation, performance options, and experimental viewpoints when supported by the installed versions.

When several packages edit the same system, load order can affect which change takes priority. Place required frameworks before the content that depends on them, and follow the author’s recommended order when available.

For voxel play, begin with the standard camera and default graphics settings. Test outdoor maps, indoor maps, doors, stairs, battles, and menus before trying experimental first-person or close-camera features. Lower render distance, lighting, shadows, or effects if performance drops.

Gen1 Recomp stores save data separately from the original ROM. The exact location depends on the operating system and LÖVE application-data behavior, so identify the active user-data folder before making progress on a long playthrough.

Back up saves before installing a new release, changing major mods, using the Save Editor, or starting a trade. Keep backups outside the installation directory and name them with a date or version so you can identify the last known-good copy.

The built-in Save Editor can manage party Pokémon, PC boxes, items, Pokédex records, and event flags. Make small changes, save, and test them in the game before applying additional edits. Invalid or inconsistent values can prevent a save from loading correctly.

Link Play uses a direct UDP connection for Pokémon battles and trades. Both players should use the same Gen1 Recomp release, compatible game versions, and matching gameplay-changing mods. The host shares an address and UDP port, while the joining player enters those details in the Link Play interface.

For internet sessions, the host may need router port forwarding and a firewall rule for the selected UDP port. Test on the same local network first. If a connection succeeds locally but fails online, check the public address, router rule, VPN, carrier network, and active firewall profile.

Most setup errors can be narrowed down by returning to a minimal configuration. Close Gen1 Recomp, disable every mod, and confirm that the clean base application launches with the supported ROM. Then restore one variable at a time.

A ROM rejection can result from an unsupported version, a modified file, an incomplete dump, or a release-specific detection requirement. Keep an untouched backup of your own ROM and test the clean file without renaming it repeatedly.

When reporting a problem through GitHub Issues, include the operating system, Gen1 Recomp version, enabled mods, reproduction steps, and whether the unmodded build works. Do not upload copyrighted ROM files or unrelated personal data.

The official project community is listed through the repository and its published Discord information. The reference materials specifically caution that gen1recomp.com is not an authorized project site, so treat unofficial download pages as untrusted sources.

The safest workflow is straightforward: use an official release, provide compatible legal game data, test the unmodded build, back up saves, and add tools or mods gradually. This approach keeps the native Gen 1 experience easier to maintain across desktop, Android, and supported handheld environments.