Pointer path to attackspeed

I am using my own memory scanner / pointer scanner for BDO, since cheat engine is detected. Finding stuff is pretty easy, however I am simply not finding a valid pointer path to some values - for example attack speed (or at least not a path that keeps working over several restarts - my scanner has funcitonality to combine multiple pointer maps, to filter invalid stuff - but after several restarts, it's just empty). I am not sure if my scanner is bugged or BDO does some wierd stuff that causes it to not find anything. Can't start cheat engine either to confirm my theory.

For that reason I came to ask if someone was kind enough to give me a valid pointer path (module+0xbla 0xbla 0xbla ...) for the attackspeed value for the current patch of BDO EU. If you think I'm just some kid trying a fancy leech, I can provide you screen shots or some other evidence that my scanner really exists / my Problem is real.
Thanks! :handsdown:

Edit: Seems there is a emergency maintenance just now - I'd need one that works after this one , didn't save my pointermaps :S

0x14341FE08 + 0xBFC

localplayer + atk speed


its probably detected

Quote:

Originally Posted by ruikangzhu1990 0x14341FE08 + 0xBFC localplayer + atk speed its probably detected

Hm, just tried, is this old? does not work for me :/

Edit: Probably 14341FE28 now, it's right next to it ...
Edit: I was able to find the bug, thank you very much <3

Quote:

Originally Posted by Jierda Hm, just tried, is this old? does not work for me :/ Edit: Probably 14341FE28 now, it's right next to it ... Edit: I was able to find the bug, thank you very much <3

what bug :O

Quote:

Originally Posted by ruikangzhu1990 what bug :O

Well, I can't really explain since it's deep into my code, but essentially in the part where my memory scanner combines pointermaps, I calculate a difference between two values, and just assigned it to a new variable with auto. However that made it unsigned, even though I assumed it was signed, which caused the difference to be >= 0 which in turn caused some weird edge cases that were only relevant with some pointers.

But since you gave me a concrete pointer, I was able to debug effeciently, so thanks again ;)