On October 19 2026 00:13 ProTech wrote:On October 17 2026 18:19 _fool wrote:
I like this thread. Originally it was about a guy who wrote a tiny tool to adjust firewall configuration, which I think is a nice "give back to the community" gesture.
Somehow it has ended up in a back and forth that I think no one else is interested in. If you guys really want a proper discussion, use DM instead of this thread. If you just want to publicly shout at each other, start your own thread.
because that's not what ip-range server blocking is being used for these days.
for team games, it's being used to clog the entire server up with bots that prevent anyone from laddering after a certain MMR, used by some of the players who are manipulating the ladder to blow up their division points+mmr.
the issue, is that the " status lock " feature in SC2 doesn't actually function the way it was designed, it's bugged. So people who consistently use nefarious means to prevent games from starting are just able to clog up 4K+ mmr queues, allowing zero resistance to compete with their rank 1 standing.
you can confirm this is an issue because if people at my rank were not using this method, and they were using the SC2 server blocker in the correct way, the game would re-route players away from each other that are blocking their respective servers.
like i mentioned before, the main issue is that the OP made this program with good intentions, and when you block the servers via his program it doesn't block every single server by default, the issue is they gave the public information on how to use IP sniffing software to find ALL the ranges that are available, which is what results in the ability to block all high rank players from queuing on ANY server. Blizzard isnt using dynamic IPs to circumvent this type of issue, so naturally people would eventually figure out how to do this
Rotating servers and MMR is the only way to get around it, but these days the queues are blanketed by bots clogging 4K+ mmr on all three servers, so once you've gotten to that MMR you can no longer queue up at a high level due to the small player pool not to mention the predictive 6m and 30s queue timer.
For example, when you watch Serral queue into the drop hacker, the reason he can't prevent it from happening is because that account is the ONLY account that he can queue into. Eventually the drop hackers are going to discover this thread, and realize that this is the next method of harassment to be used at the highest level.
I should also mention, I never would have understood any of this, if it weren't for the gearUP VPN. I stopped using server blocking becasue the vpn gives me playable ping, but even still 100% of my games get blocked at high mmr.
What people don't understand also, is that even IF they address the IP-Range server blocking, because this method is primarily used for automation, blizzard also needs to remove the globe in the user interface, because if you want to dodge someone, or prevent matches from starting, you can just open up the server selection in queue and when the match starts, just swap servers and it will cancel the match.
What you don't realize is that you left the wrong screen up a while back and showed that you were doing this for every match. I think you found out someone else was doing it, got mad, and now you have made the problem exponentially worse just to try and get Blizzard to change it. It's madness really because you're making "your problem" everyone else's problem now. It's a pattern of dishonest behavior with this server blocking, getting fraudulent ad revenue on your channel, and passing blame onto others for problems you have created.
EPT
