I was able to attach the debugger to a clean version of rb and debug kupo with vs2019. Its possible that if you have a 3rd party plugin or routine...
Nothing really has changed, should be working. I'll see if there's something vs2019 related.
Can some cn users test and see if you are able to once again reach the cn nav server.
I've pushed the updated offsets.
I've been at the doctor all day today. I'll be home shortly to work on it.
Can you try pinging our cn server again, see if it is still unreachable?
Can some people please ping 22.214.171.124, and let me know if you are able to reach it. That way i can switch it back to the closer server.
I'm going to redirect the cn nav to the na nav, latency will be pretty high but should still be usable.
try ipconfig /flushdns then pining and...
Please try pinging rbnav.cn.buddyauth.com, and running a traceroute to it.
It's likely a routing issue with the data centers isp. There are incoming connections.
I'm seeing connections to the server. Might be a routing issue.
Restarted, should be working now.
It's most often caused by dns issues preventing authentication from happening properly. Try changing your dns to google dns.
New version should allow you to queue for chocobo races.
check the ContentUICategory for the correct instancecontentresult to pass to the queue...
DutyManager api has been overhauled.
The following api functions have been added
Do a clean install. This issue is caused by a plugin your using overriding the navigator with a outdated version.
Update has been deployed
Wanted to give an update on this. Getting queueing support is done just putting some finishing touches on the api so that its in an actual usable...
I've restarted the navigation server, investigating why it froze in such a manner.
new build coming now that resolves the issue
Separate names with a comma.