Well it seems that aoe dc's after a certain amount of hits in EP9
and it DC's faster the higher the aoe value gets. so like at 14 it would dc in about 8 moves, at 1000 it dc's in 2 moves.
i also noticed that the aoe pattern is different from before and seems as though aoe misses more often regardless of the reach value
before with aoe i think what happend was an aoe hit was considered 1 hit but now in ep9 aoe is considered multiple moves at once. if that is the case this puts into play alot more varaibles.
my theory is that maybe it dc's because the number of misses
or because theyre considered as individual hits the trigger for no cool down dc's because of too many hits too fast.
i dunno those are my theories. any input??
btw im CABAL NA\
GM = cabalmain.exe+A82198
REACH = cabalmain.exe+AC5498
RANGE = cabalmain.exe+AC549C
another note. alot of the code regarding "attacking" has changed alot
for example. there are no more little functions in the memory for no cool down
before it used to be something like this
mov eax, [esi + 4]
mov ebp, [eax + 0x20]
...
now it 1 HUGE function which actually took me a whole day to bloody find.
same with attack through walls
but anyway i was walking around and i actually found a bot that managed to do AOE for ALL skills as described in this topic "http://www.elitepvpers.com/forum/cabal-main-discussions-questions/2042274-aoe-non-supported-skills.html" without dcing once
i went and tried to update those addresses but like i said above almost every piece of important code regarding "attack" has changed
at first i tried searching for the asm for memory editing (i can do that btw no problem) but couldnt find anything related to that.
so then i tried searching for the base address to change the range_type via dynamic memory
and finnally after 6 hours of reversing i figured out that they outphased that array or moved it somewhere else
the new base for range_type for cabal na should have been
0x00EC46F4 but that dword is always NULL durring gameplay so its obviously wrong lol
so if someone could give me some insight or help i would really appreciate it. thanks in advanced :handsdown:
yup just confirmed this right now (soz for double post)
on cabal na latest update AoE (GM Range) now dc's after a few hits
and it DC's faster the higher the aoe value gets. so like at 14 it would dc in about 8 moves, at 1000 it dc's in 2 moves.
i also noticed that the aoe pattern is different from before and seems as though aoe misses more often regardless of the reach value
before with aoe i think what happend was an aoe hit was considered 1 hit but now in ep9 aoe is considered multiple moves at once. if that is the case this puts into play alot more varaibles.
my theory is that maybe it dc's because the number of misses
or because theyre considered as individual hits the trigger for no cool down dc's because of too many hits too fast.
i dunno those are my theories. any input??
btw im CABAL NA\
GM = cabalmain.exe+A82198
REACH = cabalmain.exe+AC5498
RANGE = cabalmain.exe+AC549C
another note. alot of the code regarding "attacking" has changed alot
for example. there are no more little functions in the memory for no cool down
before it used to be something like this
mov eax, [esi + 4]
mov ebp, [eax + 0x20]
...
now it 1 HUGE function which actually took me a whole day to bloody find.
same with attack through walls
but anyway i was walking around and i actually found a bot that managed to do AOE for ALL skills as described in this topic "http://www.elitepvpers.com/forum/cabal-main-discussions-questions/2042274-aoe-non-supported-skills.html" without dcing once
i went and tried to update those addresses but like i said above almost every piece of important code regarding "attack" has changed
at first i tried searching for the asm for memory editing (i can do that btw no problem) but couldnt find anything related to that.
so then i tried searching for the base address to change the range_type via dynamic memory
and finnally after 6 hours of reversing i figured out that they outphased that array or moved it somewhere else
the new base for range_type for cabal na should have been
0x00EC46F4 but that dword is always NULL durring gameplay so its obviously wrong lol
so if someone could give me some insight or help i would really appreciate it. thanks in advanced :handsdown:
yup just confirmed this right now (soz for double post)
on cabal na latest update AoE (GM Range) now dc's after a few hits
