How to Read Issue Reports
An open GitHub issue confirms that a report exists; it does not mean every user is affected or that the suggested cause is correct. Always compare the reported Gen1Recomp version, VoxelMod version, game, device and enabled mods with your own setup.
Gen1Recomp Issues
Gen1Recomp's active issue tracker covers gameplay events, saves, input, audio, rendering and platform packages. Because individual reports change state frequently, the official Gen1Recomp issue tracker (opens in a new tab) is more useful than a copied list that can quickly become stale.
The project also documents deliberate differences from original Game Boy behavior. A modern feature or ruleset change is not necessarily a bug.
VoxelMod Reports to Check
The VoxelMod tracker includes reports involving:
- widescreen battles (opens in a new tab);
- performance and draw distance (opens in a new tab);
- battle transitions (opens in a new tab);
- 3D battle presentation (opens in a new tab);
- Android performance (opens in a new tab);
- sprite artifacts (opens in a new tab).
Open each report to see its current state, affected versions and maintainer discussion.
Performance and Mod Conflicts
VoxelMod performance can change with CPU and GPU capability, graphics drivers, resolution, draw distance, effects, thermal limits and other mods. No universal minimum specification or guaranteed frame rate is documented.
VoxelMod 1.4.0 does not list an explicit mod conflict in its manifest. Other combinations can still cause problems, so enable and test one optional mod at a time.
Before Reporting a Problem
Record the game, exact base version, mod version, platform, device, graphics settings and other enabled mods. Search the relevant issue tracker before opening a duplicate report.
- Base-game logic, saves or input: Gen1Recomp issues (opens in a new tab)
- Voxel rendering or 3D presentation: VoxelMod issues (opens in a new tab)
- Setup problems: review the 3D setup guide first.