- Gen1 Recomp stadium battles use a separate voxel mod, not a built-in Pokémon Stadium game mode.
- Base setup first: Confirm Red, Blue, or Yellow launches correctly before adding visual modifications.
- Battle view: Enable 3D battle presentation, then test wild and trainer encounters separately.
- Optional models: Stadium-style Pokémon models require compatible assets and separate configuration.
- Safe testing: Back up saves, use matching mod versions, and return to the standard view when troubleshooting.
gen1 recomp stadium battles: What They Are
Gen1 Recomp is a native Lua and LÖVE2D recreation of Pokémon Red, Blue, and Yellow that uses data from a legally owned ROM. Its standard presentation is distinct from the optional 3D experience. Stadium-style battles refer to the visual battle presentation provided by the separate DramaticShape Voxel Mod and its optional model features.
This distinction matters. The project does not become the original Pokémon Stadium software, and the base project should not be described as containing a separate Stadium campaign. Instead, the voxel mod can reinterpret Kanto maps and battles with 3D geometry, configurable cameras, and optional Pokémon model support.
Base Gen1 Recomp
- Native Lua/LÖVE2D engine
- Supports Red, Blue, and Yellow
- Test this version before modding
Voxel Presentation
- Community-made visual mod
- 3D overworld and battle scenes
- Requires version compatibility
Stadium-Style Models
- Optional model-based feature
- Needs prepared compatible assets
- Keep separate from core files
Do not treat the DramaticShape Voxel Mod as an official Pokémon Stadium port. It is a separate community project that changes how Gen1 Recomp renders the game.
| Feature | Base Project | Voxel Mod |
|---|---|---|
| Core engine | Native Lua/LÖVE2D recreation | Runs on Gen1 Recomp |
| Overworld | Original-style presentation | Voxelized 3D interpretation |
| Battles | Standard Gen I presentation | Optional 3D battle presentation |
| Stadium-style models | Not assumed built in | Optional supported feature |
| ROM requirement | Legally owned Red, Blue, or Yellow data | Same supported game data |
Install the Voxel Battle Setup
Install and verify the base application before changing its visual profile. This approach makes it easier to identify whether a problem comes from Gen1 Recomp, the voxel package, an optional model set, or a graphics setting.
Verify the Base Release
Download Gen1 Recomp from the official GitHub repository or Releases page. Choose the package for your operating system, extract the complete archive, and launch the unmodded application.
Import Supported Game Data
Use a clean dump from your legally owned Pokémon Red, Blue, or Yellow cartridge. Confirm that the title screen, movement, menus, audio, and a normal save work before continuing.
Back Up User Data
Close the application and copy the save, configuration, and mod folders to a separate backup location. Keep an unmodded recovery point available.
Import DramaticShape
Download the prepared DramaticShape Voxel Mod package from its project repository. Use the built-in Mod Manager when supported, preserve the archive structure, and check its required Gen1 Recomp version.
Enable and Test
Enable required dependencies before the main voxel package. Restart Gen1 Recomp, load a test save, and confirm the voxel overworld works before enabling optional battle models.
| Setup Stage | What to Confirm | If It Fails |
|---|---|---|
| Base launch | Title screen and menus load | Reinstall the complete release folder |
| ROM import | Correct Red, Blue, or Yellow version appears | Test a clean supported dump |
| Save test | Game can create and reload a save | Restore the base configuration |
| Mod import | Voxel package appears in Mod Manager | Check ZIP structure and compatibility |
| First 3D test | Map, collision, and transitions work | Disable optional visual packages |
Add one major change at a time. A base-game test followed by a voxel test gives you a reliable comparison point for later battle troubleshooting.
Configure Cameras and 3D Battles
Once the voxel overworld is stable, configure the camera and battle presentation. The most reliable starting point is the mod's recommended preset rather than an experimental first-person or close-camera mode.
Use the standard camera to check map navigation, doors, stairs, collision, and transitions. Then enter a wild battle and a trainer battle separately. Different encounters may expose different camera positions, model behavior, or performance limits.
| Setting | Recommended First Test | Adjustment Goal |
|---|---|---|
| Camera preset | Standard recommended view | Preserve readable navigation |
| Rotation | Small changes only | Keep movement orientation clear |
| Zoom | Moderate distance | Show the arena without clipping |
| Battle presentation | Enable after overworld test | Separate renderer issues from map issues |
| Effects | Default or reduced | Improve frame pacing on weaker systems |
| First-person view | Experimental only | Use after normal 3D mode is stable |
Wild Battles
Test transitions, opponent placement, menu readability, and return-to-map behavior.
Trainer Battles
Check whether larger scenes, trainer animations, or camera framing behave correctly.
Close Camera
Use only after standard 3D battles work. Restore the default view if navigation becomes difficult.
Use this order: base game, voxel overworld, wild battle, trainer battle, optional models, then experimental camera features.
Controls, Models, and Performance
Stadium-style presentation is most useful when the battle interface remains readable and the controls stay predictable. Keep camera actions separate from movement, confirm, cancel, Start, and Select. Controller layouts can vary between desktop computers, Android devices, and handheld systems, so test every required input after changing the profile.
Optional Pokémon models should be treated as an additional layer. Follow the model package instructions, avoid mixing unsupported versions, and keep model files independent so they can be disabled without removing the main voxel mod.
Battle Readiness Checklist:
- Confirm the unmodded Red, Blue, or Yellow game loads
- Back up saves and user-data folders
- Match the voxel mod to the installed Gen1 Recomp version
- Test wild and trainer battles separately
- Verify battle menus and camera controls
- Disable optional models first when visual errors appear
| Symptom | Likely Cause | Recommended Fix |
|---|---|---|
| Game will not launch | Broken package or incompatible mod | Disable the newest mod and test the base game |
| Black or missing models | Incorrect assets or version mismatch | Review model requirements and package structure |
| Battle stutters | High voxel effects or resolution | Lower effects, shadows, render distance, or resolution |
| Camera clips terrain | Experimental angle or zoom | Restore the standard camera preset |
| Menus are hard to read | Excessive zoom or camera angle | Increase distance and return to the recommended view |
| Controller feels incorrect | Platform-specific mapping | Remap movement, confirm, cancel, Start, and Select |
Visual mods usually affect presentation, but gameplay or data mods can change persistent save information. Keep separate backups for unmodded and modded playthroughs.
Official project links: Gen1 Recomp GitHub repository, Gen1 Recomp Releases, and the DramaticShape Voxel Mod repository.
Troubleshooting and FAQ
When a Stadium-style battle setup breaks, reduce the configuration to its smallest working profile. Disable optional models and experimental camera features first, then test the voxel package, and finally test the base application without mods. Compare the installed Gen1 Recomp release, game version, mod version, and load order before reinstalling anything.
| Recovery Step | Action | Success Check |
|---|---|---|
| 1 | Disable optional models | Base voxel scenes render |
| 2 | Restore the standard camera | Maps and battles remain navigable |
| 3 | Disable other visual mods | Battle presentation becomes stable |
| 4 | Test without voxel features | Base Gen1 Recomp launches |
| 5 | Re-enable packages individually | The conflicting component is identified |
Q: Does Gen1 Recomp include an official Pokémon Stadium battle mode?
No. The Stadium-style experience comes from the separate DramaticShape Voxel Mod and optional model features, while the base project recreates Red, Blue, and Yellow.
Q: Can I use Stadium-style battles without the voxel mod?
The supplied setup information places 3D battles and optional Stadium model support within the separate voxel project. Test the base application first, then install that mod if you want the 3D presentation.
Q: Why do my battles crash after adding models?
Common causes include an unsupported model package, mismatched Gen1 Recomp and voxel versions, incorrect archive structure, or excessive graphics settings. Disable models and restore the last working profile.
Q: Do both players need the same setup for Link Play?
For direct battles or trades, both players should match the Gen1 Recomp release, game version, gameplay-changing mods, and relevant load order. Test an unmodded session when synchronization fails.
Treat the voxel battle setup as a layered configuration. Keep the base game, voxel renderer, optional models, and experimental camera features easy to disable independently.