Quote:
Originally Posted by Neuro Toxin
You need the servers to send the end point URL to the redirect service to get a proper work around.
1. Client uses server command for a URL
2. Server sends URL to redirection service with a qualifier like a SteamID
3. Server receives response that the request has processed / store to a database
4. Server sends MOTD request to client with the qualifier
5. Client connects to redirection service with the qualifier
6. Redirection service reads end point URL from step 2
7. Client redirects to requested end point
Eg: The client always sends the same qualifying URL such as: http://weblync.xxxxxxxx.com/redirect.php?SteamId=<SteamID>
|
I originally implemented something like that (similar to what you have here), which took most of yesterday, and it works fine. However, I find that the 2-domain approach works just as well and is a lot simpler. I think using that approach would be better for a plugin like this so consumers don't have to set anything up and there's less that can go wrong.