Page 1 of 1
FFXI-3331 Error
Posted: Thu Jun 09, 2016 12:51 pm
by HackGoDz
Hey everyone, a new client update rolled out yesterday and I was wondering if theres a fix for this? Thanks!
Re: FFXI-3331 Error
Posted: Thu Jun 09, 2016 2:11 pm
by seffy
Peculiar, I've had no such issue logging into my own server.
Iis it possible that the DS code hasn't even been updated yet to reflect the changes to the client?
Re: FFXI-3331 Error
Posted: Thu Jun 09, 2016 4:25 pm
by HackGoDz
seffy wrote:Peculiar, I've had no such issue logging into my own server.
Iis it possible that the DS code hasn't even been updated yet to reflect the changes to the client?
Yup. I've been having this issue all day.
Re: FFXI-3331 Error
Posted: Fri Jun 10, 2016 1:54 am
by Delaide
Yes, the current version the server supports is: 30160427_0
https://github.com/DarkstarProject/dark ... rsion.info
The current client version, if you update now, is 30160602_0
I just modified my version file for my server, since I had to update, but I cannot chose to update to the 0427 version, only from my old install to the 0602 version. However, that will not work if you are playing on someone else's server. Plus, that will create npc and mission conflicts. I am hoping it is updated to the 0602 version soon myself, since I can't downgrade or update to a specific version only...
Re: FFXI-3331 Error
Posted: Wed Jun 15, 2016 12:16 pm
by Juno
I think I may be having the same issue. I was able to get it running on four separate occasions over the last week but this time not matter what I do I keep getting that 3331 error. I can log into other peoples servers just fine but not my own, although there could be conflicts in logging into other servers. if anyone knows a workaround I could do I would love to know, I've reinstalled 3 times and am don't know how many more 6 hour updates my sanity can take, thanks in advance!
update:
I figured it out in case anyone was wondering. changing the version.info inside of the darkstar folder to the current version that your client is updated to, in my case CLIENT_VER: 30160602_0 fixed the problem.