I build unofficial ports, runtime patches, modding tools, and quests around PMDO / RogueEssence. Most projects start with “that would be neat” and end with pinned dependencies, hash manifests, hardware test notes, and far more PowerShell than originally planned.
alignment chaotic good
current biome runtime internals
favorite spell git apply --check
boss fight device-specific edge cases
loot reproducible artifacts
| Quest | What escaped the lab |
|---|---|
| PMDO Android Player | An experimental native ARM64 Android player with controller/touch input, dual-screen experiments, verified runtime import, and a save vault. No Windows emulation and no INTERNET permission. |
| Echoes of the Abyss | A bilingual PMDO quest release with Lua content, a tightly scoped runtime patch stack, reproducible packaging, and source provenance. |
| PMDO Widescreen Sidebar | Party status, objectives, and dungeon maps in unused widescreen space—plus deterministic builds, verification passes, and runtime attestations. |
C# / .NET · Kotlin · Lua · PowerShell · Android · RogueEssence · runtime patching · platform porting · reproducible builds · hardware testing
- Unofficial does not mean careless. Compatibility, provenance, and limitations belong in the README.
- Patch, don't redistribute. My projects do not bundle upstream runtimes, proprietary game data, or third-party assets.
- Bring your own legitimate runtime. Imports are verified before activation where the project supports them.
- Make weird builds inspectable. Pin revisions, publish patch series, record hashes, and document the hardware-specific gremlins.
Side quests & rabbit holes
- Poking at Kotlin server code in OpenMMO
- Following the engine trail through RogueEssence
- Finding out exactly how many assumptions a desktop game makes before breakfast
Found something weird? Open an issue with the device, build, exact steps, and logs that do not contain private data. Found something delightful? Tell me what improbable hardware you made it run on.
Stay curious. Respect upstream. Hash your artifacts.
All projects are independent community work. They are not official releases and are not endorsed by upstream developers or rightsholders. See each repository for its exact scope, licenses, and compatibility notes.