Textractor
English ● Español ● 简体中文 ● 日本語 ● Русский ● Bahasa ● Português ● ภาษาไทย ● 한국어
Textractor (a.k.a. NextHooker) is an open-source x86/x64 video game text hooker for Windows/Wine based off of ITHVNR.
Watch the tutorial video for a quick rundown on using it.
Download
Releases of Textractor can be found here.
The last release of ITHVNR can be found here.
Try running vcredist if you get an error when starting Textractor.
Features
- Highly extensible and customizable
- Auto hook many game engines (including some not supported by VNR!)
- Hook text using /H "hook" codes (most AGTH codes supported)
- Directly extract text using /R "read" codes
Support
Please let me know of any bugs, games that Textractor has trouble hooking, feature requests, or other suggestions.
If you have trouble hooking a game please email me a place where I can freely download it, or gift it to me on Steam.
Extensions
See my Example Extension project to see how to build an extension.
See the extensions folder for examples of what extensions can do.
Contributing
All contributions are appreciated! Please email (no, I'm not busy!) me at akashmozumdar@gmail.com if you have any questions about the codebase.
You should use the standard process of making a pull request (fork, branch, commit changes, make PR from your branch to my master).
Contributing a translation is easy: just translate the strings in text.cpp as well as this README.
Compiling
Before compiling Textractor, you should get Visual Studio with CMake support, as well as Qt version 5.11
You should then be able to simply open the folder in Visual Studio, and build. Run Textractor.exe.
Project Architecture
The host (see GUI/host folder) injects texthook.dll (created from the texthook folder) into the target process and connects to it via 2 pipe files.
Host writes to hostPipe, texthook writes to hookPipe.
texthook waits for the pipe to be connected, then injects a few instructions into any text outputting functions (e.g. TextOut, GetGlyphOutline) that cause their input to be sent through the pipe.
Additional information about hooks is exchanged via shared memory.
The text that the host receives through the pipe is then processed a little before being dispatched back to the GUI.
Finally, the GUI dispatches the text to extensions before displaying it.