Gamesutil
[!NOTE] Installation is supported only for the following:
- Windows
- Linux
[!NOTE] Development requires a fully configured Dotfiles dev environment
Table of Contents
Installation
Pip
python3 -m pip install gamesutil
Manifest
Create the Save-Manifest.json
[!NOTE] Any instances of {STEAM_ID} are automatically replaced by the program with your Steam ID
If multiple Steam Ids are present in the Steam installation, the program will prompt the user for clarification
The Manifest should contain:
- coldLocation: The folder where the cold saves are stored
- saves:
- save:
- coldName: The folder name that will be stored in the cold save location
- hotLocation: The location of the hot save
- save:
{
"coldLocation":"F:\\misc\\src\\gamesutil\\saves",
"saves": [
{
"coldName":"My Game Save",
"hotLocation": "%USERPROFILE%\\AppData\\Local\\Game Company\\The Game"
},
{
"coldName":"My Other Game Save",
"hotLocation": "C:\\Program Files (x86)\\Steam\\userdata\\{STEAM_ID}\\976730"
}
]
}
In the above sample:
-
cold location: F:\misc\src\gamesutil\saves\My Game Save
-
hot location: "%USERPROFILE%\AppData\Local\Game Company\The Game"
-
hot location: "C:\Program Files (x86)\Steam\userdata\{STEAM_ID}\976730"
[!NOTE] Hot location: should point to the directory where the game saves
Cold location: your backup {STEAM_ID} is replaced by the program with the actual Steam Id, if multiple exist in your system it will prompt the user for clarification
Usage
Collect
-sm The location of the Save Manifest
gamesutil collect -sm C:\PATH\TO\SAVE-MANIFEST.JSON
This will copy all hot saves listed in the manifest into the cold save location
Inject
-sm The location of the Save Manifest
gamesutil inject -sm C:\PATH\TO\SAVE-MANIFEST.JSON
This will copy all the cold saves listed in the manifest into the hot save location
Old
An "old" folder will be created inside the cold location, this folder maintains
a copy from the previous collection and its useful in the event the most recent game save is corrupted
Development
[!NOTE] Development requires a fully configured Dotfiles dev environment
source init.sh
Metadata
Release files for gamesutil 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gamesutil-2.1.0.tar.gz | 16.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gamesutil-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.8 kB
Release files / gamesutil-2.1.0.tar.gz
| Download URL | gamesutil-2.1.0.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc952b9d133cebb55ba3ca53040cba7ecdaf6002e9b88190f8159dbcaef18668
|
|
BLAKE2b-256 checksum How to use checksums |
067403259f8afaafefd7f5bca27839bffc9aea16287d1a226350e2b005ff1b6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Release files / gamesutil-2.1.0-py3-none-any.whl
| Download URL | gamesutil-2.1.0-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc6d7f15b2f91cf80b9f0ffde0dfab232e658f6c81dfa4e26108f1e60fc2682b
|
|
BLAKE2b-256 checksum How to use checksums |
9bd702263890c45fab0443e27fc949f25951d8076d76025bc285f4cf2ffb8536
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|