VTable I/O

Author: Scags

README.md

@@ -24,7 +24,7 @@ Name says it all, but this verifies SourceMod gamedata files. This requires Valv
 
 Has a few quirks with it at the moment:
 - It does not support multi-line comments within gamedata files nor will it support multiple instances of `#default` keys. Parsing core SourceMod gamedata files is essentially verboten.
-- Windows or stripped VTable offsets cannot be verified.
+- VTable functions that are stripped cannot be verified, obviously.
 - Function overloads tends to mess up VTable offset checking; e.g. `GiveNamedItem`.
 - Offset checking is variably difficult depending on naming conventions. If the gamedata key name is not named exactly the same as the function name, it will not be found; e.g. `OnTakeDamage` -> `CBaseEntity::OnTakeDamage` and `CTFPlayer::OnTakeDamage` -> `CBaseEntity::OnTakeDamage` but `TakeDamage` != `CBaseEntity::OnTakeDamage`.
 
@@ -41,4 +41,9 @@ Takes a SourceMod signature and jumps you to the function it's for. If it's a ba
 
 ### nameresetter.py ###
 
-Resets the name of every function in IDA's database. Does not include library or external functions.
+Resets the name of every function in IDA's database. Does not include library or external functions.
+
+
+### vtable_io.py ###
+
+Imports and exports virtual tables. Run it through a Linux binary to export to a file, then run it through a Windows binary to import those VTables into the database. This is similar to [Asherkin's VTable Dumper](https://asherkin.github.io/vtable/) but doesn't suffer from the pitfalls of multiple inheritance. Since it doesn't have those liabilities, it's function typing will almost always be perfect. It currently does not work with templated or nested classes. 32-bit only for now.