mio-decomp-cli
A CLI for decompiling the .gin files from MIO: Memories in Orbit.
Huge thanks to @mistwreathed for creating the original version of this tool.
Installation
python -m pip install mio_decomp
mio-decomp version # Verify it installed successfully
Setup
mio-decomp config set game_dir "<Path to your MIO install>" # Defaults to "C:\Program Files (x86)\Steam\steamapps\common\MIO". If your install is there, you can skip this command.
Use
mio-decomp decompile gin1.gin ./path/to/another/gin.gin -o output # Decompile .gins
mio-decomp parse ./path/to/save.save -o save.json # Convert save file to JSON
1 maintainer
Metadata
1 maintainer
Release files for mio-decomp 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mio_decomp-0.3.2.tar.gz | 39.7 kB | With provenance | Details for mio_decomp-0.3.2.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mio_decomp-0.3.2-cp313-abi3-win_amd64.whl | CPython 3.13 | abi3 | Windows x86-64 | Details for mio_decomp-0.3.2-cp313-abi3-win_amd64.whl |
| mio_decomp-0.3.2-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.13 | abi3 | Linux glibc 2.17+ x86-64 | Details for mio_decomp-0.3.2-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| mio_decomp-0.3.2-cp313-abi3-macosx_11_0_arm64.whl | CPython 3.13 | abi3 | macOS 11.0+ ARM64 | Details for mio_decomp-0.3.2-cp313-abi3-macosx_11_0_arm64.whl |
Total release size: 1.8 MB
Release files / mio_decomp-0.3.2.tar.gz
| Download URL | mio_decomp-0.3.2.tar.gz |
|---|---|
| Size | 39.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c69ad4d54afa198bf98a7e9c4a11fe44291dc14637503fcc127d315e54342208
|
|
BLAKE2b-256 checksum How to use checksums |
aa80fba10e91a5daa8a11e3a63dafeae4914d1c26f2f13ac219ccd7e2a50392a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / mio_decomp-0.3.2-cp313-abi3-win_amd64.whl
| Download URL | mio_decomp-0.3.2-cp313-abi3-win_amd64.whl |
|---|---|
| Size | 492.6 kB |
| Tags | CPython 3.13 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0ba57cfe6b6bcae39fe5f598266c3ed3153fb63a73809e1bc2b9760a967b036a
|
|
BLAKE2b-256 checksum How to use checksums |
77fc583d6095e01bd058105d01ddbd53059263e1d99660f8cc7e3f2ccdc3e261
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / mio_decomp-0.3.2-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | mio_decomp-0.3.2-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 698.1 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
5bba6e510e9b7a5cdf86fd7cec51119caf2d90ed07b5f599c30cfa01451d62bf
|
|
BLAKE2b-256 checksum How to use checksums |
1d662c6fa30d94fd26c4d106c73d75b90583613584a3f0fda63b3e91816150a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / mio_decomp-0.3.2-cp313-abi3-macosx_11_0_arm64.whl
| Download URL | mio_decomp-0.3.2-cp313-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 559.0 kB |
| Tags | CPython 3.13 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3197493fdc32cb04c2bed7e532ee4d074b374e3d326c3e7b3ec286dad90425a1
|
|
BLAKE2b-256 checksum How to use checksums |
416ab78cc580d8949058ca3ee0c5476bf905452e45c511daed299ad89db8e1fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logSecurity for mio-decomp 0.3.2
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.
Full provenance
All 4 files in this release have been uploaded with provenance metadata.
Attestation for mio_decomp-0.3.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logA 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.
