Reporting bugs
Every report helps, and a good report gets fixed first. Reports go to the issue tracker, which asks for everything we need step by step. If you found the pack on a mod site, its Bugs tab works too: we copy those reports into the tracker.
Pick the right form
- Crash or freeze: the game closed by itself, froze, or didn't start.
- Bug report: something works differently from the docs.
- Idea or request: something new.
What to attach
All of these are plain text files you can drag into the form.
| File | Where | What it tells us |
|---|---|---|
LibertyCityCore.log, CompactHUD.log, LBInteractionCompat.log, PedSpawnGuard.log | plugins\ in your GTA IV folder | Which parts of the pack started, which ones switched themselves off and why |
LibertyCityCrash.log | plugins\ | What the pack saw just before a crash |
ScriptHook.log | your GTA IV folder | Whether ScriptHook and the scripts loaded |
| The car's log, if you use one of our cars | plugins\RoadsterX.log or plugins\TandemT6.log | The car plugin's start-up and settings |
Copy the logs right after the problem, before you start the game again: a new start overwrites them.
The crash location
When GTA IV crashes, Windows records where:
- Press Win, type Event Viewer and open it.
- Go to Windows Logs > Application.
- Find the newest Application Error whose program is GTAIV.exe.
- Copy the lines Faulting module name and Fault offset into the crash form.
That pair (for example GTAIV.exe and 0x008f2c32) is often enough to find the exact cause.
Your setup in one line
The forms ask for these. Having them ready saves time:
- the pack version (from the zip name, for example
0.1.0-beta.1) - Steam or Rockstar Games Launcher, and the game version (how to check)
- Windows 10 or 11
- your other mods: a list of the files in
plugins\is perfect - keyboard and mouse, or which controller