This repository contains the original Pixel Dungeon code, adapted to work with modern Android build tools. The original codebase for the game uses the outdated ADT build system, this codebase uses Gradle but is otherwise functionally identical.

Look below for compilation instructions

Pixel Dungeon

Traditional roguelike game with pixel-art graphics and simple interface.

Pixel Dungeon on Google Play: https://play.google.com/store/apps/details?id=com.watabou.pixeldungeon

Original Pixel Dungeon Source Code: https://GitHub.com/watabou/pixel-dungeon

Official web-site: http://pixeldungeon.watabou.ru/

Developer's blog: http://pixeldungeon.tumblr.com/

Compiling Pixel Dungeon

To compile Pixel Dungeon you will need:

• (required) A computer which meets the system requirements for Android Studio
• (recommended) A GitHub account to fork this repository, if you wish to use version control
• (recommended) An Android phone to test your build of Shattered Pixel Dungeon

1. Installing programs

Download and install the latest version of Android Studio. This is the development environment which android apps use, it includes all the tools needed to get started with building android apps.

It is optional, but strongly recommended, to use version control to manage your copy of the Shattered Pixel Dungeon codebase. Version control is software which helps you manage changes to code. To use version control you will need to download and install Git. You are welcome to use a separate graphical git client or git CLI if you prefer, but this guide will use Android Studio's built-in git tools.

2. Setting up your copy of the code

If you are using version control, fork this repository using the 'fork' button at the top-right of this web page, so that you have your own copy of the code on GitHub.

If you do not wish to use version control, press the green 'code' button on this repository's main page, and then 'Download ZIP'. Unzip the downloaded zip to any directory on your computer you like.

3. Opening the code in Android Studio

Open Android Studio, you will be greeted with a splash page with a few options.

If you are using version control, you must first tell Android Studio where your installation of Git is located:

• Select 'Configure' then 'Settings'
• From the settings window, select 'Version Control' then 'Git'
• If it wasn't auto-detected, Point 'Path to Git executable:' to 'bin/git.exe', which will be located where you installed git.
• Hit the 'test' button to make sure git works, then press 'Okay' to return to the splash page.

After that, you will want to select 'check out project from version control' then 'git'. Log in to GitHub through the button (use username instead of tokens), and select your forked repository from the list of URLs. Import to whatever directory on your computer you like. Accept the default options android studio suggests when opening the project. If you would like more information about working with Git and committing changes you make back to version control, consult this guide (skip to chapter 4).

If you are not using version control, select 'Import project (Gradle, Eclipse ADT, etc.)' and select the folder you unzipped the code into. Accept the default options android studio suggests when opening the project.

4. Running the code

Once the code is open in Android Studio, running it will require either a physical android device or an android emulator. Using a physical device is recommended as the Android Emulator is less convenient to work with and has additional system requirements. Note that when you first open and run the code Android Studio may take some time, as it needs to set up the project and download various android build tools.

The Android Studio website has a guide which covers the specifics of running a project you have already set up.

This guide includes a section on physical android devices...

... and a section on emulated android devices.

5. Generating an installable APK

APK (Android PacKage) and AAB (Android App Bundle) files are used to distribute Android applications. The Android studio website has a guide which covers building your app. Note that the option you will likely want to use is 'Generate Signed Bundle / APK'. APK files are best used when you are not trying to upload your app to Google Play, otherwise you must provide Google with an AAB file and they will used that to generate APK files for you.

Note that APK and AAB files must be signed with a signing key. If you are making a small personal modification to Pixel Dungeon then your signing key is not important, but if you intend to distribute your modification to other people and want them to be able to receive updates, then your signing key is critical. Google will also sign your app for you on Google Play, but you can provide them with the same key that you use to sign your own APKs. The Android studio website has a guide on signing keys that covers both personal and Google Play distribution.

6. Distributing Your APK

The Android Studio website includes a guide for ways to distribute your app.

Note that by distributing your modification of Shattered Pixel Dungeon, you are bound by the terms of the GPLv3 license, which requires that you make any modifications you have made open-source. If you followed this guide and are using version control, that is already set up for you as your forked repository is publicly hosted on GitHub. Just make sure to push any changes you make back to that repository.

If you intend to make your version of the game available on Google Play PLEASE CONTACT ME AT THE FOLLOWING EMAIL ADDRESS: [email protected] . There are various aspects of Google's Developer Policies that go beyond the scope of a simple 'how to compile' guide. If you do not take necessary precautions before attempting to publish on Google Play, your version of the game will almost certainly be taken down for impersonating Pixel Dungeon.