actually some servers work, the one i was auto select was not working
tho when i selected my char it has an delay of 2 secs to really connect to the server that provides the map im on,
actually is fixed

Are you connecting to North America game server of ragnarok online? Is it okay to connect without Full VPN mode?

And according to your configuration, it seems you're changed the connection protocol from UDP (default) to TCP. Is there a reason for that? If UDP is working on your environment please use it to get more connect speed.

i changed by two reasons to tcp , first one is because ro1 uses tcp coneccion as far i know and the second one is because when i use udp my game and latency are too good that i can even notice that the server is lagging(mobs delay to act)
also is working well without fullvpn mode , i hear a online radio when i play so it would also blast my bandwidth
fast connect mode seems to have fixed the connection drops

> i changed by two reasons to tcp , first one is because ro1 uses tcp coneccion as far i know

Yes ragnarok online game is TCP based game but "connection protocol" of Mudfish is used only for data path between Mudfish client and Mudfish node. So it's independent one.

> the second one is because when i use udp my game and latency are too good that i can even notice that the server is lagging(mobs delay to act)

You mean it was too bad, right? Weird as already I mentioned at above.

yeah it disconnects and lags when using udp mode
i tried most of em and tcp 443 seems to work better

Okay I see however it's weird. Is there any network firewall or QoS appliance on your network? Without it, I can't imagine why TCP 443 is working better than others.

the only thing that i can think of is netlimiter 4 but is not configured to change anything else than my web
browser however it can be cause of im having packet loss and using tcp fix it and the case of port 443 maybe some isp priority

I'm not sure how NetLimiter 4 is working on Windows. However it's working based on port number filtering, it could affect because most of web browser are accessing to port 80 (HTTP) and 443 (HTTPS) so NetLimiter could mark packets to port 443 as high priority.

it doesnt work port based , it uses process based bandwidth limiting

Oh I see. Then it seems I misunderstood the feature of NetLimiter. Thank you for information. :-)