测试合并
Go to file
2018-06-10 04:53:14 -04:00
gui remove unused code from textthread and related files 2018-06-10 04:53:14 -04:00
i18n/gui_korean Revert "remove korean gui (for now) since its hard to maintain" 2018-05-24 05:36:05 -04:00
vnr remove unused code from textthread and related files 2018-06-10 04:53:14 -04:00
.gitattributes Line ending attributes for window LF 2016-12-12 00:50:06 +09:00
.gitignore add VS folder to gitignore 2018-04-22 03:06:19 -04:00
CMakeLists.txt update to 3.5640.1 2016-01-06 00:01:17 +09:00
LICENSE add license and update readme 2018-05-20 21:21:37 -04:00
README.md Update README.md 2018-06-01 09:56:40 -04:00

NextHooker

Overview

NextHooker is an open-source x32~~/x64~~ text hooker for Windows.

Basically, GUI text hooker based on Stomp's ITHVNR.

Extensions

See my Example Extension project to see how to build an extension.

To use an extension, simply rename the extension dll file to {NUMBER}_nexthooker_extension.dll and copy into the NextVNR folder.

Extensions are called in order by the number they are prefixed with.

Downloads

Releases of NextHooker can be found here

Previous releases of ITHVNR can be found here.

Features

  • Open-source
  • Hook text (AGTH hook codes supported)
  • Extensions (New!)

License

GPL v3

Developers

Special Thanks

  • Everybody adding issues!

Compiling

Before compiling NextHooker, You should get CMake, Windows Driver Kit 7.1, and Visual Studio.

Project Architecture

The GUI links to vnrhost.dll (created from the texthook folder) which injects vnrhook.dll (created from the vnrhook folder) into the target process and connects to it via 2 pipe files.
vnrhost writes to hostPipe, vnrhook writes to hookPipe (duh?)
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 Hook class.
The text that vnrhost receives through the pipe is then processed a little before being dispatched back to the GUI and displayed.