Network-only game client Emulator for Mir4 Global version, written in C# by AlSch092 @ Github.
This project was started in 2022 and retired in 2024; No further updates will be made to this repo.
- Auto-collecting (mining, herbs, chest spawns, etc)
- Basic auto-kill monsters
- Map teleport
- Players and chat detection
- Ban evasion from "hidden objects"
- Vulnerability discovery testing tools (full network protocol & opcode list, Protobuf serializer)
This project uses login/session tokens to log in, since the game normally uses a web login/HTTP request chain (web login fetches the session token for ingame login). You will need to manually verify accounts (ingame captcha solve) and collect a working login token for your account, along with the deviceId for that account. You can also try adding a captcha-solving solution to automate this process. Each account has a static deviceId along with a login token which changes every 24h (or 72h if your character is above level 70). This can be collected by using an HTTPS analyzer such as Fiddler and viewing the /auth/loginCheck POST request. Once you've collected your login token & deviceId, a "profile" can be filled out following the template in the Profiles folder, and you can then launch the executable program at the command line in the following format:
Mir4ClientEmulator.exe <profile.ini path>
Alternatively, you can manually fill out the fields in the main form and click the "Connect" button.
- Copy the
Datafolder into the same folder as the compiled executable. The program will throw exceptions if this is not completed. I suggest a folder namedProfilesis also present, which is where account profiles will reside.
This project can support hundreds (if not thousands) of instances at once on a single machine, and is suitable for load & security testing.
- This program handles all network actions but does not encrypt/decrypt GameServer data: you will need to update & use my other project,
Mir4Encryption(C++ DLL) to successfully encrypt & decrypt data. Place the encryption .dll into same folder as this project's executable. You will need to update the AES-128-CBC key yourself at new client patch updates, as it rotates randomly.