Dread Remote Lua
A further modification of Dread depackager, that makes the game listen to a socket, running any lua code sent to it.
Original readme
dread depackager
A modification for Metroid: Dread allowing redirection of files from within pkg files to loose files in RomFS.
usage
dread deapackager expects a json file called "replacements.json" to be placed into the root of the RomFS directory for your mod, and the subsdk9 and main.npdm files in the exefs directory.
replacements.json can have two structures, and it will be automatically detected.
format 1 example:
{
"replacements" :
[
"file1/path/within/pkg",
"file2/path/within/pkg"
]
}
with format 1, file1/path/within/pkg will be directed to rom:/file1/path/within/pkg when the game tries to open it from within a pkg, and instead will open it from the same path within RomFS.
format 2 example:
{
"replacements" :
[
{ "file1/path/within/pkg" : "rom:/mymod/file1" },
{ "file2/path/within/pkg" : "rom:/mymod/file2" }
]
}
with format 2, the RomFS path is arbitrarily defined for any pkg file path, allowing for more flexible organization of the reaplced files in the finished mod
How it works
Dread depackager uses the filepaths listed in replacements.json to selectively replace paths in the game's path to crc conversion code. All file paths first pass through this function, and by hooking it and replacing the string, it can selectively redirect file paths into romfs
dread depackager uses a few libraries:
- exlaunch, a code injection framework for switch executables. Its original readme can be found below
- cJSON, a json parsing library written in C. Dread depackager uses a slightly modified version of this library.
Original exlaunch readme
exlaunch
A framework for injecting C/C++ code into Nintendo Switch applications/applet/sysmodules.
Note
This project is a work in progress. If you have issues, reach out to Shadów#1337 on Discord.
Credit
- Atmosphère: A great reference and guide.
- oss-rtld: Included for (pending) interop with rtld in applications (License here).
Metadata
Release files for open-dread-rando-exlaunch 1.3.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 |
|---|---|---|---|---|
| open_dread_rando_exlaunch-1.3.0.tar.gz | 392.2 kB | With provenance | Details for open_dread_rando_exlaunch-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| open_dread_rando_exlaunch-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for open_dread_rando_exlaunch-1.3.0-py3-none-any.whl |
Total release size: 558.3 kB
Release files / open_dread_rando_exlaunch-1.3.0.tar.gz
| Download URL | open_dread_rando_exlaunch-1.3.0.tar.gz |
|---|---|
| Size | 392.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6b59b61265cc61debd0f0cc3c457135c333e226e85c7ffd097065b92d3a6a24
|
|
BLAKE2b-256 checksum How to use checksums |
6a0ffbedca60348ab4901618a46e6610656901a00ba634497de4820f568b4df3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 18, 2026.
Transparency logRelease files / open_dread_rando_exlaunch-1.3.0-py3-none-any.whl
| Download URL | open_dread_rando_exlaunch-1.3.0-py3-none-any.whl |
|---|---|
| Size | 166.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05f9735621f0c1863650349415547624f8ff15f1c94293b41129f19f85b9875f
|
|
BLAKE2b-256 checksum How to use checksums |
4956bbee51397031f1310f65f68a3c382297d6a7af761bfd152732f0f4d1e40a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 18, 2026.
Transparency logSecurity for open-dread-rando-exlaunch 1.3.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
Both files in this release have been uploaded with provenance metadata.
Attestation for open_dread_rando_exlaunch-1.3.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 18, 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.