NMS.py
NMS.py is a python library to expose interal game functions for No Man's Sky.
NOTE: This library is missing a lot of info which will gradually get added over time. It should also be noted that Game updates can very easily break mods utilising NMS.py, so care should be taken when using mods. Any responsibility for broken saves is entirely on the users of this library.
Also note that this library will never contain functions relating to online functionality to avoid any abuse. The author of this library does not condone any use of this code for any purpose that is directly detrimental to other players.
Installation
Note: It is recommended that you download python from the official site as the windows store version may have issues, as well as the managed python which uv installs.
Note: Python 3.14 is not yet supported. This will come in time but requires some changes to a dependency in pyMHF.
The recommended way to install NMS.py is to simply run python -m pip install nmspy. This will install NMS.py and its' dependency pyMHF into your system python. You can of course install it in a venv or as a dependency using uv if you prefer.
Usage
To run NMS.py, enter the following command into a terminal:
pymhf run nmspy
This will display some config options to complete. The only option to consider is the location of the mods folder. It is recommended that you specify the MODS folder inside the GAMEDATA folder as your mod directory (ie. the same one you put normal mods in).
All mods will be placed in either this folder, or in a chcild folder of this. You can essentially think of any mod using NMS.py being able to be "installed" in the same way you would any other normal mod.
If NMS.py starts up successfully you should see two extra windows; an auto-created GUI from pyMHF, and a terminal window which will show the logs for pyMHF.
If you want to stop NMS, you can press ctrl + C in the window you started the process in to kill it.
Writing mods
Currently the best way to see how to write a mod is to look at the example_mods folder, as well as looking at the pyMHF docs which has comprehensive details on how to use pyMHF.
Contributing
NMS.py can always be better! If you are interested in improving it, the best way to do so is to either make mods using it, or, if you have reverse engineering skills, you can contribute either new functions or new field offsets.
Adding new functions to hook
To add a new function to hook you need to add the details to tools/data.json as well as the nmspy/data/types.py file.
The data for these can generally be found by comparing the structure of the function in the latest exe to either the mac binary or the 4.13 binary.
It is recommended to use either IDA Fusion or SigmakerEX for IDA or some other plugin for any other disassembler to get the unique byte pattern for the function you are providing.
Adding new struct fields
This is a bit trickier and will often involve a good amount of reverse engineering of the exe, comparing the data to the 4.13 binary as well as potentially the mac binary. It is best if a comment is made above the added field so that it's possible to find it again when the game updates so that it's possible to check if the offset has changed.
Credits
Thanks to the developers of minhook, cyminhook and pymem, all of which are instrumental in making this framework possible.
Big thanks to vitalised for their constant RE discussions, and gurren3 for the same as well as the initial work done on NMS.API which heavily inspired the creation of this.
Thanks also to the many people I have discussed various NMS details with, both big and small.
Thanks to RaYRoD for initially discovering the pdb as well as regular insightful discussions regarding all things reverse engineering NMS.
Thanks also to anyone who has contributed function definitions or patterns. Any and all help is always appreciated!
1 maintainer
Metadata
1 maintainer
Release files for NMSpy 170671.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nmspy-170671.6.tar.gz | 494.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nmspy-170671.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 923.4 kB
Release files / nmspy-170671.6.tar.gz
| Download URL | nmspy-170671.6.tar.gz |
|---|---|
| Size | 494.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd6f9b9d612f308b7c0fa5d92f834d97a959231e5075a85e9cf09989404c412c
|
|
BLAKE2b-256 checksum How to use checksums |
7dba954b1882e3e12adfb81f0c3188ace4d9287177c206d80476409b08bb0418
|
| 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 8, 2026.
Transparency logRelease files / nmspy-170671.6-py3-none-any.whl
| Download URL | nmspy-170671.6-py3-none-any.whl |
|---|---|
| Size | 428.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c984a660664cffd8403b40d467a43995bc78b4ebc319074c590c740e3fbeefdc
|
|
BLAKE2b-256 checksum How to use checksums |
d473138544d3d413ab2c81fca5cf4d166043fa7c6f3e988068792caadc8d422d
|
| 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 8, 2026.
Transparency log
