|
United Kingdom20263 Posts
On May 24 2019 21:13 Ej_ wrote:
Video games are suposed to be fun for the players, clearly they aren't for someone with lag.
I honestly don't get the SEA players who'd rather have an unpleasant match than wait a few more minutes.
Bunch of people have taken to personal attacks against the players of X location rather than addressing the point that i made on the first page so i'd guess that they have no logical argument against it.
|
Australians play on NA? WHY would you DO that?
|
On May 24 2019 21:28 maddogmcgee wrote:Show nested quote +On May 24 2019 21:13 Ej_ wrote:
Video games are suposed to be fun for the players, clearly they aren't for someone with lag.
I honestly don't get the SEA players who'd rather have an unpleasant match than wait a few more minutes. Why clearly?
Because there's many people at multiple levels of play who welcomed the trick shown by the OP very much?
Just because you're used to playing in bad conditions, doesn't mean other should be satisfied with it.
|
I only want to block AUS, which IP?
|
On May 25 2019 17:54 ilovegroov wrote:
Australians play on NA? WHY would you DO that?
Not sure if sarcastic or not...
If not, SEA server merged with NA years ago. Playing on NA is the recommended server for AUS players. They don't have a good time playing on NA either because the ping is just as bad for them as it is for the NA continental players.
On topic, what is the legality of blocking IPs?
|
United Kingdom20263 Posts
Just as legal as pulling out your ethernet cable
|
but my 2v2 partner is australian and i love yelling AUSTRAAAAALLLLIIAAA when we get matched on AUS server  but i agree in 1v1 i haaate it.
|
|
|
If someone from NA were to play Europe or Asia server with these settings active, would it cause any conflicts?
|
On May 28 2019 14:13 PvP wrote:
If someone from NA were to play Europe or Asia server with these settings active, would it cause any conflicts?
There shouldn't be any conflicts with the EU or Asia servers. This solution only blocks every IP address from Australia, Brazil and Singapore. So if you don't restrict it to only the Starcraft.exe, you wouldn't be able to view anything on the internet from those 3 countries. It should be possible to only block the Blizzard server IPs, but since we don't know the IPs and that Blizzard could always change them, blocking every IP from those specific countries is the only for sure solution.
|
If i want block the servers of Eastern, Central and Western, how i can do? I'm a Chilean player who plays with 300+ of ping on those servers, I can only play decently on the Brazil server
|
On May 25 2019 06:29 brickrd wrote:
this is a pretty funny argument because it's literally just a bunch of people from two different regions saying "this is worse for us and i subjectively care more about how it affects me than how it affects others" and it's all over ping between casuals in a video game
+1. Obviously there’s a conflict of interest; Aussies don't want to wait forever for games and Americans don’t want to play with lag. A good compromise is one where all parties walk away unhappy. Skewing the deal in your favor is all well and good, but don’t pretend you’re not fucking over the other party for personal gain when you do so.
|
Finally got around to trying this today, and am still getting put onto Brazil Server. Does this still work? Anyone know why this could be? I linked to the executable file path, but could it not work because i am launching through the battlenet app? I don't think its possible to launch without the app so im not sure what to do...
|
maybe u permitted it thru windows , try deleting everything and making it again, like the end of the op says? (just a thought)
|
On August 04 2019 09:55 FFGenerations wrote:
maybe u permitted it thru windows , try deleting everything and making it again, like the end of the op says? (just a thought)
yeah ive been trying that. i think i found the issue though. Maybe the executable route i linked is not the most up to date one. I tried a couple but this time i just copied the pathway from the firewall popup window asking for permission... waiting a bit to see if its fixed. thanks for help~
|
been working just fine until the last patch. did this change anything for anyone else? Tried deleting inbound sc2 rules and it doesn't help. Does this not work any more after the last patch?
|
Anyone else having issues with this after last patch?
|
Each patch has a new sc2 executable, did you point everything to the new one?
|
Does anyone know the IP ranges for the korean server and the taiwan server?
|
Some big improvements! I have made it easier to setup the firewall and gotten all the servers now (US East, US West, US Central, Korea, Taiwan, Singapore, Brazil, Australia)
I have also cataloged all the server IPs in game so that the firewall rules can be strict. This way you can apply them globally on your computer and NO LONGER need to point to the new SC2 executable file every patch! It also won't get in the way of other programs because it is a stricter filter.
Steps to set up:
1. Run cmd as administrator
2. Enter the netsh command of the server you want to block
Done! This will apply to all future versions of the game as well
Australia
+ Show Spoiler +netsh advfirewall firewall add rule name="ScAustralia" Dir=Out Action=Block RemoteIP=103.4.114.128/25
Brazil
+ Show Spoiler +netsh advfirewall firewall add rule name="ScBrazil" Dir=Out Action=Block RemoteIP=52.67.103.10,52.67.109.237,52.67.159.199
Singapore
+ Show Spoiler +netsh advfirewall firewall add rule name="ScSingapore" Dir=Out Action=Block RemoteIP=13.228.101.219,13.228.112.153,13.228.191.11,13.228.206.125,13.229.23.192,13.229.26.161,52.221.101.120,52.221.47.252
US East
+ Show Spoiler +netsh advfirewall firewall add rule name="ScEast" Dir=Out Action=Block RemoteIP=107.23.122.166,34.193.133.210,34.195.101.118,34.235.72.119,34.238.213.23,34.238.30.52,34.239.26.221,34.239.54.208,52.23.20.87,52.45.62.231,52.71.51.54,54.227.157.150
US Central
+ Show Spoiler +netsh advfirewall firewall add rule name="ScCentral" Dir=Out Action=Block RemoteIP=24.105.50.0/24,24.105.51.0/24
US West
+ Show Spoiler +netsh advfirewall firewall add rule name="ScWest" Dir=Out Action=Block RemoteIP=24.105.48.0/24,24.105.49.0/24
Korea
+ Show Spoiler +netsh advfirewall firewall add rule name="ScKorea" Dir=Out Action=Block RemoteIP=117.52.36.0/24
Taiwan
+ Show Spoiler +netsh advfirewall firewall add rule name="ScTaiwan" Dir=Out Action=Block RemoteIP=203.69.111.0/24
To remove any rule run netsh advfirewall firewall delete rule name="Sc<ServerName>"
|
|
|
|
|
|
EPT
