With FastConnect Mode enabled, these ping responses are from your local computer (Its very unique feature of Mudfish). If you'd like to test with 'ping' command, you can see your real ping result after disabling FastConnect Mode. However the best way is that if your game has a interface to know your ping status, it'd best exact resource to know.

Blade and Soul has no in-game Ping command or interface, so I use the Blade and Soul Ping Tool from Dojo forum and Resource Monitor. I see 0 ping to Dallas server from both of them.

Without FastConnection mode, the ping is even worse than what I normally have (about 250-270).

So, I'm really play at 0 ping by using Mudfish with FastConnection mode?

No. 0 ping is a fake motion of motion to maximize the packet delivery from game client. I think the correct way to figure out the good mudfish node is:

* Without FastConnect mode, pick a best mudfish node with testing other nodes based on RTT avg and std.

* When you pick one then enable FastConnect mode.

I think thses steps are one of things you can try.

Since the game server is located in Dallas, doesn't it mean that Dallas node would be the best choice?

No normally it's not and should be very dependent to game policy and RTT. If the game is restricting accesses from foreigh countries, you should pick a node of US-based mudfish nodes. Buf if it's not, you can pick any node which shows lowest RTT avg and std.

About chained servers, I hear it helps to optimize the latency. What is a good way to setup them? I heard from Wtfast users that set one close to my place, and one close the the server location. Will it be the same with Mudfish?

Normally yes though it's not always true. At advanced node option, you can find a magnifier icon which show more detail available node options. At there you can see what's shortest RTT is for your item.

Thank for being helpful. One more question: There are choices for UDP and TCP connections. Should I switch between them according to the game server being TCP-based or UDP-based, or should just leave it as UDP?

Please leave it as UDP if it works. That protocol is totally independent from game's protocol because it's used for data path of mudfish. A reason why TCP exists there is to avoid network firewalls.

I don't know whether the fault lies in the undersea optical fiber in Southeast Asia being under maintenance mode or not, but my connection to BnS NA with Mudfish (via a node in Texas, Dallas - HostUS) is recently very hicup with increasing lag spikes and constant disconnection at certain hours. Meanwhile, without Mudfish, I can still access the game normally with some delay, but hey, I don't pay Mudfish to play with a normal connection.

Need to look into more details. Could you please check it using http://pingplotter.com/ tool to see where this hicup happens? I think you can try to test against Texas, Dallas - HostUS node. There are multiple possibility related with this issue; 1) might be on your ISP, 2) undersea optical fiber 3) mudfish node itself 4) game server ISP.