-
Notifications
You must be signed in to change notification settings - Fork 1
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
Request - console access? #1
Comments
As far as I looked, there isn't any easy way to enable console access, hence why I created entire list of pointers from decompiled functions. Not all will work, but most should: Cheat Engine pointer configuration example: Make sure to attach Cheat Engine to JB_LiveEngine_s. |
What Sui said is incorrect. Enabling console access is rather easy granted youre doing it in a DLL, not C#. It's probably really easy in C# too, but I personally don't have much experience and can't comment on that. //In dllmain, place this inside DLL_PROCESS_ATTACH
CreateThread(nullptr, 0, reinterpret_cast<LPTHREAD_START_ROUTINE>(ShowDevConsole), nullptr, 0, 0);
//then place this anywhere above, or in a separate .cpp file
DWORD dllBase = reinterpret_cast<DWORD>(GetModuleHandleA("jb_mp_s.dll"));
void ShowDevConsole()
{
reinterpret_cast<int(__cdecl*)()>(dllBase + 0x2C4230)();
MSG m;
while (GetMessage(&m, nullptr, 0, 0)) {
TranslateMessage(&m);
DispatchMessage(&m);
}
} |
Would you be able to prepare a binary file to use console in multiplayer? Thanks! |
I used the same approach in my project on my page which enables it in MP. |
Hello, I would like to preserve this game by means of porting, however there aren't really any tools out there. I saw in the wiki there are a lot of debugs commands - but frankly I'm not sure how to work with that.
What I would like the most is ability to use ~console, turn on noclip cheat, disable culling as much as possible, and if possible - turn off xmodels rendering, ability to show material name when pointed - all of this is possible in basically every call of duty game.
looking forward to hear from you!
thanks for the tool!
The text was updated successfully, but these errors were encountered: