in 8.2, the password encryption has changed too, so now you can't connect to a private server with the newest sframe (the ph sframe is still using the old encryption based on DES)
To bypass the ip check, you can tell windows to add a ip to your local loopback interface, and then redirect all traffic on 127.0.0.1:4500/45xx to any private server. But it require the user to do that ...
For the 8.2 gameserver (if we will have it one day), a patched unpacked sframe should be needed, to keep easy installation by users.
For RDB reading, any language can be used. It's just not always the same API to do the same thing.
> 1. There is a valid IP List in the Client itself
> 2. The SFrame is checking the ip with a server in the internet.
>
> If i'm a professional IT Company I would choose the second way to be sure that i'm able to modify
> the IP lists without patching the client. If there is a server that is responsible to do these ip checks
> we only have to emulate this server and to modify the ip. That can't be very hard^^
I think it's hardcoded in the client, as the client is packed (and shouldn't be unpacked

) and even without any data.* it check before the auth_ip. You may want to test to alias the "devel" hostname with the hosts file and remove the /auth_ip parameter as it seems by default, that sframe use "devel" as the auth_ip, but never checked that