Actually a ping that high locks you out of any archer build or auto attack build.
150ms is fine if you plan on dealing no more than 1-2 attacks/skills per second.
Average human reaction time is around 150 ms, so having a ping around this is already good enough and feels like having a 0 ping. It is good for PvP but if you are planning to just PvE all the way, a ping straight up to 400 ms is already playable.
Having a low ping is only necessary when you are doing a fast paced genre, much like to those of PvP oriented and that just it (MOBAs). It doesn’t apply to PvE as it is more casual and laid back.
3 Likes
280-300 ms from india 
, hope there is a eu server
but the elitist asian blood in me is telling to hit the highest dps I can possibly hit even with the circumstances im presented, to make my ancestors proud.
This post was flagged by the community and is temporarily hidden.
4 Likes
This. Doing ping tests to a server that is empty right now proves very little. That won’t be your final ping at all.
######inb4 “there’s 300+ on the server right now”
2 Likes
This post was flagged by the community and is temporarily hidden.
Wouldn’t a full tracert be a more effective test?
ping 131ms… not bad for me 
I played the betas (am from Portugal) and it was fine, but ive read that some classes that do a bunch of hits in short amount of time need very low ping 40-50 to actually register them, so yea its kind of a concern but im not going to cry a river over it.
my ping is 110ms, I’m from Belgium (EUW)
It would be, you should explain it so others understand.
lol I did it this way and got 97. I am super giddy right now. I can make an archer ;D
Should be as simple as replacing ‘ping’ with ‘tracert’.
I can’t test right now as I am not at my home computer.
so many hops…
Tracert is typically used to troubleshoot problems with connecting to a specific service or services, whereas ping is a direct test of how long it takes for a packet to be sent to a service and back to you.
Based on this I think that ping is a reasonable testing point. It is not exact, but neither is a tracert, it just gives you more information.
https://www.freeccnaworkbook.com/blog/ccna/ping-vs-traceroute-vs-pathping
[quote]PING, is an application based on the ICMP protocol which is used to send echo packets to a destination and expecting to receive an echo response and it calculates the RTT (Round Trip Time) from when the packet was sent to when the echo response was received. Generally when using PING on a LAN network you can trust that what it is saying is accurate unless you have foreknowledge of network devices in the transit path that prioritize ICMP over mission critical TCP/UDP Traffic. This however is very common in networks that utilize unified communications, meaning voice and data on the same network. This is because QoS Policies are put in place to ensure voice traffic and other mission critical traffic is prioritized over ICMP thus indirectly affecting the RTT time of an ICMP ping test.
Trace-route is another method commonly used by technicians and engineers to diagnosis latency in the transit path however any engineer that has studied how trace-route works would know that its results are nearly always misleading.[/quote]
TL;DR: PING is fine. TRACERT is for checking the individual hops to troubleshoot a connection failure.
139ms I can live with this.
so is there a reason why I can’t connect to over half of the IPs made in the traced route? As far as I know my internet is absolutely uninhibited.