Logfiles and Troubleshooting

There is no such thing as “bug free” software, the ModPack is highly configurable, and I am a one man team. This means that you’re likely to run into things that don’t work as expected when combined with other mods, or that cause errors. 99% of the time these are harmless but inconvenient errors that may do things like softlock the game during matches or produce infinite loading screens. The days of the ModPack being able to irreparably corrupt your save file are long gone, and you shouldn’t worry about things like that at this point, there’s almost always a solution to whatever problem you are facing, and the community is generally happy to help, and if they can’t get you up and running again, I’m pretty readily available to help as well. However, I’m going to need a logfile before I can do much for you. Otherwise, it’s like finding a needle in a haystack to figure out what went wrong. The ModPack has hundreds of thousands of lines of code, and trying to find the line that caused your error just isn’t going to happen without some direction. If you experience a bug or error, the official Discord is the place you want to go. There’s a channel there called mod-bug-reports that you will want to post a description of your problem and your logfile to.

A logfile can be produced two ways. The first, produces an actual file, PWGRLog.txt, in your root Fire Pro directory, the second produces a window which displays log messages. The first is definitely more helpful, but must be enabled BEFORE starting the game to catch the problem, while the other is faster and doesn’t require anything at startup, it won’t produce a file and will still only catch errors if the window is open.

To create a logfile in the root directory you need to start the game with the –logfile startup command. To do this open the StartupCommands.txt file found in your root Fire Pro directory and add the line "-logfile" with no quotation marks to a new line in the file. Please make sure it's the only text on the line.

To open the Log window simply go to your PWGR window while the game is running and hit the Log option on the menu bar. This will open a window that will catch errors. You can then provide a screenshot of this window in the same way that you can provide a logfile. If you missed the error (and it’s not a repeating error) there’s a very good chance that you can use the “Main Menu” button on the ModPack Menu to return to the main menu and restart the match to see if you can get it to error again with the log window open.

Once you have a logfile of your error/bug, head to the mod-bug-reports channel and leave a message in there. The community will try to assist you, and if they can’t I should be able to help you out. Please remember that I while I do spend a lot of time working on my computer, that I do this as a hobby mostly, and that I can’t always immediately jump at your post to help you.

If you use the –logfile command, please note that it SHOULD NOT be left enabled when not trying to reproduce bugs for an error report. Logging can take a lot of processing (depending how often the game is producing something that needs to be logged) and will slow the game down considerably in some circumstances.