测试合并
Go to file
2018-11-04 17:12:25 -05:00
cmake build system improvements 2018-10-19 15:55:48 -04:00
extensions add thread linker extension 2018-11-04 16:37:23 -05:00
GUI refactor error handling 2018-11-04 17:12:25 -05:00
include extract more strings 2018-11-04 04:00:14 -05:00
vnrhook add default codepage option 2018-11-01 21:59:13 -04:00
.gitattributes Line ending attributes for window LF 2016-12-12 00:50:06 +09:00
.gitignore ignore qt creator 2018-10-20 14:52:34 -04:00
CMakeLists.txt build system improvements 2018-10-19 15:55:48 -04:00
CMakeSettings.json build system improvements 2018-10-19 15:55:48 -04:00
deploy.ps1 add regex filter 2018-11-03 23:58:52 -04:00
LICENSE add license and update readme 2018-05-20 21:21:37 -04:00
README_JP.md update readmes 2018-10-21 16:31:19 -04:00
README.md update readme for new project architecture 2018-11-04 01:41:39 -04:00

Textractor

日本語

Overview

Textractor (a.k.a. NextHooker) is an open-source x86/x64 text hooker for Windows/Wine based off of ITHVNR.

How it looks

Downloads

Releases of Textractor can be found here.

Previous releases of ITHVNR can be found here.

Features

  • Highly extensible
  • Auto hook many game engines (including some not supported by VNR!)
  • Hook text using /H "hook" codes (most AGTH codes supported)
  • Extract text using /R "read" codes (Guide)

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).

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 vnrhook.dll (created from the vnrhook folder) into the target process and connects to it via 2 pipe files.
Host writes to hostPipe, vnrhook writes to hookPipe.
vnrhook 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 shared through a file view (a.k.a. section object) that is mapped to a reference to the TextHook class.
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.

Developers

Special Thanks

  • Everybody adding issues!