Fixed the problems stated above by YinYin.
For those of you who are interested the fault was simply the DLL handling the "itrs"-variable as an array of pointers, while it is a pointer to an array, which should be fixed now (same thing goes for bdys).
On top of that the variables have been renamed to fit their actual purpose. (move_counter, run_counter, weapon_holder, weapon_thrower).
Also another bad typing error was fixed, and you are now able to read more scoreboard data. (total hp lost etc.)
Download: http://www.mediafire.com/folder/pxd026nq...2ddWrapper
Edit: @below: Whoopsies.
For those of you who are interested the fault was simply the DLL handling the "itrs"-variable as an array of pointers, while it is a pointer to an array, which should be fixed now (same thing goes for bdys).
On top of that the variables have been renamed to fit their actual purpose. (move_counter, run_counter, weapon_holder, weapon_thrower).
Also another bad typing error was fixed, and you are now able to read more scoreboard data. (total hp lost etc.)
Download: http://www.mediafire.com/folder/pxd026nq...2ddWrapper
Edit: @below: Whoopsies.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.