Satisfactory Save Library
A library to parse and edit save games of the game Satisfactory by Coffee Stain Studios.
Install
pip install satisfactory-save
Usage
import satisfactory_save as s
# Load a save game
save = s.SaveGame('test.sav')
# Store a save game
save.save('test_edit.sav')
# Get save header, e.g., SessionName
print(save.mSaveHeader.SessionName)
A save game could be seen as mainly consisting of objects stored in several levels.
Each object is of a specific class, which is identified by a class name, e.g., a foundation is of the class /Game/FactoryGame/Buildable/Building/Foundation/Build_Foundation_8x4_01.Build_Foundation_8x4_01_C.
For further details about the save game structure, please refer to the detailed documentation here.
To access the save objects, the following methods exist:
# List of objects of the main level (including buildings)
save.mPersistentAndRuntimeData.SaveObjects
# List of other level save objects
for i in range(len(save.mPerLevelDataMap)):
level_name = save.mPerLevelDataMap.Keys[i]
level_objects = save.mPerLevelDataMap.Values[i].SaveObjects
# Unified list of all objects
save.allSaveObjects()
To access the objects by class name, the following methods exist:
save.isObjectClass('/Class/Name')
save.getObjectsByClass('/Class/Name')
To access the objects by path name, the following methods exist:
save.isObjectPath('Path_Name')
save.getObjectsByPath('Path_Name')
Objects can be added and removed to a save game:
# Add object, a level must be provided, -1 refers to the main level
save.addObject(object, level=-1)
# Remove object from save game
save.removeObject(object)
Adding and removing objects is computationally expensive because internal structures are rebuilt every time. To overcome this limitation, an interface to add or remove lists of objects exists:
save.addObjects(objects, level=-1)
save.removeObjects(objects)
For more details about creating objects and adding properties, some examples are available here.
1 maintainer
Metadata
1 maintainer
Release files for satisfactory-save 0.11.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 | Provenance | Actions |
|---|---|---|---|---|
| satisfactory_save-0.11.0.tar.gz | 1.0 MB | With provenance | Details for satisfactory_save-0.11.0.tar.gz |
Built distributions (wheels)
Total release size: 22.4 MB
Release files / satisfactory_save-0.11.0.tar.gz
| Download URL | satisfactory_save-0.11.0.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02c4c387843b1efe2fb4fde5e9b5f4901385fac3f4c19ebfa79a17b89e64ee56
|
|
BLAKE2b-256 checksum How to use checksums |
99b6cdcf333607c28fa04a66a95fac05a04166a31caed41fdf20087410e3679b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp314-cp314t-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
809279c62a26afc5111147b25f301ece33196cb5efe1b1ee1bfa8eb0116a6a65
|
|
BLAKE2b-256 checksum How to use checksums |
2292e98237f53aed8e89b6c535cf7b0dd6afd7b40ca6280f6f7a39defdcfa877
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
54c0226d3278d8140bc6c501dde79eb5b7ca0c56a5e3b737c63b48dc07d5aac9
|
|
BLAKE2b-256 checksum How to use checksums |
c18757127ef2eca2e3745053411f11aabb9a5a321117ffe759ebfba3c00696a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp314-cp314-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e616ec596184ab1036f0df1c73327eec5d8706f98c58f60b4371c750f005c4c1
|
|
BLAKE2b-256 checksum How to use checksums |
ccca34f7a4dc45b4cbb35425d765778c201ee27a021dd1bee678e2c71270b72f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b44b25099054ac2f0f52ac2011b63c513a562b99028d72c4ad6becd362871e13
|
|
BLAKE2b-256 checksum How to use checksums |
2d03708e3634a8f6b9dccb642608e262d21a35141952c2a49753b56247fe292e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp313-cp313-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fb35a2a1fbd34857133652de6f58a3df7ca042fd44d2abd1ac5dee5573728627
|
|
BLAKE2b-256 checksum How to use checksums |
1c01fdf2f53e8245a37573ee75c2272d9d06ba21a112c0f833f663547d92f749
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ac5254030722600db1467ec8041e063e3b687a0ffecaed3cc31c35c152a8172c
|
|
BLAKE2b-256 checksum How to use checksums |
da0274c4d01394e75b38ba2e1356040b58e9226a3bfb4cf616916d0e93894099
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp312-cp312-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a6799f9cf1c66aae8fd021caa464ee1fe52a2577585db3e134b4cfca1ad3c39d
|
|
BLAKE2b-256 checksum How to use checksums |
88d243c093aa48adf383a8c15bdc1b3ed63f043f1cb01b2b417174a29fd231bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
425193f696d94f0dd34c7d4d76dfaf2fcf301fd686aff1d19fd15c41eb085194
|
|
BLAKE2b-256 checksum How to use checksums |
f3dac6c1e4ef1889fdcc80769384061a33eed58eaa1546256f424e3afec74acc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp311-cp311-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6d4b06437ae9f14050e3da2e0ca2079a44199639285b3fe0e0ce261ff0c75c44
|
|
BLAKE2b-256 checksum How to use checksums |
cbe1d245dd499e2cf06373db7f99b0346900958190a043837cc1abd12c338c50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
aaaa2e86043b2b1ffbe4af06a54fb89d35afabfa367716e17b52be2ad7b6b4db
|
|
BLAKE2b-256 checksum How to use checksums |
0e36bca1e8b9db4b3cd580479e70820efec043e463ecfa3c4abd3b4a52ea1dd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp310-cp310-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b3813a5f29b46e974b82af5d5285bf36425490d6a99bc1a11e5452405a4274b3
|
|
BLAKE2b-256 checksum How to use checksums |
9b94b85aeead286c98640063d8eb1bd64b72f9a5568061e435538cdfd74035c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0f55837d4b0f928b0828614d162a6d09d32e633026ae8865fa095c2145e02c70
|
|
BLAKE2b-256 checksum How to use checksums |
9c3b7e08429954c5e0b1850b3ee37b1d82845a182fbeef39cec755158024eba8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp39-cp39-win_amd64.whl
| Download URL | satisfactory_save-0.11.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7c8dad54e5c91cf7300bde77f3437e74861927a104b61bd53a027a233bd3474e
|
|
BLAKE2b-256 checksum How to use checksums |
5e874269c51fd84af38980c033ed9a2e9ec247702185f5ac6002f0df383586d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logRelease files / satisfactory_save-0.11.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | satisfactory_save-0.11.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
304ea522ce257f44891508a2b91d2351fd7c306c33a24e36cc6db92edf9cb0c4
|
|
BLAKE2b-256 checksum How to use checksums |
933acddbfae3ec98116d55b9f98643395764216729a6f3ed0558b164418a0fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 4, 2026.
Transparency logSecurity for satisfactory-save 0.11.0
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 15 files in this release have been uploaded with provenance metadata.
Attestation for satisfactory_save-0.11.0.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 Apr 4, 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.
