Join us on Discord!
Development Live stream
Support us on Patreon

We are also working on a toolset:
Please consider helping out with this project as well!

About this project

OpenDiablo2 is an ARPG game engine in the same vein of the 2000’s games, and supports playing Diablo 2. The engine is written in golang and is cross platform. However, please note that this project does not ship with the assets or content required to play Diablo 2. You must have a legally purchased copy of Diablo 2 and its expansion Lord of Destruction installed on your computer in order to run that game on this engine. If you have an original copy of the disks, those files should work fine as well.

We are currently working on features necessary to play Diablo 2 in its entirety. After this is completed, we will work on expanding the project to include tools and plugin support for modding, as well as writing completely new games with the engine.

Please note that this game is neither developed by, nor endorsed by Blizzard or its parent company Activision.

Diablo 2 and its content is ©2000 Blizzard Entertainment, Inc. All rights reserved. Diablo and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.



At the moment (march 2021) the game starts, you can select any character and run around Act1 town. You can also open any of the game’s panels.

Much work has been made in the background, but a lot of work still has to be done for the game to be playable.

Feel free to contribute!


To pull the project down, run go get

On windows this folder will most likely be in %USERPROFILE%\go\src\\OpenDiablo2\OpenDiablo2

In the root folder, run go get -d to pull down all dependencies.

To run the project, run go run . from the root folder.

You can also open the root folder in VSCode. Make sure you have the ms-vscode.go plugin installed.


There are several dependencies which need to be installed additionally. To install them you can use ./ in the project root folder – this script takes care of the installation for you.


If you find something you’d like to fix that’s obviously broken, create a branch, commit your code, and submit a pull request. If it’s a new or missing feature you’d like to see, add an issue, and be descriptive!

If you’d like to help out and are not quite sure how, you can look through any open issues and tasks, or ask for tasks on our discord server.

As of Oct. 26, 2020 we will no longer be accepting pull requests that introduce lint errors.

We use golangci-lint to catch lint errors, and we require all contributors to install and use it. Installation instructions can be found here.

VS Code Extensions

The following extensions are recommended for working with this project:

  • ms-vscode.go
  • defaltd.go-coverage-viewer

When you open the workspace for the first time, Visual Studio Code will automatically suggest these extensions for installation.

Alternatively you can get to it by going to settings Ctrl+,, expanding Extensions and selecting Go configuration, then clicking on Edit in settings.json. Just paste that section where appropriate.


The engine is configured via the config.json file. By default, the configuration assumes that you have installed Diablo 2 and the expansion via the official Blizzard Diablo 2 installers using the default file paths. If you are not on Windows, or have installed the game in a different location, the base path may have to be adjusted.


There are many profiler options to debug performance issues. These can be enabled by suppling the following command-line option and are saved in the pprof directory:

go run . --profile=cpu

Available profilers:
cpu mem block goroutine trace thread mutex

You can export the profiler output with the following command:
go tool pprof --pdf ./OpenDiablo2 pprof/profiler.pprof > file.pdf

Ingame you can create a heap dump by pressing ~ and typing dumpheap. A heap.pprof is written to the pprof directory.

You may need to install Graphviz in order to convert the profiler output.



Layouts can show their boundaries and other visual debugging information when they render. Set layoutDebug to true in d2core/d2gui/layout.go to enable this behavior.

Example layout in debug mode


There is an in-progress project roadmap, which will be updated over time with new requirements.


Main Menu

Select Hero

Select Hero


Inventory Window

Game Panels

Additional Credits