Would anybody advise against supporting the friends list packets for non-war3 clients? They appear to function, but it seems like a fairly easy way for bnet to detect a bot...
Has bnet written anything to automatically detect a bot and block it's ip from connection forcing closure or something along those lines? I don't beleive so..since bnet is more worried about ladder abuse/hacking than bots. And I doub't they monitor every connection anyway...it probably wouldn't raise much of an alarm.
Quote from: hismajesty on September 15, 2003, 07:00 PM
Has bnet written anything to automatically detect a bot and block it's ip from connection forcing closure or something along those lines? I don't beleive so..since bnet is more worried about ladder abuse/hacking than bots. And I doub't they monitor every connection anyway...it probably wouldn't raise much of an alarm.
Often, if you do something stupid, you get ip-banned. They will, perhaps, eventually notice this and make it an ip-ban.
Hrm, perhaps I should go ahead and add it, but make an option to disable it?
That's what I would do :)
Quote from: Camel on September 15, 2003, 09:14 PM
Hrm, perhaps I should go ahead and add it, but make an option to disable it?
I doub't blizzard will even notice it as of now, in the future they'll probably become bitchier and make it an ip-ban but for now...I'd go for it. :)
Solution: send 0x65 and 0x7D upon recieving 0x75. Also allow double-clicking the clan/friends tab to refresh either (except clan list when non-war3). This means that the friends list will not load automaticly while on a non-war3 product, but the user will still be able to request the list manually.