CRASH LOG AUTO SCANNER &
SETUP INTEGRITY CHECKER (CLASSIC)

INTRODUCTION

CLASSIC is a tool used for scanning crash logs generated by Buffout 4 (Fallout 4) and Crash Logger (Skyrim), as well as scanning game/mod files for the same games. Starfield support is also on its way.

CLASSIC will provide detailed information on detected settings, errors, and mods that might be causing the crash, along with various suggestions and steps to take depending on what it finds. There are currently around ~250 different checks implemented into the code. CLASSIC also allows you to easily backup, restore and remove certain mod files, check for Script Extender updates, monitor Papyrus logs, scan many other logs for errors and extensively scan game and mod files for any potential problems.

For more info and setup instructions, see the PDF. CLASSIC is also on Nexus Mods: https://www.nexusmods.com/fallout4/mods/56255

REQUIREMENTS

FALLOUT 4

You can find detailed Buffout 4 installation instructions here.

• Fallout 4 Script Extender
• Address Library for F4SE Plugins
• Buffout 4 NG (OG/NG/VR) or Buffout 4 (OG)
• BSArch (for scanning mod files)

SKYRIM (Work in Progress)

• Skyrim Script Extender
• Address Library for SKSE Plugins
• Crash Logger AE for VR
• BSArch (for scanning mod files)

Note that for both Fallout 4 and Skyrim, you should also install the Microsoft Visual C++ Redistributable All-In-One package and the DirectX Redist (June 2010) package. These packages contain important files and components required for many games / certain mods and can also prevent some forms of crashes.

INSTALLATION

Option 1: Download Pre-built Release (Easiest - Recommended)

The simplest way to use CLASSIC is to download the pre-built release from the Releases page:

1. Go to the Latest Release
2. Download the .7z archive from the Assets section (e.g., CLASSIC-v8.0.0.7z)
3. Extract the archive to your desired location using 7-Zip or similar
4. Run CLASSIC.exe from the extracted folder

What's included:

• CLASSIC.exe - Main executable
• CLASSIC Data/ - Configuration files and databases
• All required dependencies bundled
• No Python installation needed

Option 2: Run with uvx (Alternative Method)

If you prefer to run the latest development version or have trouble with the release archive, you can use uvx to run CLASSIC directly from GitHub. This requires Python 3.12 or newer.

Install uv (One-time Setup)

First, install the uv tool if you haven't already:

Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

macOS/Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

Running CLASSIC

Once uv is installed, you can run CLASSIC directly from GitHub:

GUI Mode (Default - Recommended)

# Run the GUI interface (full featured)
uvx --from github:evildarkarchon/CLASSIC-Fallout4 classic

# Or explicitly specify GUI
uvx --from github:evildarkarchon/CLASSIC-Fallout4 classic-gui

Command-Line Mode (Crash Log Scanner)

# Run CLI crash log scanner (scans all logs in default locations)
uvx --from github:evildarkarchon/CLASSIC-Fallout4 classic-cli

Game Integrity Scanner

# Run game file integrity checker (optional feature)
uvx --from github:evildarkarchon/CLASSIC-Fallout4 classic-scan

Running Specific Versions

# Run a specific release version
uvx --from github:evildarkarchon/CLASSIC-Fallout4@v7.35.0 classic

# Run from a specific branch
uvx --from github:evildarkarchon/CLASSIC-Fallout4@got-caps classic

# Run from a development branch
uvx --from github:evildarkarchon/CLASSIC-Fallout4@uv-rays classic

Advanced Options

# Specify Python version
uvx --python 3.12 --from github:evildarkarchon/CLASSIC-Fallout4 classic

# Run with verbose output for debugging
uvx --verbose --from github:evildarkarchon/CLASSIC-Fallout4 classic

Persistent Installation

If you use CLASSIC frequently, you can install it persistently:

# Install CLASSIC commands system-wide
uvx install --from github:evildarkarchon/CLASSIC-Fallout4 classic-fallout4

# Now you can run directly:
classic       # GUI (full featured)
classic-cli   # CLI crash log scanner
classic-scan  # Game integrity checker

uvx Notes

• First Run: The first time you run CLASSIC with uvx, it will download dependencies (including PySide6 for the GUI). This may take a minute or two.
• Cached Environment: Subsequent runs will be much faster as uvx caches the environment.
• GUI Requirements: The GUI mode requires a display. Use CLI mode for headless/server environments.
• Windows Users: If you encounter permission issues, run PowerShell as Administrator.
• Updates: uvx always runs the latest version from GitHub unless you specify a version tag.
• Data Files: uvx automatically handles the CLASSIC Data folder and configuration files.

Contributing

Dev Environment Setup

The project uses Python 3.12+ and dependencies are managed with uv, a fast Rust-based Python package manager that's 10-100x faster than traditional tools.

Our primary IDE is Visual Studio Code. .vscode/ contains config files to aid in working on the project, including extension recommendations. In the Extensions sidebar (Ctrl+Shift+X), search for @recommended and you'll see a star on them.

You can run CLASSIC or build the exe from the VS Code GUI in the Run and Debug sidebar (Ctrl+Shift+D).

Installing uv

Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

macOS/Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

Setting Up the Development Environment

Clone the repository and install dependencies:

# Clone the repository
git clone https://github.com/evildarkarchon/CLASSIC-Fallout4.git
cd CLASSIC-Fallout4

# Install all dependencies (creates .venv automatically)
uv sync --all-extras

# Or install specific extras as needed:
# uv sync --extra cli      # For CLI progress features
# uv sync --extra windows  # For Windows-specific features

Note: For development, it's recommended to use uv sync --all-extras to ensure you have all optional dependencies (tqdm for CLI progress bars, pywin32 for Windows features) available for testing all interfaces.

To verify VS Code is using this venv: press F1 and search >python.setInterpreter, then select .venv/Scripts/python.exe (Windows) or .venv/bin/python (Unix).

Running the Application

# Run GUI mode
uv run python CLASSIC_Interface.py

# Run CLI mode
uv run python CLASSIC_ScanLogs.py

# Run tests
uv run pytest -n auto

Managing Dependencies

# Add a new dependency
uv add requests

# Add a development dependency
uv add --dev pytest

# Update all dependencies to latest versions
uv lock --upgrade

# Update specific package
uv lock --upgrade-package pyside6

Migration from Poetry

If you have an existing Poetry environment, you can migrate using the provided script:

python migrate_to_uv.py

This will backup your Poetry environment and set up uv automatically.

Building Executables

CLASSIC's exe is built using PyInstaller. You can do so with VS Code (Ctrl+Shift+D) or via command. To enable compression of the exe, download UPX. Add the folder it's extracted in to your PATH or specify the location in the command or .vscode/launch.json

# Build the executable
uv run pyinstaller --clean .\CLASSIC.spec

# With UPX compression (smaller file size)
uv run pyinstaller --clean --upx-dir 'C:\\Path\\to\\UPX' .\CLASSIC.spec