SQL Module Merging Guide

Query builder for merging SQLite databases. Replaces the Hogwarts Mod Merger, but is based on your version of the game and has the ability to edit merges. Simple manual version.

Hogwarts Legacy Guide for merging SQL mods

🎮 **The ultimate guide to fix the black screen issue after merging SQL mods! **

Are you experiencing black screen issues after incorporating the SQL mod? Don't worry, this can usually be solved by **manually merging the mod with your version of the game**!

✨ Script Introduction

This is a script for generating merge queries for a SQLite database. You can think of it as an alternative to **Hogwarts Mod Merger**, but it's based on **your version of the game** and allows you to **edit merged content**.

• **Project address**: GitHub - HL_sqlite_query_merge_gen
• **About**: This script helps modders or users of Hogwarts Legacy to generate the differences between your mod (containing SQLite database changes) and your game version's SQL database, and update it.
• **Requirements**: Python 3.7
• **Library**: os, sqlite3

---

🛠️ How to use

For mod users:

• **Extract your game database**

Use FModel to extract your version of the database from the game files.

• Select `pakchunkO-WindowsNoEditor.pak` -> `Phoenix/Content/SQLiteDB/PhoenixShipData.sqlite` - this is your database version.
• Move this file to the `Updated` folder in your home directory.

• **Extract database files in the module**

Use unrealpak to extract the db file from the HL module.

• Just drag your files onto `Unpack.bat`.
• Move this folder to the `main/Mods` directory. You can add the mods you need and the script will scan all folders.

• **Generate differential SQL file**

Run `main.py` which will generate an SQL file of differences between the module and your database.

• **You can modify it! ** For example, I added a script to remove all lines containing `tutorial` data because on my version of the game it would cause the game to crash when any mod was installed. You can find `substrings = ["Tutorial", "Game"]` in the code. If you are sure that some data will cause the game to crash when starting, you can modify it.

• **Update your database files**

Run `update.py` to update the database files in the `/Updated` folder. It executes all queries in the SQL query file.

• **Package changes into pak file**

Use unrealpak again.

• Create a folder tree `./z_MergedMods/Phoenix/Content/SQLiteDB` in the unrealpak root directory.
• Copy **PhoenixShipData.sqlite** from the `./Update` folder to `./z_MergedMods/Phoenix/Content/SQLiteDB`.
• Drag the `z_MergedMods` folder onto `UnrealPak-Without-Compression.bat`.

• **Done! **

Place the generated `z_MergedMods` folder into HL's `~mods` directory.

---

For modders:

You can generate a `differences_and_updates.sql` SQL file using your mod and the original HL database file.

This way you get **clean and correct changes** that work on all game versions!

For specific operations, please refer to this example: Example. This way, everyone can merge based on their own version of the game!

---

💡 **Tips**: Although manual merging is a little more steps, it can fundamentally solve the version conflict problem, allowing you to freely combine your favorite modules and enjoy a unique magical world!