- Gen1 Recomp install mods: Use the built-in Mod Manager instead of copying random files manually.
- Compatibility check: Confirm the mod supports your Gen1 Recomp release and Red, Blue, or Yellow version.
- Safe testing: Back up saves and test the unmodded game before enabling new packages.
- Conflict recovery: Disable recent mods first, then re-enable packages individually to identify problems.
Gen1 Recomp Install Mods: What to Prepare
Gen1 Recomp is a native Lua and LÖVE2D recreation that uses game data from a legally owned Pokémon Red, Blue, or Yellow ROM. It is not a traditional emulator and does not include copyrighted ROM files. Before you install mods, make sure the base application launches correctly and reaches the title screen.
The safest workflow is simple: install the official release, import your supported game data, create a working save, and only then add compatible modifications. This gives you a clean recovery point if a visual, gameplay, script, or interface package causes an error.
Base Application
- Download Gen1 Recomp from the official GitHub repository.
- Use the release package for your operating system.
- Extract the complete archive before launching.
Supported Game Data
- Use a clean dump from a legally owned Pokémon Red, Blue, or Yellow cartridge.
- Keep an untouched backup outside the installation folder.
- Avoid testing with an unverified ROM hack.
Mod Package
- Choose a package designed specifically for Gen1 Recomp.
- Read its version, dependencies, and supported game notes.
- Keep the original ZIP intact until import.
| Preparation | Recommended action | Why it matters |
|---|---|---|
| Official build | Use the GitHub Releases page | Avoid modified or unofficial downloads |
| First launch | Confirm the base game reaches the title screen | Separates application problems from mod conflicts |
| Save backup | Copy the active save and user-data folders | Protects progress before major changes |
| Mod source | Follow the author’s official project page | Provides compatibility and migration notes |
Never download or distribute ROM files through a mod guide. Gen1 Recomp supplies the engine, while users must provide game data from their own legally owned copy.
How to Install Mods with the Mod Manager
The built-in Mod Manager is the preferred method for gen1 recomp install mods. It helps organize packages, show installed content, toggle modifications, and reduce the risk of damaging the base application. Install one mod at a time so every change can be tested before the next package is added.
Verify the Mod Release
Check the mod’s official project page and confirm that it targets Gen1 Recomp rather than a conventional emulator, ROM hack, or different recompilation project. Note the required Gen1 Recomp version, supported game version, dependencies, and installation format.
Preserve the Original ZIP
Download the player-ready release package when one is available. Do not place a ZIP inside another ZIP, rename internal metadata files, or add an unnecessary top-level folder. Incorrect archive structure can prevent the manager from detecting the package.
Open the Mod Manager
Launch Gen1 Recomp after confirming that the unmodded game works. Open the built-in Mod Manager and select its import or add-mod option. Choose the downloaded package and wait for the manager to identify the mod.
Review and Enable
Read the detected name, version, dependencies, and compatibility information. Enable the package only after reviewing those details. Restart Gen1 Recomp if the manager requests it, then confirm that the mod appears in the installed list.
Test Before Adding More
Load a test save and check the feature affected by the mod. For example, inspect a changed interface, enter a map affected by a visual package, or test a gameplay rule in a controlled situation. Keep the new package disabled if the base game no longer starts correctly.
| Installation stage | What to check | Stop if |
|---|---|---|
| Compatibility | Target project, release version, game version | The package is made for another engine |
| Archive | Original ZIP structure and metadata | Files are nested or missing |
| Import | Mod name and version appear in the manager | The package is not detected |
| Activation | Game launches with one mod enabled | The title screen crashes |
| Testing | Affected feature works in a test save | Progress or loading behaves abnormally |
Import and test a single package at a time. A small, documented mod profile is easier to maintain than a large collection enabled without a known load order.
Manage Compatibility, Load Order, and Updates
Most mod problems come from overlapping files, outdated dependencies, or packages that change the same scripts and assets. The later-loaded mod may override an earlier change, so follow the order recommended by each author whenever a package includes dependency instructions.
Separate ordinary community mods from the DramaticShape Voxel Mod. The voxel project is a distinct community modification with its own compatibility requirements, camera settings, 3D battles, and performance considerations. Do not assume that a feature shown in a voxel package belongs to the base Gen1 Recomp application.
| Mod category | Typical changes | Compatibility priority |
|---|---|---|
| Interface mod | Menus, text presentation, input displays | Usually lower risk, but version checks still matter |
| Visual mod | Sprites, effects, scaling, presentation | Test alongside other visual packages |
| Gameplay mod | Pokémon, moves, items, rules, encounters | High priority; may affect saves or link play |
| Script or map mod | Events, maps, NPCs, progression | High priority; conflicts can block progress |
| Voxel mod | 3D rendering, cameras, battles, models | Treat as a separate project with specific requirements |
Stable Profile
Keep a tested Gen1 Recomp version, a known-good save, and a short list of compatible mods. Record the enabled order after every successful test.
Update Profile
Install a new base release separately, launch it without mods, verify the ROM and save, then restore compatible packages one at a time.
Recovery Profile
Maintain an unmodded backup and a separate modded save. This allows you to compare behavior without overwriting the clean setup.
When updating an installed mod, disable the older version before importing its replacement. Remove duplicate copies so the manager cannot load two versions simultaneously. Preserve configuration files only when the new release explicitly supports them.
For major Gen1 Recomp updates, use this order:
- Back up saves, settings, and the mods folder.
- Test the new base application with no mods.
- Confirm that your legally owned ROM loads normally.
- Update required framework or dependency packages.
- Import dependent mods individually.
- Test the game after each activation.
A base application update can change internal systems used by mods. Temporarily disable outdated packages until their authors confirm support for the installed release.
Troubleshoot Broken Mod Installations
If Gen1 Recomp stops launching after a mod change, return to the smallest working configuration. Close the game, open the Mod Manager, and disable the most recently installed or updated package. If the application launches again, test that package separately before restoring the rest of the profile.
| Symptom | Likely cause | First recovery action |
|---|---|---|
| Mod is not listed | Incorrect archive structure or unsupported package | Recheck the original ZIP and project requirements |
| Title screen crashes | Incompatible or damaged package | Disable the newest mod |
| Visual errors | Conflicting renderer or outdated visual files | Return to default graphics settings |
| Save fails to load | Invalid edit or persistent gameplay change | Restore the latest save backup |
| Link Play fails | Version, mod, firewall, or UDP mismatch | Test both systems without gameplay mods |
| Android data disappears | App replacement or uninstall removed local storage | Restore the exported save backup |
Use a controlled elimination process:
- Disable every mod and verify that the base game starts.
- Re-enable packages individually.
- Test the affected map, menu, battle, or save after each activation.
- Check dependencies before removing a framework package.
- Record the package that reproduces the error.
- Review the mod author’s official issue tracker or instructions.
For save-related failures, do not immediately overwrite the failed file. Preserve it for comparison, then restore the last known-good backup. The built-in Save Editor can change party Pokémon, PC boxes, items, Pokédex data, and event flags, but large edits should be made carefully and tested in small groups.
Before You Keep a Mod Enabled:
- The base Gen1 Recomp installation launches without mods
- The mod targets Gen1 Recomp and supports the installed release
- The original ZIP structure and required dependencies are intact
- A clean save and a modded-save backup exist separately
- The affected feature works after a restart
If the unmodded game launches and your backup loads, the installation is recoverable. Rebuild the profile gradually instead of reinstalling everything at once.
Modding Checklist and Practical Recommendations
A reliable mod setup depends more on organization than on the number of packages installed. Keep the base application, save backups, mod archives, and active profile easy to identify. This is especially useful when moving between Windows, macOS, Linux, Android, or handheld environments.
| Task | When to do it | Recommended result |
|---|---|---|
| Back up saves | Before installing or updating mods | A dated copy outside the game folder |
| Test the base game | Before the first mod import | Title screen, movement, menu, and save all work |
| Record versions | After every stable setup | Base release, mod versions, and load order documented |
| Test link play | Before online trades or battles | Matching versions and compatible mod sets |
| Review updates | Before replacing an installation | Release notes and known issues checked |
Keep gameplay-changing mods separate from cosmetic packages when troubleshooting. If both players use Link Play, match the application version, game version, active mod list, and load order. Visual or interface changes may be less likely to affect synchronization, but testing without gameplay modifications remains the safest diagnostic step.
The Gen1 Recomp Wiki is the best place to review project-specific workflows, while the official repository and releases provide the recognized project entry points. For the separate voxel experience, consult the DramaticShape Voxel Mod repository.
Treat every working mod profile as a restore point. Record its versions and load order before experimenting with a new package or visual configuration.
Q: Where should I download Gen1 Recomp mods?
Use the mod author’s official project page or repository whenever possible. Verify that the package targets Gen1 Recomp, then review its supported release, game version, dependencies, and installation notes.
Q: Can I install emulator mods in Gen1 Recomp?
Not automatically. Mods designed for an emulator, conventional ROM hack, or another recompilation project may use incompatible files and systems. Only install packages explicitly made for Gen1 Recomp.
Q: What should I do if a mod breaks the game?
Disable the newest package first and confirm that the base game launches. If necessary, disable all mods, restore a clean save backup, and re-enable packages individually until the conflicting mod is identified.
Q: Is the DramaticShape Voxel Mod built into Gen1 Recomp?
No. It is a separate community mod that adds voxelized 3D presentation, configurable cameras, 3D battles, and experimental viewing features. Install it only after testing the base application.