I've been waiting for a proper time to post this for a while, but i just get the opportunity now... So, i'm sorry for this late post...
It's about unique searching feature that belongs only to MHS, which in turns would greatly increase the searching process... However, i think there are some bugs about group search, which i'm gonna tell you...
And since Group Search is unique, we certainly hope that it works perfectly ... ^^
...
I've comparing the MHS PRO 3.0.1.4 with (at present) the newest MHS Demo #17, and the target game is Warcraft 3 The Frozen Throne...
The following case is about Hero's movement speed...
In MHS PRO 3.0.1.4, the group search managed to found the address:
but, in MHS Demo #17 nothing was found:
Both above pictures were taken at the same time, while targeting the same process... It's like the Demo version's Group Search not as 'powerfull' as the Pro version... (?)
...
The next following case is about Hero's Stat Constants...
Every heroes within WC3 TFT v1.20, always have 3 stats constants (STR,INT,AGI) which are added to the current stat everytime the heroes gain a level up...
For example:
If Hero's Stat Constants values are:
- STR : 1.85
- INT : 2.35
- AGI : 1.95
and at Level 01 the stats are:
- STR : 16
- INT : 20
- AGI : 18
then, if the hero gains a level up, the stat would be:
- STR : 16 + 1.85 = 17
- INT : 20 + 2.35 = 22
- AGI : 18 + 1.95 = 19
(the decimal number are hidden (not shown on-screen) but still counts...)
after a small research, i found that those 3 Stat Constants are stored within the memory this way: XXXX nnnn YYYY nnnn ZZZZ
XXXX = STR Const
YYYY = INT Const
ZZZZ = AGI Const
So, using MHS Pro 3.0.1.4 group search, i tried to found the address:
as you can see, there are 3 'undescribed' addresses, which actually the addresses for 3 stat constants values, which i put before the search manually... But, the group search was unable to find anything...
But the weird thing occured right after i wrote description for the 3 addresses:
Suddenly, MHS PRO 3.0.1.4's Group Search found the address 'I was looking for'...
The two previous screen captures (which were taken right one after another) show the very same addresses, but with different result of Group Search...
As for the Demo #17, it was unable to find anything at all (regard this 3 stat constants)...
Was it my mistake or was it a real bug ?
These problems, AFAIK, occured only when we're working with float numbers... Are they have anything to do with float number's precisions ?
For example:
Maybe MHS Pro thinks these number are the same:
- 18.345678
- 18.345777
- 18.35
while MHS Demo thinks they're different ?
....
I hope my post clear enough to understand for my english is not very good... And I mean nothing offense at all...
Thank you very much, and keep up good work !