Quote:
Originally Posted by yuri.ccp
Please stop this unnecessary discussion about need of the launcher.
Some people simply have problems with the current NCSoft launcher that can make unplayable in some cases.
In my case for example, I need to run the game directly simply because the launcher don't run through WINE. But different people have different issues with the launcher and need to run the game directly.
So with someone help how to run the game bypassing the current launcher it will help us a lot.
Ps.: joka666 'client.exe /launchbylauncher /sesskey /CompanyID: "12" /ChannelGroupIndex: "-1" /LoginMode 2 -lang:English -region:0' don't work anymore since the update 50.
Currently I tried to decrypt the AuthnToken base64, but it only turns into two UUIDs. The first is based on login data (user/pass) and always the same for the same account, the second is auto generated by launcher and always change, probably is received by launcher auth server to allow that instance of the game.
Probably the only way to bypass the launcher now is create another one that mimic the current data passed trough the NC auth servers, receive their UUIDs and reply them to client.exe
|
True, the only way to do that is to emulate the launcher and made it compatible for Linux users.
However, for Windows users, creating a new launcher with Login information is kinda pointless.
And Ignore @
[Only registered and activated users can see links. Click Here To Register...]
He clearly did not READ the replies after the Silverfrost patch. And still thinks hes method works. Which I find funny.
@
[Only registered and activated users can see links. Click Here To Register...]
If you have EZBot, download ProcessExplorer from Microsoft.
[Only registered and activated users can see links. Click Here To Register...]
Then, start EZBot, then let it start Client.exe as it normally does.
Then, start ProcessExplorer.exe and find "Client.exe" from the list.
After that, double click it OR right click -> Properties to see the Parameters IF EZBot still uses parameters to log you in to the game.
Otherwise, I can only guess, they found a way to send & receive the right token from client to server and vice versa to trick the "client" which was run from ezbot started by the Launcher. (Sounds confusing, I know)