d2r-mobile
Diablo II: Resurrected on iPhone, iPad & Apple silicon Mac. Play offline with touch or a controller, one-tap Runewords and 100-level Greater Rifts. Native ARM + Metal, including Reign of the Warlock. Open source; bring your own Switch game files. 暗黑2重制版 · iOS / macOS.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/d2r-mobile--d2r-mobile)HTML
<a href="/listings/d2r-mobile--d2r-mobile"><img src="/api/listings/d2r-mobile--d2r-mobile/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Both routes start with **the files of the game you bought**: the Switch release of Diablo II: Resurrected plus the Reign of the Warlock expansion, updated to 1.0.34.0 (the version the console shows; it corresponds to PC version 3.3.94012, and the directory names and tools in this repository use the latter number). This project is built for the version with that expansion; using it without the expansion is not supported and has not been verified. How to prepare them is in [docs/GAME_FILES.md](docs/GAME_FILES.md).
> This project provides only tools and an install shell that contains no game content. We do not distribute or endorse, and are not responsible for, any third party distributing game assets, game executables or install packages that contain game content. Please use only game files you legally own.
This project is implemented and verified on the Switch release 1.0.34.0 (which corresponds to PC version 3.3.94012), and by default the tools accept only that version. Community users have reported adapting other versions on their own by following the structure of this repository, and running them successfully. The rule tables are grouped by game version (in `dm/tools/patch_nso.py`, keyed by the build ID of the main program); you are welcome to contribute the version you adapted.
**Check your device first**: the "Which devices are supported" table above tells you which build to use and whether you also need a Legacy Device Pack.
| | With a Mac | Without a Mac | |---|---|---| | Computer | An Apple silicon Mac with Xcode installed | Windows / Linux / a Mac without Xcode | | Method | A full build from source | Download a "shell" with no game content, add your own game content with the packaging tool, then install it with a sideloading tool | | Status | The main route; every number above comes from it | Works end to end on Windows, from making the package to playing on a device, and both systems produce a byte-identical game program. Nobody has tried signing with a sideloading tool yet: try it and tell us | | Instructions | The three steps below | [docs/NO_XCODE.md](docs/NO_XCODE.md) |
The Apple account you sign with: a paid developer account gives you everything. A free Apple ID works too, without iCloud save sync, and you re-sign and reinstall the app every 7 days. [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md) lists every dependency.
The fastest route is [the one-sentence build](#build-it-with-one-sentence): your agent runs the steps below for you.
With a Mac: three steps
1. Put your game files in the workspace (default `~/dm-work`, or set `DM_ROOT`):
~/dm-work/data/switch/3.3.94012/Update/ExeFS/ main, sdk, subsdk0 ~/dm-work/data/switch/3.3.94012/Update/RomFS/ data/…
2. Prepare the workspace. This checks your tools, rewrites the game program, and translates the game's shaders to Metal. The first run takes about 11 minutes; later runs skip finished steps.
./setup.sh source ~/dm-work/build/cache/dm/venv/bin/activate # run everything after this inside the Python environment setup prepared; if you changed DM_ROOT, use it in place of ~/dm-work
3. Fill in your signing details and build the app:
cp dm/ios/local.env.example dm/ios/local.env # set DM_TEAM_ID and DM_BUNDLE_ID; with a free Apple ID also set DM_FREE_ACCOUNT=1 and DM_IOS_UDID, and keep the phone connected while building cd dm/ios && ./run.sh build # targets both iPhone and iPad by default; for iPhone only: DM_DEVICE_FAMILY=1 ./run.sh build
The first time you open the app on your phone, it asks for the "game resource folder": the 18 resource archives from your game files. The section "The "game resource folder" that goes on the phone" in [docs/GAME_FILES.md](docs/GAME_FILES.md) shows where to put them.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 438 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # D2R Mobile · Diablo II: Resurrected for iPhone, iPad, Mac, Android & HarmonyOS
- **Play Diablo II: Resurrected offline on iPhone, iPad, Apple silicon Mac, Android and HarmonyOS.** Native ARM code, Metal on Apple and Vulkan on Android and HarmonyOS. Includes Reign of the Warlock, touch controls and controller support. Bring your own Nintendo Switch game files.
- Drag to aim. Make Runewords in one tap. Clear Hell, then take on 100 levels of Greater Rift and a 12-stage Boss Rush. Play with touch or a controller; the native Mac app also supports keyboard and mouse.
- **[Build & install](#getting-started)** · [Supported devices](#which-devices-are-supported) · [Releases](https://github.com/d2r-mobile/d2r-mobile/releases) · [中文](README.zh-CN.md) · [Español](README.es.md)
- MIT · English / 中文 / Español / Русский / 한국어 / Português · iOS 26+ / macOS 26+; older-API builds support iOS 18+ / macOS 15+. Apple TV 4K has a [community developer preview](dm/tvos/README.md), verified through character selection only.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/hero_en.jpg" width="100%" alt="Diablo II: Resurrected running natively on iPhone, with Harrogath and the red portal to the Greater Rift">
- </p>
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_boss.jpg" width="49%" alt="Touch combat with the boss health bar pinned to the top">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/ipad.jpg" width="49%" alt="True full screen on iPad">
- </p>
- | Locked 60 fps | 10 h battery | 1-tap Runewords | 100-level Greater Rift | Uber Boss Rush | 1 s to play |
- |:---:|:---:|:---:|:---:|:---:|:---:|
- | No drops once the phone warms up | Per charge, in power saver mode | Long-press a base, socket every rune | Skill cap rises from 20 to 40 | 12 stages, ending with Diablo Clone and the Ubers | From the main menu into a game |
- Performance readings are from iPhone 17 Pro Max. Battery life is estimated from measured power use at 30 fps. [Measurement conditions](#speed-and-battery).
- ## Build it with one sentence
- Have your own game files ready, then tell Claude Code or Codex:
- ```
- Use the d2r-mobile skill from https://github.com/d2r-mobile/d2r-mobile to build D2R Mobile for my iPhone. My game files are in <path>.
- ```
- The agent checks your machine, prepares the workspace, signs and installs the app, and copies the game resources to your phone. It stops to ask you for your Apple signing details and before any install that needs `sudo`. The skill lives at [skills/d2r-mobile/SKILL.md](skills/d2r-mobile/SKILL.md), and both agents find it on their own through `.claude/skills/` and `.agents/skills/`. For manual builds and installation, see [Getting started](#getting-started).
- ## Why it plays like a native game
- - **Your phone runs the original program.** iPhone and Switch use the same family of ARM processors. The rewriter changes only the instructions Apple's kernel rejects (thread-pointer registers, system calls, timers) and leaves every other byte as shipped. Classes, Runewords, Terror Zones, bosses, drop rules and quests match the original because they are the original code.
- - **Graphics go straight to Metal.** A small host written for Apple platforms provides the system calls, files, audio and input the game expects, and reimplements its graphics API on Metal. The build translates every shader offline, so you never wait on a shader compile when you enter a new area.
- - **Older chips get their own textures.** A16 and earlier chips lack the game's compressed texture format. The build adds a supplementary texture pack for them, and those phones hold 60 fps too.
- ## What ships, and what you bring
- The repository ships the rewriter, the host, the graphics layer, the iOS app, the test tooling and the full build pipeline. It ships no game program, art, text, data tables or shaders: your own machine generates all of that from your own files (see [docs/GAME_FILES.md](docs/GAME_FILES.md)). The interface details we recorded to make the port work, such as shader interface descriptions, the graphics API function table and addresses inside the program, are listed item by item in [docs/DERIVED.md](docs/DERIVED.md).
- The game runs fully offline and needs no online account. Multiplayer is out of scope.
- ## Battle-tested
- All **44** iPhones and iPads in the closed beta **cleared Normal, Nightmare and Hell with several characters**: 35 registered devices (25 iPhones and 10 iPads) plus 9 TestFlight accounts with one device each. The oldest, an iPhone 14 Pro Max with 6 GB of memory, holds 60 fps.
- | | Models |
- |---|---|
- | iPhone | 14 Pro Max, 15, 15 Pro, 15 Pro Max, 16 Plus, 16 Pro, 16 Pro Max, 17 Pro Max and more |
- | iPad | iPad Air, iPad mini, iPad Pro 11-inch and 12.9 / 13-inch (including M2 and M4) and more |
- | Lowest model tested | **iPhone 14 Pro Max (A16, 6 GB): a steady 60 fps** |
- One install package covers iPhone and iPad.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/act1.jpg" width="19%" alt="Act I">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/act2.jpg" width="19%" alt="Act II">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/act3.jpg" width="19%" alt="Act III">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/act4.jpg" width="19%" alt="Act IV">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/act5.jpg" width="19%" alt="Act V">
- </p>
- ## Speed and battery
- Measured on an iPhone 17 Pro Max:
- | Item | Reading |
- |---|---|
- | In-game frame rate | **60 fps**, steady, with no drops once the device warms up |
- | App launch | 0.15 s |
- | To the main menu | about 1 s |
- | From the main menu into a game | **about 1 s** |
- | Quick Restart, back in a game | about 1.2 s |
- | Longest frame when changing acts | about 0.1 s |
- | Whole-device power, 60 fps | **about 3.8 W** (in camp, 50% brightness): close to 5 hours of play on a full charge |
- | Whole-device power, power saver mode at 30 fps | **about 1.85 W**: close to 10 hours of play on a full charge |
- <sub>Measurement conditions: whole-device power measured on 2026-10-10 on an iPhone 17 Pro Max, standing in the Act I camp at 50% brightness, with 60 fps and power saver mode measured in the same scene. Battery life comes from the measured power and the battery capacity, not from playing a full charge down to empty. Launch and game-entry times were measured on the same model in 2026-10; frame rate and act-change readings were taken on the same model on 2026-10-12 while moving through areas and changing acts.</sub>
- The install package is a little over 100 MB. The game resources (about 5.6 GB) go onto the phone separately, and app updates leave your saves and resources alone.
- Why it is this fast: the program executes natively, and not a single instruction goes through emulation; graphics go straight to Metal; every shader is translated offline and compiled ahead of time, so nothing is compiled when you enter a new scene. Older chips (A16 and earlier, such as the iPhone 14 family and iPhone 15) do not support the game's original compressed texture format; they need an extra texture pack made from your own game files, and then run at full frame rate too — see [docs/LEGACY_DEVICES.md](docs/LEGACY_DEVICES.md).
- We rebuilt every panel and every action for touch, with one rule: **keep the original interface language, and use gestures in place of extra buttons**. Text and tap targets are sized for fingers. You can play the moment you pick it up, and long sessions stay comfortable.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/touch_game.jpg" width="49%" alt="The touch interface: stick and skill buttons">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_belt.jpg" width="49%" alt="In camp: belt with potions, mercenary portrait and minimap">
- </p>
- - **Move**: a virtual stick with precise diagonals. Tap an NPC or the ground to walk there. Doors, portals and cave entrances respond to a tap anywhere on their surface.
- - **Fight**: press a skill button to cast, hold to keep casting, and **drag to aim at any angle**; nearby monsters get targeted for you. You get two skill sets. Skills on your secondary weapons cast with one tap: the game swaps weapons, casts and swaps back, and the button shows the charges left.
- - **Boss health bar**: pinned to the top of the screen with the percentage remaining.
- - **Items**: tap, double-tap, long-press and drag and drop all follow your finger. Double-tap gear to equip or unequip it. Drag an item anywhere onto the vendor panel to sell it. On a stack, double-tap takes 1 and long-press takes 3. Long-press an empty inventory slot to sort everything.
- - **Text**: you type with the system keyboard. Character names can be in Chinese; leave the name blank for a random one.
- - **Screen**: on iPhone the game fills the 19.5:9 display edge to edge, clear of the notch and rounded corners. On iPad it fills the whole screen, and the interface centers itself when you open a panel. You can brighten the 3D picture.
- ### Controller
- Connect a controller and press any button: the interface switches to the original controller layout, with button prompts at the bottom of every panel. Touch the screen and you are back in the touch interface instantly. Inventory, stash, skill tree, Chronicle and settings are fully controller-navigable, with the same button mapping as on Switch. With an Xbox controller the layout switches automatically to the PC / Xbox one (bottom confirms, right goes back) and the prompts show Xbox button icons; there is nothing to turn on. With a PlayStation controller (DualSense or DualShock 4) the prompts switch to the game's own PlayStation button icons (✕ confirms, ○ goes back), contributed by [@Ti800](https://github.com/Ti800).
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_pad_combat.jpg" width="49%" alt="Combat with a controller connected">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_pad_inventory.jpg" width="49%" alt="Navigating the stash with a controller, button prompts at the bottom">
- </p>
- ## Endgame on top of the original
- Clear Hell and a new endgame opens up. None of it changes the original rules.
- ### Greater Rift
- Enter through the red portal in Harrogath. The Rift has 100 levels, and the monsters grow stronger on each one. Fill the progress bar and kill the Rift Guardian within 15 minutes to clear a level. Every 2 levels grant +1 Skill Point and +5 Stat Points, and the skill level cap rises from 20 to 40. Every 10th level has a first-clear reward, and clearing level 10 unlocks six new equipment slots for your mercenary.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_panel.jpg" width="40%" alt="The Greater Rift level select panel">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/rift_game.jpg" width="58%" alt="Combat inside a Greater Rift">
- </p>
- ### Boss Rush, Elysium mode and the Kill Board
- - **Endgame Boss Rush**: 12 stages after you clear Hell. Stage 11 is Diablo Clone, and stage 12 is the three Uber bosses.
- - **Elysium mode** (you choose it at character creation): Unique ×5, Set ×3, Runes ×5. The "no drop" chance falls to a tenth, and every boss kill drops like a first kill.
- - **Kill Board**: for every boss, your kill count, the time of your first kill, the Unique and Set items it has dropped, and your best and average kill times.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_killboard.jpg" width="49%" alt="The Kill Board">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_mode_select.jpg" width="49%" alt="Choosing Elysium mode at character creation">
- </p>
- ### Storage for collectors
- - **Chronicle stash**: every identified Unique and Set item has its own fixed slot, shared by all your characters, with search, deposit and withdraw. The Deposit button sends the Unique and Set items in your inventory and Horadric Cube there in one tap.
- - **Stash**: 14 columns wide, with 5 personal pages and 5 shared pages.
- - **Trove**: the gem, rune and material pages merged into one, with the Horadric Cube's crafting grid in the middle, so you find and craft on one page. Runes, gems and materials you put into the personal or shared pages get filed here for you.
- - **Pouch**: an extended inventory. Runes and gems you find in the field go into it and take up no inventory space.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_trove.jpg" width="49%" alt="The Trove: gems, runes, materials and the crafting grid on one page">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_chronicle.jpg" width="49%" alt="The Chronicle stash">
- </p>
- ### Less busywork while you farm
- | | |
- |---|---|
- | Runeword helper | Long-press a socketed base to list the Runewords it can make and their stats. Once you have the runes, socket them all in one tap |
- | Auto-recast buffs | Your learned buffs need no slot on the skill bar. When a buff runs out, the game recasts it the moment you stand still. Buffs from your secondary weapons (such as Battle Orders from Call to Arms) swap weapons, recast and swap back |
- | Potions and belt | Auto-drink has two tiers: a healing potion below 50% Life, a rejuvenation potion below 30%. **Your mercenary drinks by the same rule.** You pick up potions on the ground when the belt has room, and a double-tap on an empty belt slot refills the whole belt |
- | Loot filter | From Nightmare on, the original loot filter switches on to hide clutter: light filtering in Nightmare, heavy in Hell |
- | Auto-pickup | Low runes and gems go straight into the Pouch; you pick up the high ones yourself |
- | Valuable drop alerts | High runes and Unique items raise a light beam and land with their own sound. The phone vibrates light, medium or heavy according to value |
- | Minimap guidance | Every map marks its Waypoint and exits, labelled with the Waypoint and destination area names (iOS / Mac). Every quest goal sits on the map. When a target is off screen, its name runs along the screen edge |
- | Chores removed | Free identification, free Town Portal with no scrolls, spawning beside the Waypoint, Quick Restart, refreshable vendor stock, free and unlimited respecs at Akara |
- | Saves | The game saves the moment you switch apps, swipe the app away or quit. iCloud syncs your saves across devices (requires signing with a paid developer account) |
- | Entertainment mode (experimental) | Over-the-shoulder and first-person camera: drag the right half to look around, with arrows for off-screen monsters and a facing pointer on the map ([details](docs/over-the-shoulder-camera.md)) |
- You can toggle most features one by one in game under Options → Custom.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_runeword.jpg" width="32%" alt="The Runeword helper">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_map_goal.jpg" width="33%" alt="The quest goal named under the area name, next to the minimap">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_map.jpg" width="33%" alt="The full-screen map">
- </p>
- ### English, Chinese, Spanish, Russian, Korean and Portuguese
- The whole game switches between English, Chinese, Spanish, Russian, Korean and Portuguese under Options → Custom (six options in two rows of three); after a restart, the interface is in the language you chose. On first launch it follows your device language (Spanish from Spain uses the game's esES text, other Spanish regions use the Latin American esMX text; Portuguese uses the game's ptBR text). In English, Spanish, Russian, Korean and Portuguese, items, skills and monsters use the original Diablo II wording, and everything we added — Greater Rift, Chronicle, the settings page, gesture prompts, map name plates — is translated too (item notes are translated for Chinese and Spanish only). Russian is the game's single ruRU text, Korean its koKR text and Portuguese its ptBR (Brazilian) text, with no regional variants. Voice acting: Chinese UI gets Chinese voices; Russian, Korean and Portuguese get the original voices when your game files include them (a package built from the complete game data does), otherwise English; everything else is English.
- <p align="center">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/en_game.jpg" width="58%" alt="Gameplay with the English interface">
- <img src="https://github.com/d2r-mobile/d2r-mobile/releases/download/assets/rift_panel_zh.jpg" width="40%" alt="The same Greater Rift panel in Chinese">
- </p>
- ## How it works
- ```mermaid
- flowchart LR
- G["Your game files<br/>(program + resources)"] --> P["Rewriter<br/>changes only a few instructions"]
- G --> S["Shader translation<br/>original → Metal"]
- P --> H["Host<br/>system services"]
- S --> X["Graphics layer<br/>the graphics API on Metal"]
- H --> A["iOS app<br/>touch and interface"]
- X --> A
- ```
- | Part | Where | What it does |
- |---|---|---|
- | Program rewriter | `dm/tools/patch_nso.py` | Rewrites only the few instructions that cannot run unchanged under Apple's kernel (thread-pointer registers, system calls, timers) and leaves the rest of the program byte for byte as shipped |
- | Host | `dm/host` | Loads the rewritten program and provides the platform services it calls |
- | Graphics | `dm/gfx` | Implements the game's graphics API on Metal; the build translates shaders offline from the game's originals |
- | iOS app | `dm/ios` | The app shell, touch controls and interface |
- | Android app | `dm/android` | The Android shell, touch overlay and Vulkan presentation |
- | HarmonyOS app | `dm/harmony` | The HarmonyOS shell (ArkTS + N-API), sharing the host and the Vulkan engine with Android |
- | Vulkan graphics | `dm/gfx/vulkan` | The same graphics API on Vulkan (shared by Android and HarmonyOS; the engine comes from the HarmonyOS port) |
- | Verification | `dm/verify` | Checks that the rewritten code behaves exactly like the original, plus the regression gates every change goes through |
- **Tests ship with the code.** The project includes unit tests for the host and graphics layers, an equivalence check for every rewritten instruction, scripted walkthrough regression for the touch interface, and on-device smoke tests. Start with `make -C dm/host/tests run`, `make -C dm/gfx/tests run` and `dm/verify/regress.sh` (run them inside the Python environment from step 2 below; `regress.sh` also needs `brew install llvm`). [CONTRIBUTING.md](CONTRIBUTING.md) covers how to send changes.
- ## Android (new in v2.0)
- Android phones execute the game's ARM64 program directly. Android and Apple share the host code for system calls, files, audio, input and saves; Android uses the NVN-to-Vulkan engine for graphics.
- Measured by the port's authors on their phones (product defaults: 3D render scale capped at 0.85 and lowered dynamically when frames drop):
- | Phone | Result |
- |---|---|
- | Redmi K50 Ultra (Snapdragon 8+ Gen 1, Adreno 730, Android 15) | Camp, Den of Evil fight, Cow Level fight: **median 60 fps**, GPU about 14–15 ms a frame |
- | OnePlus 13 (Adreno 830) | Playable; when one particular light effect appears in the camp, small black squares occasionally flash for an instant (under investigation) |
- Minimum: ARM64, Android 12 (API 31) or later, and a GPU with Vulkan 1.1.
- **Build and install**: follow the [Android build guide](dm/android/README.md) to build the APK. Run `python3 dm/tools/d2rm_android.py <Update directory> <output directory>` with your own game files, then copy the generated `android` folder and game resources (`data`) to `Download/S2X/D2R Mobile/` on the phone. Open the app to import them. See the [installation guide](docs/ANDROID.md) for the full steps.
- Progress, the measurements from every round and the remaining work are in [docs/ANDROID_COLLABORATION.md](docs/ANDROID_COLLABORATION.md) and [docs/android-notes/](docs/android-notes/). The HarmonyOS version is in the next section.
- ## HarmonyOS (new in v2.0)
- The HarmonyOS NEXT app (`dm/harmony`) shares the host and Vulkan engine with Android. See the build guide for the recorded installation, import and save checks on a Mate 90 Pro Max.
- **Build and install**: follow the [HarmonyOS build guide](dm/harmony/README.md), sign the app with your own developer certificate and install it. Run `python3 dm/tools/d2rm_android.py --target ohos <Update folder> <output folder>` to prepare the runtime pack, then import it with your own game resources. See the [installation guide](docs/HARMONYOS.md) for the full steps.
- ## Which devices are supported
- Minimum: **an A14 / M1 chip or later** — the graphics layer needs Metal 3, which Apple supports from A14 / M1 on (see Apple's [Metal support on Apple devices](https://support.apple.com/102894) and [Metal Feature Set Tables](https://developer.apple.com/metal/Metal-Feature-Set-Tables.pdf)).
- | Device | Playable? | How | How sure we are |
- |---|---|---|---|
- | **iPhone / iPad, A17 Pro and later** (iPhone 15 Pro and later, iPhone 16 and later, iPads with M-series chips) | Yes | iOS 26 or later: the default shell / default build; iOS 18 – 25: the iOS 18 shell / [older-API build](docs/OLDER_SYSTEMS.md) | Main devices, played daily |
- | **iPhone Duo** (foldable) | Yes; the picture resizes when you unfold or fold | The shells on the Releases page are built with Xcode 27.1; when building with Xcode yourself, use 27.1 so the inner screen is filled (see [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md)) | Supported since v2.0. Checked on a Mac switching between the outer and inner screen sizes taken from the iPhone Duo simulator (the simulator itself cannot run the game's graphics). We will test on a real iPhone Duo as soon as we have one; if you have the phone, please tell us how it goes in an Issue |
- | **iPhone / iPad, A16 and earlier** (all iPhone 14 models, iPhone 15 / 15 Plus, iPhone 13 series and so on) | Yes, with one extra step | Make a Legacy Device Pack from your own game files as in [docs/LEGACY_DEVICES.md](docs/LEGACY_DEVICES.md) and include it when making the install package; the system split is the same as the row above | Played by players: iPhone 14 Pro Max (A16, 6 GB) at 60 fps; iPhone 13 Pro Max (A15, 6 GB) in the 30 fps mode |
- | **Devices with 4 GB of RAM** (such as the 6th-generation iPad mini or the 4th-generation iPad Air) | Runs, but memory is very tight (we are still reducing memory use) | Same as the A16-and-earlier row (with the Legacy Device Pack) | Tested by a player: on an iPad mini 6 (A15, 4 GB, iPadOS 27) a few minutes of Act I ran at 50–58 fps after automatic quality reduction, with constant system memory warnings and only about 560 MB below the system memory limit — busy scenes with many monsters and effects may be ended by the system; on an earlier version an iPad Air 4 (A14, 4 GB) was ended by the system a few seconds after launch |
- | **A14 chips with 6 GB of RAM or more** (such as iPhone 12 Pro / 12 Pro Max) | No reports yet | Same as the A16-and-earlier row | If you have tried, please open an Issue and tell us |
- | **A13 and earlier chips** (such as the iPhone 11 series and the 2020 iPad Pro) | Not supported | — | The graphics chip does not support Metal 3 (tested by a player on an iPad Pro with A12Z; Apple's references are above the table); the app says so at launch instead of crashing |
- | **Mac, Apple silicon** | Yes (native macOS App) | macOS 26 or later: the default build; macOS 15 – 25: the [older-API build](docs/OLDER_SYSTEMS.md). Keyboard, mouse and gamepad all work; what each can do is in [docs/MAC.md](docs/MAC.md) | A player has played the older-API build on macOS 15.7.7 |
- | **Apple TV 4K (3rd generation, A15)** | Developer preview under the MIT License | Build as in [dm/tvos/README.md](dm/tvos/README.md) and copy the game files and the Legacy Device Pack into the app; real hardware only, the Simulator cannot run it; saves live in the Caches directory, which the system may purge | Reached the character-selection screen on real hardware; entering the game, full controller mapping and saves are not verified yet, and the maintainers have not tested it on real hardware |
- | **HarmonyOS phones** (HarmonyOS NEXT, API 26) | Playable (community port) | A locally built app signed with your own debug certificate, plus a runtime pack made from your own game files, see [docs/HARMONYOS.md](docs/HARMONYOS.md) | Verified by the author on a Mate 90 Pro Max: re-sign, install, import, into a game, save and exit |
- | **Android phones** (ARM64, Android 12 or later, Vulkan 1.1) | Playable (community port) | A locally built APK + an import pack made from your own game files, see [docs/ANDROID.md](docs/ANDROID.md) | Measured by the port's authors: Redmi K50 Ultra median 60 fps; OnePlus 13 playable, with occasional black squares flashing for an instant; played on a vivo X200 Ultra |
- | **Intel Macs** | Not supported | — | — |
- **What the dialogs in the App mean**
- - **"One More Step for This Device"**: this phone can run the game; the install package was made without the Legacy Device Pack. Make the pack as in [docs/LEGACY_DEVICES.md](docs/LEGACY_DEVICES.md), make the install package again with it and reinstall.
- - **"Device Not Supported … iPhone 15 Pro and later can play"**: this is the old text from before v1.0.9. You are on an old version; update to the latest. For A16 and earlier devices, then follow the line above.
- **What a package you build yourself does not have, compared with our test-group builds**: the public version can be built and installed with a free Apple ID. Three things in our test-group builds are not in it: iCloud save sync (the App needs the iCloud signing entitlement, which a self-signed package does not have), downloading packs and resources inside the App, and new-version notices (these two use our own server). The game itself and the features we added are the same.
- ## Getting started
- Whatever device you play on, you start with **the files of the game you bought**: the Switch release of Diablo II: Resurrected plus the Reign of the Warlock expansion, updated to 1.0.34.0 (the version the console shows; it corresponds to PC version 3.3.94012, and the directory names and tools in this repository use the latter number). This project is built for the version with that expansion; using it without the expansion is not supported and has not been verified. How to prepare them is in [docs/GAME_FILES.md](docs/GAME_FILES.md).
- > This project provides only tools and an install shell that contains no game content. We do not distribute or endorse, and are not responsible for, any third party distributing game assets, game executables or install packages that contain game content. Please use only game files you legally own.
- This project is implemented and verified on the Switch release 1.0.34.0 (which corresponds to PC version 3.3.94012), and by default the tools accept only that version. Community users have reported adapting other versions on their own by following the structure of this repository, and running them successfully. The rule tables are grouped by game version (in `dm/tools/patch_nso.py`, keyed by the build ID of the main program); you are welcome to contribute the version you adapted.
- **Check your device first** and find your section in the table below; the "Which devices are supported" table above tells you which build to use on Apple devices and whether you also need a Legacy Device Pack.
- | Your device | How | Steps |
- |---|---|---|
- | iPhone / iPad, with an Apple silicon Mac | A full build from source | "With a Mac: three steps" below |
- | iPhone / iPad, without a Mac | Download a shell with no game content and add your game content on Windows / Linux | "Without a Mac" below and [docs/NO_XCODE.md](docs/NO_XCODE.md) |
- | Mac (Apple silicon) | Build a native macOS App | "Playing directly on a Mac" below and [docs/MAC.md](docs/MAC.md) |
- | Android phone | Build and install the APK, then copy your import pack to the phone | "Android" below and [docs/ANDROID.md](docs/ANDROID.md) |
- | HarmonyOS phone | Build and sign the app with your own certificate, then prepare and copy your runtime pack | "HarmonyOS" below and [docs/HARMONYOS.md](docs/HARMONYOS.md) |
- The two routes for iPhone / iPad compared:
- | | With a Mac | Without a Mac |
- |---|---|---|
- | Computer | An Apple silicon Mac with Xcode installed | Windows / Linux / a Mac without Xcode |
- | Method | A full build from source | Download a "shell" with no game content, add your own game content with the packaging tool, then install it with a sideloading tool |
- | Status | The main route; every number above comes from it | Works end to end on Windows, from making the package to playing on a device, and both systems produce a byte-identical game program. Nobody has tried signing with a sideloading tool yet: try it and tell us |
- | Instructions | The three steps below | [docs/NO_XCODE.md](docs/NO_XCODE.md) |
- The Apple account you sign with: a paid developer account gives you everything. A free Apple ID works too, without iCloud save sync, and you re-sign and reinstall the app every 7 days. [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md) lists every dependency.
- The fastest route is [the one-sentence build](#build-it-with-one-sentence): your agent runs the steps below for you.
- ### With a Mac: three steps
- 1. Put your game files in the workspace (default `~/dm-work`, or set `DM_ROOT`):
- ```
- ~/dm-work/data/switch/3.3.94012/Update/ExeFS/ main, sdk, subsdk0
- ~/dm-work/data/switch/3.3.94012/Update/RomFS/ data/…
- ```
- 2. Prepare the workspace. This checks your tools, rewrites the game program, and translates the game's shaders to Metal. The first run takes about 11 minutes; later runs skip finished steps.
- ```
- ./setup.sh
- source ~/dm-work/build/cache/dm/venv/bin/activate # run everything after this inside the Python environment setup prepared; if you changed DM_ROOT, use it in place of ~/dm-work
- ```
- 3. Fill in your signing details and build the app:
- ```
- cp dm/ios/local.env.example dm/ios/local.env # set DM_TEAM_ID and DM_BUNDLE_ID; with a free Apple ID also set DM_FREE_ACCOUNT=1 and DM_IOS_UDID, and keep the phone connected while building
- cd dm/ios && ./run.sh build # targets both iPhone and iPad by default; for iPhone only: DM_DEVICE_FAMILY=1 ./run.sh build
- ```
- The first time you open the app on your phone, it asks for the "game resource folder": the 18 resource archives from your game files. The section "The "game resource folder" that goes on the phone" in [docs/GAME_FILES.md](docs/GAME_FILES.md) shows where to put them.
- `./setup.sh check` is a health check: it reports the state of this computer, the tools, the game files and the signing configuration item by item, and for everything missing it says where to get it and which command to run next; it changes nothing. If what you have is a whole game package (`.xci` / `.nsp`), `./setup.sh <game package> <prod.keys>` first extracts the game files into place and then carries on (install hactool first); if the base game and the update are separate packages, give both: `./setup.sh <base game> <update> <prod.keys>`. Run `./setup.sh` again after every update to a new commit: it rebuilds the patched binaries and the shader library for the current sources (steps that are already up to date are skipped). It also rewrites three files in the repository that change with your local tool fingerprints (`dm/gfx/tools/dmsh_chain.lock`, `dm/gfx/nvn/dmsh_chain.h`, `dm/gfx/nvn/c1_full.tsv`); that is expected, do not commit them.
- ### Playing directly on a Mac
- After the same `./setup.sh`, one more command builds a native macOS App that starts on double-click and works with keyboard, mouse and gamepad, with no developer account:
- ```bash
- source ~/dm-work/build/cache/dm/venv/bin/activate
- dm/tools/mac_app.sh # macOS 26 or later: produces ~/dm-work/out/macapp/D2R Mobile.app
- DM_MAC_M3=1 dm/tools/mac_app.sh # macOS 15 – 25: produces D2R Mobile M3.app
- ```
- The interface is the original's gamepad interface. Keyboard: Space confirms, Esc goes back, Return, the `=` key opens the menu / a new character, W A S D moves, and every other gamepad button has a key. Mouse: clicking a monster, NPC or object walks over and interacts, and the skill slots, potion cells and key hints at the bottom, buttons and tabs in panels, the class figures when creating a character and the minimap can all be clicked; clicking empty ground walks there and holding keeps walking, clicking a monster attacks it, and items take double clicks and drags. With a keyboard, the prompts on screen show keyboard keys. Saves stay on this Mac (iCloud sync needs a paid developer account and a build with `DM_MAC_ICLOUD=1`, see [docs/MAC.md](docs/MAC.md)) and can be imported by hand from an iPhone / iPad. The key table, how to create a character, what the mouse can do, the import steps and the known shortcomings are in [docs/MAC.md](docs/MAC.md). Keyboard and a physical gamepad have not been operated by a person yet — if you try it, please tell us how it went.
- ### Android
- Build the APK from source, then prepare your own game content on a computer. Import-pack generation has been verified on a Mac. For build steps, required tools and troubleshooting, see [docs/ANDROID.md](docs/ANDROID.md).
- 1. Prepare your game files, the same as for Apple devices ([docs/GAME_FILES.md](docs/GAME_FILES.md)).
- 2. Make the import pack on a computer:
- ```
- python3 dm/tools/d2rm_android.py <Update directory of your game files> <output directory>
- ```
- 3. Over USB, copy the `android` folder it made and the game resource folder `data` to `Download/S2X/D2R Mobile/` on the phone.
- 4. Build and install the APK using the [Android build guide](dm/android/README.md), open it and allow "All files access". The app imports your pack and starts the game.
- Before starting the game, the Android startup screen can export saves to a ZIP or restore an exported backup. Restore keeps a local ZIP backup of the previous saves. See [save backups](dm/android/ANDROID_CUSTOMIZATIONS.md#startup-save-backups--启动页存档备份) for details; device validation is pending.
- The source must be from the same release as the APK; for a new release, replace both the APK and the import pack, and your saves stay. To build the APK yourself from source, see [dm/android/README.md](dm/android/README.md).
- ### HarmonyOS
- Build the app using the [HarmonyOS build guide](dm/harmony/README.md). You need a Huawei developer account and DevEco Studio (for its signing tool and `hdc`; it can also generate the debug certificate and register the phone). The full steps, commands and what to do when something fails are in [docs/HARMONYOS.md](docs/HARMONYOS.md).
- 1. Prepare your game files, the same as for Apple devices ([docs/GAME_FILES.md](docs/GAME_FILES.md)).
- 2. Build the HAP using the [HarmonyOS build guide](dm/harmony/README.md), sign it with your own debug certificate and profile, then install it with `hdc install -r`.
- 3. Make the runtime pack on a computer:
- ```
- python3 dm/tools/d2rm_android.py --target ohos <Update folder of your game files> <output folder>
- ```
- 4. On the phone, make a "D2R Mobile" folder with the game resources in `data/` and the runtime pack from the previous step in `dm/`, open the app, tap Import and pick that folder.
- The source must be from the same release as the shell. For a new release, re-sign the new shell with the same signing and install it over the old one; your saves are kept. The author ran these steps on a Mate 90 Pro Max.
- ### Without a Mac: the shell plus the packaging tool
- Download our prebuilt "shell" package (`D2RMobile-shell-build-input.zip`; `D2RMobile-shell-ios18-build-input.zip` for iOS 18 – 25), which contains no game content, from this repository's [Releases page](https://github.com/d2r-mobile/d2r-mobile/releases), add your own game files, make the install package on Windows or Linux, then sign and install it with a sideloading tool. The shell is build input, not an app to install (installed as is, it only shows a dialog and does not start the game); when you move to a new release, make the install package again with the new shell. On this route only, because the computer making the package has no Apple shader compiler, the **first launch** on the phone spends about 7 minutes compiling shaders (once, with a progress bar); a package built with Xcode has no such step. The steps, and how far each one has been verified, are in [docs/NO_XCODE.md](docs/NO_XCODE.md).
- ## Known limitations
- | Item | Status |
- |---|---|
- | Online play | Out of scope; fully offline |
- | Android version | A few iOS touch details (empty-skill-slot menu, stat-point overlay, the item image that follows your finger in a shop) are unfinished; see "Android" above |
- | `.nsp` / `.xci` game packages | The tools only check the version of the main program and do not distinguish package formats; we ran the whole path with an `.xci` ourselves, and users have reported that `.nsp` packages work perfectly as well |
- | Signing and installing with a sideloading tool (Sideloadly, AltStore and the like) | Not verified; open an issue and tell us how it went |
- | Making the package on Linux | Not verified (verified on Windows and Mac) |
- | Devices that have not moved to iOS 26 / macOS 26 | Playable with the older-API build (minimum iOS 18.0 / macOS 15.0): [docs/OLDER_SYSTEMS.md](docs/OLDER_SYSTEMS.md); the full device table is under "Which devices are supported" above |
- | A16 and earlier devices (iPhone 14 family, iPhone 15 / 15 Plus and so on) | Playable; they need a Legacy Device Pack and an App built with it: [docs/LEGACY_DEVICES.md](docs/LEGACY_DEVICES.md). "One More Step for This Device" (older versions say "Device Not Supported") in the App means this step is missing |
- | The "one-line verdict" and "legacy Chinese name" entries in item notes | These two content tables are not shipped with the repository; you can supply your own, see `dm/ios/tools/annot/README.md` |
- ## Contributing and feedback
- - If you hit a problem, open an issue (there is a template). The file from Share Diagnostics in the pause menu helps the most.
- - For the items marked not verified, tell us whether they worked. Either answer helps.
- - To change the code, get the test entry points above passing first. Every change has to pass the regression gates.
- **Taking it to other platforms:** this approach is not limited to iPhone and iPad. Apple silicon Macs already have a native version (see "Playing directly on a Mac" above), built from the same game program and the same host; Apple TV also has a community port (developer preview, see the device table). Android has been reached too: since v2.0 there is a community-ported Android version (see "Android" above) built on the same host, with only the graphics layer swapped for Vulkan; a HarmonyOS version has arrived too (see "HarmonyOS" above), sharing the same Vulkan engine.
- **Taking it to other games:** someone has already tried other Switch games on the same host. The host has some behaviour that is on by default on iOS and was written for this one game; another game runs into these first, so turn them off or move them out before you start:
- - `dm/host/hle_oe.c`: the 3D render scale defaults to 0.75 on phones (the Android app sets 0.85), and `scale3d_tick` rewrites it at offsets inside this game's renderer — with another game that is a wild pointer.
- - `dm/host/hle_fs.c`: seeding the shared stash on first launch (`DM_STASH_SEED`) and the touch-layout default settings (`DM_TOUCH_DEFAULTS`) are on by default on iOS.
- - `dm/host/main.c`: the save-flush throttle patches a constant at a fixed address in the game program; `argv[0]` is hard-coded to `"D2R"`.
- - `dm/host/hle_time.c`: the fixed-time test switch recognises a fixed address in the game program.
- - `front_game_res` in `dm/host/front_mac.m`: the docked / handheld resolutions are hard-coded to 1600×900 / 1280×720.
- - `dm/host/dm_cloudsync.c`: character directories are recognised by `.d2s`.
- - `dm/host/dm_cursor.c` and `dm/host/dm_world.c`: the whole files are specific to this game.
- The cleaner arrangement is to move these defaults into per-game configuration and keep the host free of game-specific defaults; pull requests in that direction are welcome.
- ## Documentation by part
- | Document | Covers |
- |---|---|
- | [dm/README.md](dm/README.md) | How the whole thing works, directory layout, common commands, the host's source files |
- | [dm/gfx/README.md](dm/gfx/README.md) | The graphics layer and the shader translation chain |
- | [dm/ios/README.md](dm/ios/README.md) | The iOS shell, building and smoke testing |
- | [dm/verify/README.md](dm/verify/README.md) | What each verification tool checks and what it needs |
- | [docs/GAME_FILES.md](docs/GAME_FILES.md) | Game files: which ones you need, how to get them from your own console, where to put them |
- | [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md) | Dependencies and third-party licenses |
- | [docs/NO_XCODE.md](docs/NO_XCODE.md) | Building without Xcode and without a Mac |
- | [docs/MAC.md](docs/MAC.md) | Playing on a Mac: building the macOS app, key mapping, and known limitations |
- | [docs/LEGACY_DEVICES.md](docs/LEGACY_DEVICES.md) | Older devices (A16 and earlier): making the texture pack and putting it on the phone |
- | [docs/OLDER_SYSTEMS.md](docs/OLDER_SYSTEMS.md) | Older systems (iOS 18 – 25, macOS 15 – 25): building the older-API version and combining it with the Legacy Device Pack |
- | [docs/qa-rift-pet-life.md](docs/qa-rift-pet-life.md) | Regression checklist for minion life in Greater Rifts (what has been run and what has not; additions welcome) |
- | [docs/DERIVED.md](docs/DERIVED.md) | Game-related material in this repository: what is here, what is not, and why |
- | [docs/ANDROID.md](docs/ANDROID.md) | Playing on an Android phone: installing the APK, making the import pack, new releases, troubleshooting |
- | [docs/HARMONYOS.md](docs/HARMONYOS.md) | Playing on a HarmonyOS phone: re-signing the unsigned shell, making the runtime pack, importing, troubleshooting |
- | [dm/harmony/README.md](dm/harmony/README.md) | HarmonyOS: source layout, build commands, defaults and measurements |
- | [dm/android/README.md](dm/android/README.md) | Android: source layout, building, the files to put on the phone, the acceptance checklist |
- | [dm/gfx/vulkan/INTEGRATION.md](dm/gfx/vulkan/INTEGRATION.md) | How the Vulkan graphics layer plugs into the shared graphics API |
- | [docs/ANDROID_COLLABORATION.md](docs/ANDROID_COLLABORATION.md) | Android / HarmonyOS collaboration: who works where, how to take part, measured status and remaining work; the notes from every round are in [docs/android-notes/](docs/android-notes/) |
- ## Legal
- **You must own the game, including the Reign of the Warlock expansion.** This is an independent, non-commercial project. It is not affiliated with, endorsed by, or sponsored by Blizzard Entertainment or Nintendo. Diablo and Blizzard Entertainment are trademarks of Blizzard Entertainment, Inc.; Nintendo Switch is a trademark of Nintendo. Use it only with a copy of the game that you own.
- ## Acknowledgements
- This project stands on the open-source work below. Thank you to its authors and maintainers.
- - **Ryujinx** (Ryubing 1.3.2, MIT): `dm/third_party/ryujinx` bundles its shader translator unchanged (the Ryujinx.Graphics.Shader, Spv.Generator and Ryujinx.Common projects), which translates the Switch game's shaders to SPIR-V. During development we also ran the original game in a patched Ryujinx as the reference for comparing pictures and game state (see [dm/verify/README.md](dm/verify/README.md); the scripts that build and drive it are not in this repository).
- - **deko3d** (devkitPro, zlib): the texture layout size algorithm in `dm/gfx/nvn/nvn_tex.c` is ported from it.
- - **nvn.h** (h1k421, MIT): the graphics API declarations in `dm/gfx/nvn/include/nvn.h`.
- - **libdeflate** (Eric Biggers, MIT): decompressing game data.
- - **bcdec** (iOrange, MIT or Unlicense): decoding BC textures on devices that do not support the BC formats.
- - **FLIP** (NVIDIA, BSD 3-Clause): the image difference metric used in image-quality checks.
- - **Offline fix patch** (LFS Mod Offline Fix): the 7 rewrites in `dm/tools/patch_nso.py` that let the game run offline come from this community patch. We have no reliable record of where it was first published or who wrote it; if you know, please open an Issue.
- - Tools used to build and verify: SPIRV-Cross (SPIR-V to Metal Shading Language), XcodeGen, .NET, Capstone and Unicorn (disassembly and equivalence checks of the rewrites), Pillow, numpy, lz4, astcenc (the Legacy Device Pack), hactool (extracting files from a game package), libimobiledevice and LLVM. Versions and links are in [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md).
- - Community contributions: Joe Hu reported and diagnosed several Greater Rift issues and proposed a verification matrix; seedds found and diagnosed the render-target view format issue on another port (#36). Both are credited as co-authors on the corresponding commits.
- ## License
- MIT, see [LICENSE](LICENSE). Third-party code keeps its own license in its own directory; see [docs/DEPENDENCIES.md](docs/DEPENDENCIES.md).
- **⭐ Star D2R Mobile to help the next player find it.**
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.