First, there is no setting in PingPlotter to ignore the final X hops - any non-responsive hops at the end, being unresponsive, don't give us enough information to know how many hops are there. Also, we don't have any facilities to ignore any intermediate hops either - so even if the final destination did respond, we couldn't ignore the hop before it.

That said, there are some pretty solid options for you here.

First option: you can just target the last responding hop. If the last hop that responds is 12.129.193.246, then just trace to 12.129.193.246 instead of us.logon.worldofwarcraft.com. That should do what you're after, although it does take that "extra" step of tracing to the final destination first to figure out what the last responsive target is.

Second option: you can switch to using the TCP packet type (http://www.nessoft.com/kb/51), which *is* allowed through the WoW firewalls (since that's what "language" the login server talks). Change your configuration (or set up a new named configuration, if you're using PingPlotter Pro) to use the packet type "TCP Packets", and then change the TCP Port to 3724 (that's the WoW login port). Once you've done that, you should be able to see the whole path to the target server.

- Pete