View previous topic :: View next topic |
Author |
Message |
spyware293 Newbie cheater Reputation: 0
Joined: 28 Jun 2012 Posts: 13
|
Posted: Sat Nov 12, 2016 9:34 am Post subject: Trace back to find cause of termination |
|
|
Im trying to make dual client. I've patched a mutex thread which allow multiple windows opened. The problem is when i tried to login, only first opened client can login. Other clients are just closed when i tried to login.
I don't have any string for a reference to look inside debugger. Where should i start looking? The closest thing i can reach is putting breakpoint on thread termination. I don't know how to trace back or step back with debugger.
|
|
Back to top |
|
|
ulysse31 Master Cheater Reputation: 2
Joined: 19 Mar 2015 Posts: 324 Location: Paris
|
Posted: Sun Nov 13, 2016 5:54 am Post subject: |
|
|
Launcher gives the client the login ticket, sometimes through a middle man process, sometimes not. You'll need to login before you close the launcher, then reopen launcher with diff account, patch the mutex, launch game again and let the launcher give your client the login ticket.
|
|
Back to top |
|
|
spyware293 Newbie cheater Reputation: 0
Joined: 28 Jun 2012 Posts: 13
|
Posted: Sun Nov 13, 2016 10:03 am Post subject: |
|
|
ulysse31 wrote: | Launcher gives the client the login ticket, sometimes through a middle man process, sometimes not. You'll need to login before you close the launcher, then reopen launcher with diff account, patch the mutex, launch game again and let the launcher give your client the login ticket. |
The client don't have launcher. just plain exe and login inside the exe. Only the first opened client can login even if the second opened client login first it will terminated as soon as login successfull (Failed login because wrong password won't terminate the client).
Edit. solved by launching every client with different window name. I realized this after putting breakpoint on kernel32.findwindow
|
|
Back to top |
|
|
|