Hogwarts Legacy Saved Game Editor

Game Savings Editor with graphical interface.

The first version of the basic GUI to modify the Hogwarts Legacy saves. It also includes a tool for extracting SQLite databases so that they can be modified externally and repackaged into a new saved game.

This is an alpha version and may contain bugs.

Features.

- Resource changes (there must be at least one).

- Change of combat resources (there should be at least one).

- Change the points of talent.

- Remove talents.

- Change the number of mission items.

- Change player name.

- Change the player's house.

- Change the size of the basic inventory

- Change the level of experience

- Detailed lock status monitoring

- Unlock all quick move points

- Unlock all transformation recipes

- Unlock all spells Unlock all spells

- Unlock all gear Unlock all gear

- Unlock all equipment properties Unlock all equipment properties.

- Change attack parameters and equipment protection in inventory.

- Extract SQLite database from file.

- Create a save file from a SQLite file.

Montage.

A web application that runs in a browser. Extract the file and open hlse.html in a browser.

Use.

- Open the hlse.html file in a browser (usually a double click).

- Select the "Saved File" input field on the left side of the screen and select the saved file you want to edit.

- If this is a valid saved file, the screen on the left will change.

- Use the tabs on the left to make changes to player data, resources, etc. and save the game.

- After making your changes, click the Save File tab on the left side of the screen.

- Click the "Download" button on the first tab. This will create a modified save of the game and replace the original one.

Important: "Database" and "Upload User Database" are options for advanced editing of the saved game; simply click the first "Upload" button on the "Save Files" tab and you will get a saved game file containing changes you made to other parts of the GUI.

Note for advanced users In previous versions, there was an error when save files were not created correctly in the new SQLite database if you added many new entries to one of the tables. It looked as if the save was refusing to load. In any case, this bug has been fixed, so feel free to experiment with more complex changes to the database.