测试合并
Go to file
Akash Mozumdar 9dfebf7eac minor fixes
2018-07-20 17:36:58 -04:00
gui remove extension code from host 2018-07-20 17:21:35 -04:00
vnr minor fixes 2018-07-20 17:36:58 -04:00
.gitattributes Line ending attributes for window LF 2016-12-12 00:50:06 +09:00
.gitignore update config stuff 2018-06-18 01:16:34 -04:00
CMakeLists.txt bugfix 2018-07-19 21:44:03 -04:00
CMakeSettings.json update config stuff 2018-06-18 01:16:34 -04:00
LICENSE add license and update readme 2018-05-20 21:21:37 -04:00
README.md update readme 2018-07-19 01:16:21 -04:00

NextHooker

Overview

NextHooker is an open-source x86~~ 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}_{NAME}_nexthooker_extension.dll and copy into the NextHooker 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 (most AGTH hook codes supported)
  • Auto hook many engines (including some not supported by VNR!)
  • Extensions (New!)

License

GPL v3

Developers

  • Copyright (C) 2010-2012 kaosu
  • VNR engine making by jichi
  • ITH updating by Andys
  • ITHVNR new GUI & VNR engine migration by Stomp
  • ITHVNR updating by mireado and Eguni

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.