It’s 100% IMC fault, whether their netcode or the server plan they hired. SA servers are hosted by AWS Brazil, which also hosts Diablo 3 and League of Legends servers. I have around 30~50ms to these servers, and yet over 300ms to SA server, sometimes with an average of 500ms. It’s definitely not our ISP fault.
Well, I wasn’t pulling it out of my ass you know, of course I’d check everything on my side before complaining.
Guys, it’s a route problem that is causing all this high latency/ping on SA server and players. The initial maps can be played quite nicely but things will start to change as soon as you reach Miners Village. At that point you will start to notice two things:
• Ping will drastically change based on your channel(even if that channel is empty)
• Thanks to a route problem, if you attempt to move to another area there’s a huge chance that the game will send you back to the main screen(server selection) and not let you enter in that map until you change channel. Here comes the route problem that I spoke above.
You guys might say ‘ah, if that’s the case then just switch to another channel and continue playing!’ …right? Nope! As I just said, after getting to Miners Village this problem will start to become more and more common… If you’re lucky to enter the map you will experience high latency thanks to the route problem AND here’s the fun part: After certain hour the SA server starts using queues… If you’re smart then you already knows what I’m about to say… If you move to another map and the channel has the route problem then congrats, you just earned a chance to wait on a 600+ queue just to get in game once again!
… You know the funny thing? If you wait in that queue and the channel you choosen is also one of the above, guess whats happens! You’re just going back to the main screen once again and have to wait the entire queue again and again until you find a working channel.
So hey folks, the OP isn’t complaining over nothing… He does have a reason! Of course I’m know they are working on it but I just think they are taking quite a while to fix this issue…
1 Like
why you always whining?
mofo whining
mmmh
oh my god
stop effin whinin?
Disparando 52.67.15.170 com 32 bytes de dados:
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=26ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=26ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=26ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=35ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=29ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=35ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=31ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=26ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=26ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=30ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=31ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=31ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=28ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=27ms TTL=115
Resposta de 52.67.15.170: bytes=32 tempo=33ms TTL=113
ingame
180~2000ms
any npc 3~5 sec to respond 
I wonder who these “others” are. Mid-East countries? And hellz no on the merge. They already split Orsha from SA because of hate issues spamming the chat 24/7 ain’t doing that again. And I don’t even know if Klaipeda is still as packed as it used to be. (Been on Orsha since day 1)
it has become clear that IMC does not want the Brazilians, which is a great ignorance, since they are a large audience and that would give a lot of money for the company if they were being respected as minimally should …
whenever you send a ticket on the subject, this is the answer
[quote]Greetings Savior,
Thank you for contacting Us.
We apologize for the inconvenience. Developers are doing their best to tweak our servers to improve players gaming experience.
Hoping for your patience and understanding.
Regards,Tree of Savior Support[/quote].
the staff stopped reading, just do ctrl c + ctrl v in response
1 Like
Salute is really going bad. At certain times i myself get a decent ping, but most of the times NPCs takes 3 to 4 secs to act, skills rollback and high delay. Its not something we are getting wrong, it is something wrong we are really having.
My internet is by far good enough to play. Im guessing most of the brazilian players play under 5]10MB internet speed, while mine is 30 MB, so its more than enough.