DISCONTINUED ❌

This project was released to the public in a half-working state after we decided to completely shut down its development.

[wontfix] Aside from a few basic ones, most features do not work due to issues related to Unity Engine version being changed, as well as field shuffling in RPC types.

Additionally, don’t be surprised if you come across confusing, debug, or outright broken code here - we didn’t exactly bother cleaning up the repo before making it public ;)

Cheers,
~ xor&pray

Yangware

Yangware is a multi-platform ZombsRoyale.io modification with two main tracks:

• A Windows DLL module and loader built with CMake and MSVC (Visual Studio 2022)
• An Android port built with Gradle, the Android SDK, and the Android NDK

This repository is organized as a workspace rather than a single binary target. The root project ties together the Windows components, while the android/ directory contains its own standalone Android app and build scripts.

Overview

Windows

The root CMakeLists.txt builds two targets:

• yangware_module: the injected native module (crossplatform)
• yangware_loader: the Windows-only loader/injector executable

The shared feature logic lives in the module source tree and is grouped into:

• Features/
• Graphics/
• Network/
• Utility/
• Yangware/

The Android JNI loader lives inside the android/ directory, in Loader.cpp.

Android

The android/ directory contains the Android port, including:

• Gradle project files
• JNI/CMake native build integration
• packaging and patching scripts
• install/build helpers for Windows and shell environments

Repository Layout

.
|-- CMakeLists.txt              # Root Windows workspace.
|-- cmake/
|   `-- YangwareCore.cmake      # Shared source lists for platform builds.
|-- yangware/
|   |-- yangware_module/        # Windows native module.
|   `-- yangware_loader/        # Windows loader/injector.
`-- android/                    # Android port and build scripts.

Requirements

Windows development

• Windows
• CMake 3.22+
• Visual Studio with MSVC C++ toolchain

The Windows targets currently use:

• cxx_std_23
• Direct3D 11 for the module UI/render hook

Android development

• Java JDK 17
• Android SDK
• Android NDK
• Apktool
• 7-Zip
• Python

The Android app is configured for:

• compileSdk 34
• targetSdk 34
• minSdk 24
• NDK 27.3.13750724
• arm64-v8a builds by default

Building

Windows Build

From the repository root:

cmake -S . -B build -G "Visual Studio 17 2022" -A x64
cmake --build build --config Release

Notes:

• The root CMake workspace is Windows-only.
• On non-Windows platforms, the root project intentionally skips the Windows targets.
• The Windows build pulls in yangware/yangware_module and yangware/yangware_loader automatically.

Android Build

The Android port has its own workflow inside android/.

Typical Windows flow:

cd android
.\scripts\make-keystore.bat
.\scripts\decompile-and-set-up.bat
.\scripts\build.bat
.\scripts\install.bat

The Android pipeline expects a prepared merged input APK named in.apk. More detail is available in android/README.md.

Code Organization

Shared source lists

cmake/YangwareCore.cmake defines the shared native source lists used across platform-specific builds. That file is the best entry point if you want to understand which feature files are considered core, Windows-only, or Android-only.

Windows module

yangware/yangware_module contains the native module code, external dependencies, hooks, UI code, networking helpers, and feature implementations.

Windows loader

yangware/yangware_loader contains the Windows-specific loader application and injection code.

Android app

android/app contains the Android application wrapper and the native Android build integration.

Getting Started

If you are new to the repo, a good way to explore it is:

1. Start with CMakeLists.txt to see how the workspace is wired together.
2. Open cmake/YangwareCore.cmake to see the core native source layout.
3. Browse yangware/yangware_module/src to inspect features and subsystems.
4. Use android/README.md for the Android-specific setup flow.

Notes

• Platform-specific details, especially around APK preparation and packaging, live in the Android subproject docs and scripts.