Three independently switchable conveniences for Final Fantasy X HD Remaster, loaded by Fahrenheit.
Work in progress / experimental preview. A successful build verifies compilation and packaging, not complete in-game compatibility. Final Fantasy X only; Final Fantasy X-2 is unsupported. Keep a backup of your saves and report the game build, scene and enabled settings when filing an issue.
- NoSplash: skips the startup splash sequence and boot videos.
- NoLauncher: prevents the launcher from reopening when the game closes.
- FocusInput: neutralizes controller input while the game window is unfocused.
Settings and diagnostic pad logging are available in Fahrenheit's settings panel. English and German labels are included.
- Windows and a legitimate installation of Final Fantasy X HD Remaster.
- Fahrenheit, compatible with the revision pinned in
fahrenheit.release.ref. - The mod is a Windows x86 managed plugin, not a standalone executable. Fahrenheit provides its runtime and loader dependencies.
Every release carries two archives. fahrenheit-full-<version>.zip is the ready-to-play package: the Fahrenheit host built from the pinned revision, the mod, a loadorder naming it, and the launcher scripts. fhqol-mod-<version>.zip is the mod alone, for an existing Fahrenheit installation.
Full package:
- Download the ZIP and its SHA-256 checksum from Releases.
- Extract it into the game directory, next to
FFX.exe. The resulting paths must befahrenheit/bin/fhstage0.exeandfahrenheit/mods/fhqol/fhqol.dll. - Start the game through
start-ffx-with-mods.cmd, which checks for the Microsoft .NET Runtime 10 (x86) and offers to install it. The bundledREADME.txthas the details.
Mod only:
- Install Fahrenheit following its upstream instructions.
- Extract the mod ZIP into the game's
fahrenheit/directory. The resulting path must befahrenheit/mods/fhqol/fhqol.dll. - Add
fhqolon its own line tofahrenheit/mods/loadorder. - Launch the game and adjust the mod's settings in Fahrenheit.
To uninstall, close the game, remove that loadorder entry and remove fahrenheit/mods/fhqol/, or remove the whole fahrenheit/ directory for the full package. Do not overwrite the game's executable or data archives.
Verify the ZIP with Get-FileHash <downloaded.zip> -Algorithm SHA256 and compare the value with the .sha256 file.
Requires Git, PowerShell 7 and the .NET 10 SDK selected by global.json.
git clone https://github.com/Exoridus/ffx-qol-mod.git
cd ffx-qol-mod
pwsh tools/bootstrap.ps1
pwsh build.ps1 -Configuration Release -OutDir .release/stageBootstrap checks out the pinned public Fahrenheit source. No game installation or private sibling repository is required to compile. -Deploy is an optional local convenience with a machine-specific destination in build.ps1; use staged output for other installations.
The full package additionally needs the Fahrenheit host, whose native loaders require Visual Studio (or Build Tools) with the C++ workload and an integrated vcpkg:
pwsh tools/build-fahrenheit.ps1 -Configuration Release
pwsh .github/scripts/New-ReleasePackage.ps1 -Tag v<VERSION> -StageDir .release/stage -OutDir .release -FahrenheitDeployDir .workspace/fahrenheit/artifacts/deploy/relCI builds on Windows, builds the Fahrenheit host from the pinned revision, and exercises the same package and release-note scripts used by releases. The mod ZIP contains only mods/fhqol/: the mod DLL, manifest, dependency metadata and localization files. The full ZIP adds Fahrenheit's bin/ as built from fahrenheit.release.ref, a loadorder, and the launcher scripts from packaging/. Game assets are never bundled.
Maintainers set the manifest version, merge to main, then dispatch:
gh workflow run release.yml -R Exoridus/ffx-qol-mod -f version=v<VERSION> -f dry_run=trueOmit dry_run to publish an experimental prerelease with a ZIP and SHA-256 file. The version must match the manifest; the workflow creates its tag only after building and packaging succeed.