-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aobscanmodule #3
Comments
Hey! Thank you for the compliments. What exactly do you mean with adding driver/dll view support? DLL view support should already be added because i iterate the modules, and when looking through memory it should display which region is from which module. |
I agree with the OP. This tool has been great help performing scans and changing values manually (for which I am very grateful for) but I sadly cannot use precompiled scripts as they rely on aobscanmodule. Attempting to use auto assemble with the following script throws an error calling the DLL. [ENABLE] aobscanmodule(Stamina,game.dll,F3 41 0F 11 08 8B 48 10 E8 C1 F7 38 00 41 8B 47 48) label(code) newmem: code: Stamina: [DISABLE] Stamina: unregistersymbol(Stamina) |
aobscanmodule is Cheatengines Lua API, which i don't support as you might know. and I won't be spending time, for the time being on adding support for it, but feel free to provide me with information on what i have to replicate to add support for it. |
If I'm not mistaken, I believe it would be "Enumerate DLL's and Symbols" from Memory View/View/Enumerate DLL's and Symbols. Thank you for the reply. |
I believe that to support CheatEngine Lua api, i'd have to inject a .dll. (quote me if i'm wrong) to make a injection through DMA w/o picking up any detections for anticheats it will be kinda hard to do. especially when executing the payload. there isn't any good way of doing it without the user manually doing work on what function to use to execute the payload. support for it can be added, just that it wouldn't be a "one for all" solution |
Very nice project, thanks to @Metick But I also found the problem as @Inquiry7 mentioned, the "Enumerate DLL's and Symbols" from Memory View/View is empty. Thanks. |
@Metick Could you double-check that the memory window does display which region is from which module? As you can see from the screenshot above, the memory window does not show module names. May I ask what version of Cheat Engine are you using? |
Thanks for being interested in contributing to my project! I should've already implemented Enumerate Dlls and symbols, Personally I never use a 2pc setup, so might be a issue when you use 2 computers on how i enumerate the process of the target computer? Or maybe not fully implemented, but it works on 1pc setup as far i'm aware. for your question which CE version i'm using, I'm using a custom compiled version of CE. which should be more or less based on CE 7.5 version |
Fixed the issue mentioned in #3 which as Lauralex pointed out is fixed on the main source already, but isn't fixed on stable version yet. so we just write the binary name to path to solve the issue (:
How would I be able to implement the LUA API myself? To obtain the aobscanmodule and be able to use "What address writes to" and "What accesses this address" |
Just a side Question, your Target Pc is the same as The "attack" pc? |
Yea, if you do 1pc setup you just plug the USB back into your own computer. making it the target and attack pc |
Nice, i tried that but get always vmm error. But maybe i connected something wrong😅 i have to trie again |
Make sure you've downloaded the FTD3xx driver, or if you use ZDMA that you have their driver installed on the same computer. |
Any way to be able to use the "What access to this address" and "What writes to this address" options? An amazing job, at your feet genius! |
Hello! First off, love what you've done and has this been extremely helpful.
I am aware you said you would only add support for things you need. However, if you have time when you stop by to update this project again, could you consider adding driver/dll view support? I am attempting to scan/write to a dll that interacts with an exe on the target computer, but am unable to due to the dll not being pulled/recognized.
Thank you!
The text was updated successfully, but these errors were encountered: