Opticraft Community
Discussion forum => Classic => Archives => Server News => Topic started by: optical on March 05, 2011, 05:38:32 am
-
Of late players have been getting "Could not authenticate your username" messages when trying to log on. Turns out i had a minor bug in my code that was causing this for some users. I have now fixed the bug and improved the authentication system, so this should no longer happen. Sorry guys!
With these changes users can now use the direct connect feature of WOM, albeit in a limited manner.
The URL To direct connect to opticraft at this time is: mc://play.opticraft.net:9999/<username>/junk
Note: This url WILL be changing soon, so check back in the upcoming weeks.
This url will only work for some users. In order to be able to use it, you must have logged in normally (via web or normal wom connection) on the ip address you are using now. If for some reason your ip address is differenent, you will get a "Cannot authenticate username" error.
TL;DR: Direct connect should only be used when www.minecraft.net is playing up.
Cheers,
Optical
-
Okay thanks opticalza! I appreciate it :)
-
Wait so if the cached is broken, we can connect using the direct connect? But only if we've been to opticraft before?
-
Yes, if you have the same ip as you had last time you played.
-
Ok cool thx
-
Sorry for the HUGE necropost (Could be the biggest ever ;) ) but I just got one of the authentication issues. It is probably be my end, but just wanted to let you know.
-
Sorry for the HUGE necropost (Could be the biggest ever ;) ) but I just got one of the authentication issues. It is probably be my end, but just wanted to let you know.
which wom client are you using? The oldest versions only work with direct connect and resume now, due to a change in the way minecraft.net connects to servers.
-
Sorry for the HUGE necropost (Could be the biggest ever ;) ) but I just got one of the authentication issues. It is probably be my end, but just wanted to let you know.
which wom client are you using? The oldest versions only work with direct connect and resume now, due to a change in the way minecraft.net connects to servers.
I was using 1.7.5 then that happened, then I updated to 1.9, it still happened. Then I tried using "Sign in" and that seemed to do the trick.
-
Use sign in for guaranteed success. Resume will not always work as it bypasses actual minecraft.net authentication
-
Use sign in for guaranteed success. Resume will not always work as it bypasses actual minecraft.net authentication
Oh, ok, thanks! :)
-
That's way better , thank u.