explaingit

natusanima/witcher-monster-slayer-revival-project

Analysis updated 2026-05-18

0C#Audience · developerComplexity · 5/5Setup · hard

TLDR

A reverse engineering project rebuilding a custom server so a shut-down Witcher mobile game can be played again.

Mindmap

mindmap
  root((Witcher Revival))
    What it does
      Reverse engineers game client
      Builds replacement server
      Redirects app network calls
    Tech stack
      C#
      ASP.NET Core
      Frida
      Python
    Use cases
      Play a discontinued AR game again
      Study a proprietary TCP protocol
      Reverse engineer an IL2CPP client
    Audience
      Reverse engineers
      Game preservation hobbyists
    Status
      Work in progress
      Handoff notes included

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Stand up a custom server that mimics the original game's shut down backend.

USE CASE 2

Use a Frida hook to redirect the original app's network calls to a local server.

USE CASE 3

Study the reverse engineered protocol docs to understand how the client and server talk.

USE CASE 4

Pick up an in progress reverse engineering effort using the included handoff notes.

What is it built with?

C#ASP.NET CoreFridaPython

How does it compare?

natusanima/witcher-monster-slayer-revival-projectanulman/docx-saxatrblizzard/vtmb-sbox-mounter
Stars000
LanguageC#C#C#
Setup difficultyhardmoderatemoderate
Complexity5/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires a physical Android device, ADB tooling, and reverse-engineered client data to get running.

In plain English

This project tries to bring back The Witcher: Monster Slayer, an augmented reality mobile game whose official servers were shut down in June 2023. Since the original backend no longer exists, the only way to make the game playable again is to build a replacement server and get the existing app to talk to it instead of the dead one. The approach has two main parts. The first is client modding: the original Android app is run on a physical phone, and a tool called Frida is injected into it at runtime to intercept the app's low level network connection calls, redirecting them from the shut down production server to a local address, and to work around parts of the app that expect a server response the project cannot yet fully replicate. The second part is the backend itself, a custom server written in C# using ASP.NET Core, which listens on a raw TCP port for game traffic and a separate HTTP port for static data, and implements the same custom, big endian message format that the original game client expects to send and receive. The repository is organized around this split. The server code lives in its own folder, with files handling the TCP session logic and the game's static data. A tools folder holds the Frida hook script, the Python script used to inject it, and the Android platform tools needed for port forwarding and launching the app. Another folder holds heavy reverse engineering output generated by a tool called Il2CppDumper, used to look up internal addresses and undocumented API details from the original app's compiled code. A docs folder contains write ups of the network protocol, memory layout findings, and the sequence of requests the client makes when it starts up. The README frames the project as an ongoing, in progress reverse engineering effort rather than a finished product, and includes a handoff file meant to help a developer resume work partway through. No license is stated in the README.

Copy-paste prompts

Prompt 1
Explain how the Frida hook.js script redirects this game's network calls to a local server.
Prompt 2
Walk me through setting up the ASP.NET Core server to listen on the game's expected TCP port.
Prompt 3
Help me understand the big-endian wire protocol described in docs/protocol-reference.md.
Prompt 4
Summarize where this project's reverse engineering work currently stands using HANDOFF.md.

Frequently asked questions

What is witcher-monster-slayer-revival-project?

A reverse engineering project rebuilding a custom server so a shut-down Witcher mobile game can be played again.

What language is witcher-monster-slayer-revival-project written in?

Mainly C#. The stack also includes C#, ASP.NET Core, Frida.

How hard is witcher-monster-slayer-revival-project to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is witcher-monster-slayer-revival-project for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.