DIABLO II: RESURRECTED
A CLASSIC, WITH YOU.
Diablo II: Resurrected, on iPhone, iPad and Mac.
A familiar world, a different screen. D2R Mobile is a community compatibility layer for running your own Switch edition on Apple devices.
Checked against upstream documentation on October 16, 2026. Performance claims belong to the developers; HY8BIT has not tested the game.
DOWNLOAD & VERSION
The upstream project distributes source and empty build shells. Choose your route below, then add your own required Switch game files. A downloaded shell is not a ready-to-play game.
| Your route | What to get | What to check |
|---|---|---|
| iOS 26+ · no Xcode | D2RMobile-shell-build-input.zip | Use source from the same release. |
| iOS 18–25 · no Xcode | D2RMobile-shell-ios18-build-input.zip | Older chips may also need the Legacy Device Pack. |
| Mac + Xcode / native Mac | Matching source code and build documentation | Follow the iOS or Mac instructions for your OS. |
The linked D2R Mobile project targets Apple platforms and does not provide an Android APK. Search results also include item trackers, guides and remote-play tools. Check the project identity before treating any of those as this native offline port.
FIND YOUR BUILD
Select the platform, system and hardware. The result summarizes upstream requirements; it is not a device test.
Recommended path
Older operating systems ↗| Hardware | What the documentation says |
|---|---|
| A17 Pro+ / M-series iPad | Main upstream iOS device class; choose the build by OS. |
| A15–A16 · 6 GB+ | Legacy Device Pack required; upstream reports exist for some devices. |
| A14 · 6 GB+ | Hardware minimum, but no device reports in the upstream table. |
| 4 GB devices / A13 and earlier | Currently unsupported. |
| Apple silicon Mac | Native Mac app; human testing of some controls remains incomplete. |
| Apple TV / Intel Mac | Apple TV is a limited developer preview; Intel Mac is unsupported. |
GETTING STARTED
Mac + Xcode → iPhone / iPad
Prepare the game files and run setup, configure your Apple signing details, then build the iOS app. A free Apple ID has a 7-day signing cycle; do not assume public self-signed builds include iCloud save sync.
Read the iOS build instructions ↗Windows / Linux → iPhone / iPad
Combine the matching upstream shell with your own game files, then sign and install the resulting package. The shell alone cannot launch the game. Third-party sideload signing and Linux packaging remain unverified in the documentation checked here.
Read the experimental packaging guide ↗Apple silicon Mac → Mac
Finish the common setup first, then build the Mac app. The first launch selects the resource folder. Local ad-hoc signing needs no developer account. Some input behavior has only automated verification, not hands-on testing.
Read the Mac guide ↗BRING YOUR OWN GAME
The tools expect the Switch release with Reign of the Warlock, updated to 1.0.34.0. The workspace calls the corresponding version 3.3.94012. The PC release is not a substitute for the Switch files.
main · sdk · subsdk0Program files used by the build tools.
build_manifest.psv + .data filesGame resources; first launch on iOS expects 18 resource archives, about 5.6 GB.
Keep the original game files, build output and save backups separate. The full checklist explains workspace layout, version matching and resource transfer.
Game-file checklist ↗Use the full Mac/Xcode build or the documented shell-packaging route. The upstream instructions do not establish a phone-only installation path.
The iOS app needs 18 resource archives, about 5.6 GB, outside the install package. If the import screen lists missing files, complete the copy and retry.
A package made without Apple’s shader compiler compiles shaders on the phone on first launch; upstream reports about 7 minutes. This one-time step is absent from the Xcode build route.
Free Apple ID signing has a 7-day cycle. Back up saves before reinstalling. Public self-signed packages do not include the test builds’ iCloud save-sync entitlement.
Run these from your local checkout after following the upstream prerequisites. These are documentation examples; HY8BIT has not run a game build.
Reports missing tools, game files and signing configuration without modifying the workspace.
./setup.sh checkAfter setup, signing configuration and Python environment activation, run in dm/ios.
DM_IOS_M3=1 ./run.sh buildAfter common setup and Python environment activation, run from the repository root.
DM_MAC_M3=1 dm/tools/mac_app.shFor older iOS chips, check whether the Legacy Device Pack was included when packaging. Creating the pack and rebuilding are separate from choosing an older-OS build.
The shell is build input. Generate the actual install package with matching source and your own game files before installing.
Copy all 18 required resource archives into the app’s resource folder, then retry. The install package does not include them.
Record your exact device, OS, source revision and error. Use Share Diagnostics in the pause menu when available and attach the log to an upstream issue. Back up saves before reinstalling.
No. This project installs on supported Apple devices. HY8BIT provides a guide, not a browser game.
Bring your own game files. Use the upstream file checklist and installation documentation; HY8BIT hosts no game packages.
The upstream project describes offline single-player only.
The linked project targets Apple platforms. This guide does not claim Android support.
Switch 1.0.34.0 corresponds to 3.3.94012 in the project’s workspace naming. The upstream tools require the matching Switch files with the expansion.
No. OS compatibility and memory requirements are separate. The upstream device table currently marks 4 GB devices as unsupported.
No. The shell is input to the packaging tool and contains no game content. Generate the install package first.
The upstream Mac build records locations in the local workspace. It is intended for the Mac that built it; keep the referenced workspace available.
No. This guide covers an independent community compatibility-layer project, not an official Blizzard mobile product.
The documented routes require a preparation computer for building or packaging, plus a signing and installation method. A phone-only route is not established.
No. The upstream release provides build inputs without game content. Current shells are ZIP build inputs; use matching source and your own files to generate the install package.
Keep the source and shell on the same release. Regenerate the package for that release and follow its notes. Keep save backups before reinstalling; do not mix a newer source checkout with an older shell.
Want to understand the experience before building? These sections cover the features, execution model and reported performance.
THE EXPERIENCE
What changes when a console classic moves to a phone? The upstream project focuses on input, inventory and the endgame. These are developer-described features, not HY8BIT playtest results.
Touch & controller
A virtual stick handles movement; skill buttons support holding and drag-to-aim. Connect a controller to switch input layouts.
Inventory & farming
The project adds collection storage and a Runeword helper alongside its touch inventory controls. Availability follows the upstream build.
Beyond the campaign
The authors describe a Greater Rift and Boss Rush as additional endgame modes. These are project additions to its offline experience.
UNDER THE HOOD
The Switch edition supplies ARM64 code. The compatibility layer adapts platform services and graphics for Apple hardware; it does not use a browser runtime.
ExeFS + RomFS
Code rewriting + shaders
Host services + Metal
Local game execution
Read the implementation notes in the upstream README. For the Mac build, the resulting app still depends on files in the workspace that built it.
README ↗UPSTREAM REPORTS
Reported on tested iOS devices
Main menu → game, author measurement
Optional power-saving mode
The README’s timing and power measurements use an iPhone 17 Pro Max. They do not establish performance on every supported device. HY8BIT has not reproduced them.
README ↗Requirements and experimental paths change. Check these maintained documents before following a build guide.