Quote (Chobot @ Aug 22 2022 07:43am)
There is a bit problem with that approach when you start all of them at once before finishing battle net connection inside a client. They will take the web token from the registry (previous account start and it's a mess xd).
Assuming u are replying to my reply, yeah I did google some multi loaders on github and all of them requires client to connect to bnet. But somehow the approach I wrote still works for me.
My guess on my approach: on bnet connection, the client uses email/pass to authenticate the server (and store the responded token somewhere in registry).
Their approach: first step is as above. After that token is also saved to file, later when user launches game, on bnet connection the client uses the saved token instead of email/pass to authenticate.
I think it doesn't mess up with the token in registry because I never reuse it, and each client never reuses it.
This post was edited by tskz on Aug 22 2022 06:00am