Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Relic SGA Archive Tool

Disclaimer

Not affiliated with Sega, Relic Entertainment, or THQ.

Warning

This project runs executables (pre-packaged) to encode/decode audio files.

Description

A tool for parsing and extracting assets from Relic Entertainment games; primarily Dawn of War I, DoW II, and DoW III.

Installation (Pip)

pip install relic-game-tool

Installing from GitHub

For more information, see pip VCS support

pip install git+https://github.com/ModernMAK/Relic-Game-Tool

Usage

Via importing the python package, or running the relic from the command line.

As a Python Library

Details pending

As a Command Line Tool

After installing the package with pip, the tool can be run by entering relic into the command prompt. The tool will list arguments and sub commands available.

Quick Use

In general, it's best to unpack the SGA files to avoid unpacking the SGA for multiple extraction passes.

To unpack SGA files, we can use the following command:

relic sga unpack 'DoW directory' -o 'storage path' -r -b -e

First, the path to the DoW game is specified, we only use one path to avoid extracting other game assets to the same output directory.
In the case of DoW, the latest game contains almost all assets of the previous releases.
The flag-o specifies the output directory, this is optional, but makes it easier to perform the next step, extracting assets.
The -r flag will search all files and folders within the directory.
The -b flag will not extract archives which contain certain keywords marking them as lower quality assets, this will prevent lower quality assets from overwriting higher quality ones.
The -e flag will force the program to crash on an error; in most cases, the output is bad, and a bug report should be submitted.

After unpacking the SGA archives, we can extract assets from Relic Chunky files.

relic chunky extract {extractor} 'storage path' -o 'extract path' -r -e

Extractor expects the 'type' of chunky to extract, running relic chunky extract will list available extractors. First, the path to the unpacked archive, 'storage path' should be the same path used after the -o flag. The flags -o, -r, and -e function the same as above.

Format Specifications

I've compiled what I've learned on the Wiki. It may be lacking compared to the actual python code; for more information, you may wish to examine the relic\sga, relic\chunky, and relic\chunky_formats sub-packages instead.

Metadata

Release files for relic-game-tool 2022.0rc0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for relic-game-tool 2022.0rc0
File Size Uploaded Provenance
relic-game-tool-2022.0rc0.tar.gz 198.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for relic-game-tool 2022.0rc0
File Interpreter ABI Platform
relic_game_tool-2022.0rc0-py3-none-any.whl Python 3 none any Details

Total release size: 430.9 kB

Release files / relic-game-tool-2022.0rc0.tar.gz

Download URL relic-game-tool-2022.0rc0.tar.gz
Size 198.9 kB
Tags Source
SHA-256 checksum
How to use checksums
6c8c040aeb2fff20a8eb75a018191150d28f054e2ab935a9bfce293a5ee21445
BLAKE2b-256 checksum
How to use checksums
aede008db69ccb0eb6a37a5496e43ab67936cd80a4a73e145ed8dab20670f0a3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.13

Release files / relic_game_tool-2022.0rc0-py3-none-any.whl

Download URL relic_game_tool-2022.0rc0-py3-none-any.whl
Size 232.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0e3f88b5664bfa383416c8bf5a1268e522dbb63dc8e7901eae81757900bd36d0
BLAKE2b-256 checksum
How to use checksums
00a7624885548103c364478ad6a9c91060475614dd71c454b25b6cd0c70c29a4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.9.13

Security for relic-game-tool 2022.0rc0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page