- Gen1 recomp gameplay uses a native Lua and LÖVE2D recreation rather than a traditional emulator.
- Supported games include legally owned Pokémon Red, Blue, and Yellow ROM data.
- Best first step is testing the unmodded game before changing graphics, controls, or gameplay systems.
- Save safety depends on backing up user data before updates, Save Editor changes, and major mods.
Gen1 Recomp Gameplay Basics and First Launch
Gen1 recomp gameplay recreates the original Pokémon Red, Blue, and Yellow experience through a handwritten Lua engine powered by LÖVE2D. It does not emulate the Game Boy hardware or distribute the original ROM files. You provide game data from a legally owned copy, then use the native application to explore Kanto, battle, trade, save, and customize the experience.
The safest starting point is a clean, unmodified ROM dump. Keep that file separate from the application folder and retain an untouched backup. A clean baseline makes it easier to identify whether a problem comes from the ROM, the application, or a later mod.
Native Recreation
Lua and LÖVE2D power the engine. The project is not a conventional emulator or an assembly-code transpilation.
Three Versions
Choose supported data from Pokémon Red, Blue, or Yellow during the initial setup process.
Built-In Tools
The project includes a Mod Manager, Save Editor, and direct Link Play features.
Community Expansion
Visual projects such as the DramaticShape Voxel Mod are separate from the base application.
Gen1 Recomp does not provide copyrighted ROM data. Use only game data extracted from a copy you legally own, and never download ROMs from unofficial reposting sites.
Open the Official Release Page
Use the official GitHub repository and its GitHub Releases page. Select a normal release asset instead of a source-code archive, then match the package to your operating system and processor.
Extract or Install the Complete Package
Windows, macOS, Linux, and handheld users should preserve the original folder structure. Do not launch from inside a compressed ZIP file, and do not separate libraries or data folders from the executable.
Import Supported Game Data
Start the application and select the legally owned Red, Blue, or Yellow ROM when prompted. Allow the first import to finish before closing the program or moving the file.
Test the Unmodded Game
Reach the title screen, start a new game, verify movement and menus, then create an initial save. Only after this baseline works should you install mods or experimental visual features.
| Setup Check | Recommended Action | Why It Matters |
|---|---|---|
| Release source | Use GitHub repository and Releases | Reduces the risk of modified or unofficial packages |
| ROM file | Use clean Red, Blue, or Yellow data from your own copy | Improves compatibility testing |
| First launch | Test without mods | Establishes a reliable baseline |
| Save test | Create and reload an initial save | Confirms the user-data path works |
Platforms, Controls, and Display Settings
Gen1 Recomp supports several operating environments, but the exact release asset and input method depend on the platform. Desktop builds generally offer the easiest file management, while Android and handheld systems may require extra permission or controller configuration.
| Platform | Release Asset | Input Options | Main Limitation |
|---|---|---|---|
| Windows | Official Windows archive | Keyboard, controller | Security warnings may appear for unsigned community software |
| macOS | Application bundle or archive | Keyboard, Bluetooth, USB controller | Gatekeeper may require a manual first-launch approval |
| Linux | Archive or executable package | Keyboard, SDL-compatible controller | Permissions and system libraries vary by distribution |
| Android | Official APK | Touch, Bluetooth, USB controller | Sideloading and storage permissions may be required |
| Steam Deck/Linux handheld | Linux build | Built-in controls, Steam Input, touchscreen | Desktop Mode is usually easier for initial file setup |
| Windows handheld | Standard Windows archive | Built-in controller, touchscreen, keyboard | Manual button mapping may be needed |
Configure movement, confirm, cancel, Start, and Select before beginning a longer play session. Test every binding inside menus, not only while walking.
The original Game Boy layout makes Start and Select important for menus and utility functions. A comfortable control profile should separate confirm and cancel inputs, especially when using a modern controller with unfamiliar button labels.
Display settings should prioritize readable menus and stable frame pacing. Integer or pixel-correct scaling is useful when available because it keeps the original pixel art sharp. If fullscreen creates stretching, flicker, or cropped dialogue, return to windowed mode and adjust the size gradually.
| Setting | Starting Choice | Adjustment Rule |
|---|---|---|
| Window mode | Windowed during setup | Switch to fullscreen after confirming stable rendering |
| Scaling | Integer or pixel-correct | Use another mode only if the image is too small |
| Audio | Moderate music and effects | Adjust separately for dialogue and battle clarity |
| Game speed | Normal speed first | Use fast-forward after confirming saves and timing |
| Controller | Default mapping | Remap Start, Select, confirm, and cancel manually |
| Voxel graphics | Disabled initially | Enable only after standard gameplay is stable |
Android builds use app-specific storage, while Linux and desktop versions use user-data directories associated with LÖVE. Back up saves before reinstalling or replacing an application package.
Core Gameplay Routine and Safe Progression
Once the first launch works, the standard Pokémon loop remains familiar: explore routes and towns, manage a party, battle trainers, collect items, progress through story events, and save regularly. The native recreation adds modern convenience through configurable controls, game-speed options, mod support, and additional management tools.
| Gameplay Task | Safe Routine | Common Mistake |
|---|---|---|
| Exploration | Use normal speed around doors, stairs, and scripted areas | Leaving fast-forward active during timing-sensitive events |
| Battles | Confirm party and move inputs before accelerating | Testing an unverified mod during an important battle |
| Story events | Save before entering major locations | Editing event flags without a backup |
| Pokémon storage | Check party and PC box capacity | Creating incomplete or duplicate records in the editor |
| Link Play | Match versions and active mods | Connecting with different gameplay systems enabled |
A reliable session flow is simple:
- Save normally before installing or disabling a major mod.
- Test new settings in a low-risk area.
- Keep fast-forward available for repeated movement or battles, but return to normal speed when diagnosing a bug.
- Avoid changing the ROM file after it has been imported.
- Close active Link Play sessions before opening the Save Editor.
The most dependable profile is clean ROM data, a tested base installation, one normal save, and mods added individually after the baseline is confirmed.
The built-in Save Editor can manage party Pokémon, PC boxes, items, Pokédex records, and event flags. Treat it as a recovery and customization tool rather than a substitute for backups. Small, isolated edits are easier to validate than changing several connected systems at once.
The direct Link Play feature supports battles and trades through a peer-to-peer network session. Both players should use the same Gen1 Recomp release and compatible game data. Gameplay-changing mods should also match, because different Pokémon, moves, maps, scripts, or battle rules can interrupt synchronization.
| Link Play Requirement | Host and Guest Should Match |
|---|---|
| Application | Same Gen1 Recomp release |
| Game data | Compatible Red, Blue, or Yellow version |
| Mod profile | Same gameplay-changing mods and load order |
| Network | Correct address and UDP port |
| Save state | Normal save completed before connecting |
For internet hosting, the selected UDP port may need router forwarding and firewall permission. Local network testing is a practical first step because it removes some address and port-forwarding variables. After a trade or battle, return to normal gameplay and create an in-game save.
Mods, Voxel Graphics, and Save Protection
Gen1 Recomp includes an integrated Mod Manager for compatible community packages. A mod designed for an emulator, a standard ROM hack, or another recompilation project is not automatically compatible. Check the target project, supported game version, required base release, dependencies, and installation format before importing anything.
Do not enable several unknown mods at once. Import one package, test it, and keep a backup before adding another change that affects scripts, maps, Pokémon data, battles, or saves.
The DramaticShape Voxel Mod is a separate community project layered over Gen1 Recomp. It can provide voxelized 3D environments, configurable camera modes, 3D battle presentation, and experimental first-person or close-camera features. These options require more graphics processing than the standard presentation.
A safe voxel workflow is:
- Confirm the unmodded Gen1 Recomp build reaches the title screen.
- Back up saves, settings, and the existing mod profile.
- Download the prepared package from the DramaticShape Voxel Mod repository.
- Import it through the Mod Manager and follow its required version notes.
- Test outdoor maps, indoor maps, transitions, collisions, menus, and battles.
- Reduce render distance, effects, shadows, or related settings if performance drops.
- Enable experimental camera modes only after the standard voxel view works correctly.
Before Updating or Editing:
- Back up the complete save and user-data folders
- Record the installed Gen1 Recomp version
- Save a copy of the active mod list and load order
- Test the unmodded application if troubleshooting
- Keep the original ROM backup unchanged
For Save Editor changes, verify the trainer name, game version, party, and current progress before editing. When changing Pokédex data, keep Caught entries consistent with Seen entries. When changing event flags, edit only the specific group needed and test nearby NPCs, doors, encounters, or scripted sequences afterward.
| Save Area | Safer Editing Practice |
|---|---|
| Party Pokémon | Use valid species, moves, and complete slot data |
| PC boxes | Respect displayed box capacity and avoid duplicate records |
| Items | Keep quantities valid and treat key items cautiously |
| Pokédex | Match Caught records with Seen records |
| Event flags | Change one related group, then test the result |
| Recovery | Restore the latest backup if the save fails to load |
Troubleshooting and FAQ
Most setup problems can be isolated by returning to a minimal configuration: clean supported ROM data, the current application release, no mods, default display settings, and a verified save backup. Record the operating system and Gen1 Recomp version when reporting a reproducible issue through GitHub Issues.
| Problem | First Check | Practical Fix |
|---|---|---|
| Application will not launch | Incomplete extraction or permissions | Extract the full package and launch from a writable folder |
| ROM is not accepted | Wrong version or modified data | Test a clean legally owned Red, Blue, or Yellow dump |
| Save is missing | Incorrect user-data location | Check the platform-specific LÖVE application-data directory |
| Mod causes a crash | Version or dependency conflict | Disable the newest mod and retest the base game |
| Link Play times out | Address, firewall, or UDP port | Test locally, then verify firewall and router settings |
| Voxel view stutters | Graphics load is too high | Reduce effects, render distance, or shadows |
Disable the newest mod first, restore default graphics settings, verify the ROM, then test the most recent save backup. This order limits unnecessary changes.
Q: What is gen1 recomp gameplay?
It is the native recreation of Pokémon Red, Blue, and Yellow gameplay through a handwritten Lua and LÖVE2D engine. It uses game data from a legally owned ROM and is not a traditional emulator.
Q: Which Pokémon versions can Gen1 Recomp use?
The documented base project supports Pokémon Red, Blue, and Yellow. Select the matching version during import and use clean data when troubleshooting compatibility.
Q: Can I install the DramaticShape Voxel Mod immediately?
Install and test the unmodded application first. Then back up saves and settings, import the separate voxel project through the Mod Manager, and verify compatibility with your Gen1 Recomp release.
Q: How do I protect saves during updates or Save Editor changes?
Close the game, copy the complete save and user-data folders, and keep the backup outside the installation directory. Test the edited or updated save before removing the backup.
Use the Gen1 Recomp GitHub repository, official Releases, project Wiki, and the Discord linked by the repository for current project information.