# How to Port Classic Games to Android Using AI: OpenGMK and Code Automation Guide

> AI Release · @ai_release1 · https://ai-release.org/guides/kak-portirovat-klassicheskie-igry-na-android-s-pomoschy_en.html

This guide solves a specific problem: you have a classic GameMaker-era game and want to run it on an Android phone without rewriting it from scratch. The approach shown here is based on a real case — the unofficial Android port of Pokemon Reloaded, published in the GitHub repository `Klisee/pokemon-reloaded-android`. The port runs on OpenGMK, an open-source engine compatible with games made in GameMaker (a popular 2D game engine whose projects ship as `.gmk`/`.exe` files). The guide applies to Android devices and to any GameMaker-compatible game for which a similar port approach is used. All project code and sources are publicly available for study and building.

## Requirements and preparation
![Illustration: Requirements and preparation](https://ai-release.org/guides/img/kak-portirovat-klassicheskie-igry-na-android-s-pomoschy-en-1.jpg)

- A computer with Git installed (to clone the repository).
- An Android device or emulator for testing the build.
- A GitHub account (optional, but useful for forking and tracking issues).
- The source repository: `Klisee/pokemon-reloaded-android` on GitHub.
- Basic familiarity with building projects from source; if you use AI assistants for code work, see [AI for programmers: coding assistants in 2026](https://ai-release.org/guides/ii-dlya-koda.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide).
- Patience: this is an unofficial port, so expect rough edges.

Checklist before you start:

- [ ] Repository cloned locally
- [ ] Android build environment working
- [ ] Test device or emulator available
- [ ] Original game assets understood (what OpenGMK needs to run the game)

## Step-by-step instructions
![Illustration: Step-by-step instructions](https://ai-release.org/guides/img/kak-portirovat-klassicheskie-igry-na-android-s-pomoschy-en-2.jpg)

1. **Study the project page.** Open the repository `Klisee/pokemon-reloaded-android` on GitHub. The project description reads «Port no oficial de Pokemon Reloaded a Android, sobre OpenGMK» — an unofficial port of Pokemon Reloaded to Android, built on OpenGMK. Expected result: you understand that this is a community port, not an official release, and that OpenGMK is the runtime engine. This matters because unofficial ports may lack polish, and knowing the engine helps you search for solutions.

2. **Clone the sources.** Download the code to your machine so you can inspect and build it. The authors explicitly made code and sources available for study and building.

   **Пример:**

   ```bash
   git clone https://github.com/Klisee/pokemon-reloaded-android.git
   cd pokemon-reloaded-android
   ls
   ```

   Expected result: a local folder with the project files, and `ls` shows the repository contents (build files, sources, README). This works because Git copies the full history and files, giving you everything needed for a local build.

3. **Understand the architecture.** OpenGMK is an open-source engine compatible with GameMaker games: it re-implements the GameMaker runtime so old games can run on new platforms, including Android. Read the README and source layout to see how the game logic and assets are wired into the Android build. Expected result: you can name which parts are engine (OpenGMK) and which are game-specific (Pokemon Reloaded assets and scripts). Why this works: separating engine from content tells you exactly what to touch if something breaks.

4. **Build the Android package.** Follow the build instructions in the repository to produce an installable Android package from the sources. Since the port is published as a source project, building from code is the intended path.

   **Пример:** after building, you should get an installable Android package file in the build output directory — for example, a file like `app-debug.apk` in a typical Android project's `build/outputs/apk/` folder (check the repo's README for the exact path and command). Expected result: an APK file exists on disk. This works because the Android build toolchain compiles the OpenGMK runtime plus the game content into a single installable package.

5. **Install and test on a device.** Enable installation from unknown sources on your Android device, transfer the built package, and install it. Expected result: the game launches and the title screen of Pokemon Reloaded appears. Why this works: the APK contains the OpenGMK runtime, which interprets the GameMaker-compatible game data at runtime.

6. **Adapt the approach to other games.** If you want to port a different classic GameMaker game, use this repository as a template: fork it, replace the game content with your target game's data, and rebuild. For automating repetitive code changes during such a port, AI agents can help — see [AI agents for task automation: a guide](https://ai-release.org/guides/ii-agenty-dlya-avtomatizacii.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide). Expected result: a working build of your target game on Android. This works because the engine layer (OpenGMK) stays the same; only the game content changes.

## Possible problems and solutions
![Illustration: Possible problems and solutions](https://ai-release.org/guides/img/kak-portirovat-klassicheskie-igry-na-android-s-pomoschy-en-3.jpg)

- **The build fails with unclear errors.** Symptom: the build command stops with an error message before producing an APK. Solution: 1) re-read the README — unofficial projects often require a specific toolchain version; 2) check the repository's issue tracker on GitHub for the same error; 3) if the error is in code you don't understand, paste it into an AI coding assistant for explanation (see the coding assistants guide linked above).

- **The game installs but crashes on launch.** Symptom: the app closes immediately or shows a black screen. Solution: 1) verify that all required game assets are present in the build — OpenGMK needs the GameMaker-compatible game data to run; 2) check the repository issues for known device-specific problems; 3) test on an emulator to rule out a device-specific issue.

- **You can't find the built APK.** Symptom: the build succeeded, but you don't know where the output file is. Solution: 1) look in the standard Android output folder (for typical projects: `build/outputs/apk/`); 2) search the project folder for files with the `.apk` extension; 3) consult the README, which should state the expected output location.

## FAQ

**Is the Pokemon Reloaded Android port official?**
No. It is an unofficial port, as stated in the project description («Port no oficial de Pokemon Reloaded a Android, sobre OpenGMK»), published by a community author on GitHub.

**What is OpenGMK?**
OpenGMK is an open-source engine compatible with games made in GameMaker. It allows classic GameMaker games to run on platforms like Android without a full rewrite.

**Where can I get the code?**
The code and sources are available in the GitHub repository `Klisee/pokemon-reloaded-android`, published for study and building.

**Can I use this method for other classic games?**
The approach — running a GameMaker-compatible game on OpenGMK and building for Android — is demonstrated by this port; adapting it to another GameMaker game means replacing the game content and rebuilding, using the repository as a reference.