Quote:
Originally posted by Qonquer@Apr 18 2006, 01:44
It would be monumentally easy to detect concurrent connections from the same IP and wouldn't take a huge update to do so, maybe 6 or 7 lines of code on the connect/disconnect routines that's all.
There's many reasons this wouldn't be a good move and probably why they haven't done it before. Net cafés for instance usually use the same IP for all the PCs, and a lot of DB business is done with people who use net cafés. Home networks as well will generally use the same IP for the PCs using it, even some ISPs work with a VPN or NAT system that make all the users share the same IP. It would be a definate shot in the foot if they did this as multiple connections from the same IP does not mean that someone is multiclienting.
|
This is very true, In the UK one of the main IP's in my area uses the same IP for most of the district and it can be a real pain it the backside if you goto a website that checks IP addresses and limits downloads accordingly. Not to mention like has been said I have 3 PC's on my home network and a WiFi connection for my laptop all accessing the same Internet conection and static IP address so this would really be a very stupid thing for TQ to do. Doesn't seem very likely to me.
ArkticWolf: Post #110 "The most practical way to do this is detect binary modifications in conquer.exe, fairly simple to do with CRCs or MD5 hashing etc."
Now that is a very good point and I will be unmoding my EXE until this is disproved/proven! :?