-
Member
Originally Posted by
SniffingPickles
I wouldn't use this as a certifiable way to not get caught botting. It's literally just blocking battle.net's ability to talk to your computer vice versa. This project was done for people who get annoyed from friends on battle.net spamming them to do rbgs/raids/farm stuff/carries etc; not for botters...although you can use it with some creativity involved.
well I do know once its properly disconnected if I switch to one or two raiding alts before disconnecting and re-connecting completey with it turned the program turned off people that have me on real i.d have asked If I deleted them since they cannot see me online which is why I was thinking before running any bots log onto an toon you don't mind wish people seeing, run this great program and disconnect properly from battlenet then switch to your bot from what I can see is the safest way If you have real i.d people on list unless I'm wrong please correct me If I am.
-
Member
Hi, I think i forgot to unblock the port before i shut off my computer or my wow, And now i can't open my wow or battle.net. Help needed!
-
Originally Posted by
LunaticFridge34
Hi, I think i forgot to unblock the port before i shut off my computer or my wow, And now i can't open my wow or battle.net. Help needed!
http://www.ownedcore.com/forums/worl...ml#post3342797 (Simple Battle.net Disabler :: Appear Offline to Your Battle.net Friends)
-
Member
Wondering if this still works and will it work for Diablo 3? Thank you!
-
Originally Posted by
dinosawrex
Wondering if this still works and will it work for Diablo 3? Thank you!
it should, if not please let me know :P I will update accordingly.
-
Member
i Dont play wow so dont know if it works for wow atm. But it doesnt seem to work for diablo 3 since you get disconnected from the came when offline from battlenet
-
Originally Posted by
dinosawrex
i Dont play wow so dont know if it works for wow atm. But it doesnt seem to work for diablo 3 since you get disconnected from the came when offline from battlenet
The ports it uses are:
80: Standard HTTP port, not blocking that
the other 2 are for the game.
This software blocks the following ports: minus 80/443 (HTTP/HTTPS/SSL)
80, 443, 1119 |
80, 443, 1119 |
So yes, it will not work since the game runs on 1119 exclusively
Last edited by ev0; 01-13-2016 at 03:02 PM.
-
Awesome for botting ^^
The only thing i need now are friends :/
-
Member
Been using it now for a while still works during 6.2.3 for wow. Great for botting when not at home and such
-
Member
not working for me. Tried to disable it. it adds the outgoing firewall or whatever it is. but doesnt disable real id? maybe its because of Eset firewall but i disabled it and still no good. restarted wow and all that good shit..
windows 7 home premium 64 bit
US btw
-
Originally Posted by
jadethread
not working for me. Tried to disable it. it adds the outgoing firewall or whatever it is. but doesnt disable real id? maybe its because of Eset firewall but i disabled it and still no good. restarted wow and all that good shit..
windows 7 home premium 64 bit
US btw
Yes, you have to be using windows default firewall for this to work. Or you can manually block the same ports in your 3rd party firewall.
-
Private
This seems to not be working after today's maintenance. I still appear online to friends. It was working fine up to last night.
Edit: There's a thread on the official forums about this http://us.battle.net/wow/en/forum/topic/20742925295, albeit not this app specifically but port blocking.
Last edited by larathiel; 03-23-2016 at 07:55 AM.
Reason: official forum post
-
Originally Posted by
larathiel
This seems to not be working after today's maintenance. I still appear online to friends. It was working fine up to last night.
Thanks for letting me know, I'll try and look into it this weekend.
-
Member
Yeah It's definetely fixed after yesterday's patch 6.2.4 which they said it was specifically to address stuff regarding Battle.net compatibility and such.
Edit: I tried adding to the firewall rule ports 55455, 55454 which Bnet uses and it does kill the desktop app connection, but once you log into Wow your Bnet is back online. 1119 seems to not be cutting it anymore as of yeserday.
Last edited by DonRP; 03-23-2016 at 12:00 PM.
-
Originally Posted by
DonRP
Yeah It's definetely fixed after yesterday's patch 6.2.4 which they said it was specifically to address stuff regarding Battle.net compatibility and such.
Edit: I tried adding to the firewall rule ports 55455, 55454 which Bnet uses and it does kill the desktop app connection, but once you log into Wow your Bnet is back online. 1119 seems to not be cutting it anymore as of yeserday.
Thank you for helping investigate this issue, I'll sniff out some network stuff this weekend and have a working prototype shortly.\
Update:
I only have a short time to test things out. I blocked the following ports, sniffed packets etc. Was only able to disable bnet for less than 1 minute which leads me to believe they're trying to patch this and it may be difficult to build a FULL blocker. I'm going to see if i can built some firewall filters to possibly block IP's instead of ports.
Ports I tested were: 55454, 55455, 52942, 1120, 1119, 3724, 57297, 58419
Last edited by ev0; 03-23-2016 at 06:28 PM.
-
Post Thanks / Like - 1 Thanks
garbanzola (1 members gave Thanks to ev0 for this useful post)