Game mode: [Enter game mode here: Online private
Type of issue: [Enter one of the following: Bug
Server type: [Enter one of the following: PvP | PvE-Conflict | PvE
Region: usa
i have tried to connect to multiple severs and i keep on getting fail to authenticate when i try to connect to the severs i can get on the official severs just fine i have tried to uninstall Conan and reinstall and battle eye and nothing works
Hey @kavfire
Welcome to our community.
If this issue does only seem to happen on private servers, please make sure youâve also installed the required mods for each server.
it could be that those servers are region locked, did you check if US region isnât blacklisted?
the last sever i tried i put all of the mods in the right order yet i still have to restart the game to try to join the sever
well thatâs normal, youâll always get restart no matter what (unless no mods are used and your mod temp is empty) it is by design unfortunate as it is
thatâs patently false information, Im afraid.
kavfire, if I were you I would check and double-check your mod install folders. If the mod handler is still restarting after setting the proper load order and this has persisted after an integrity check and a reinstall, Iâm going to bet youâll find your problem there.
Try unsubscribing from everything on the workshop, then removing the modlist.txt file from the conansandbox/mods folder (thats also where your load order is saved, so maybe doublecheck that and keep a copy for later use) and then making sure that you dont have anything in steamapps/common/440900
That would be the way to perform a âcleanâ start in your mods directory.
Not for him, and not for me. My game always does a restart after checking the mods, even if everything is correct.
What also can happen is that you have a newer version of the mod than the server does. It happens from time to time that people cannot get onto my server because of this.
My server does a restart at 5AM each morning. If an update to a mod comes during the day, the games of those players not already on the server get the update via Steam as soon as Steam starts on their PCs. But the server does not have the update yet (even though Autoupdate was checked on G-Portalâs server administration page), thus there is a mismatch. I have to restart the server manually to get the update. Or wait for the next dayâŠ
I dont use a managed host. So I dont know what kind of issues gportal is giving you. But the only reason you should ever see the client mod handler is if your modlist.txt isnât configured to exactly match the load order running on the server, or if youâre not running the same mod version as the server.
That screenâs entire purpose is to prompt you that your client has not loaded with the exact same modlist setup as the server youâre trying to join and to give you options to rectify that (download the right mods and RESTART TO LOAD YOUR CLIENT WITH THE CORRECT MODS IN THE CORRECT ORDER)
If you have the right mods in the right order, you will never see that screen and you will never need your client to restart (because that would be entirely redundant) except for version mismatch
TL:DR you dont have the right configuration saved clientside, so the mod handler steps in to fix it for you and restarts your game with the right setup necessary to join with.
Well, I used G-Portalâs server adminsitration tool to subscribe to the mods, brought them into the desired order and then activated them.
All the players on my server, including myself, never subscribed to any mods manually, we all got the mods via the gameâs modloader.
And still every one of us sees the mod-mismatch page after selecting the server, and then have the game restart. Even if the mods on server and client are the same version, i.e. the mismatch page says âOKâ.
Mad_Marius prompted me to dig in the subject again, and apparently both answers are correct
it will prompt restart even if you subscribed through server, because server actually creates temporary modlist unless youâll manually edit your local modlist.txt (or copy-pasting modlist.txt from server) just be aware that paths need to be fixed, I just tested it and my server accepted login attempt without client restart
thanks Mad_Marius
Should the modloader not be responsible for making the correct order on the client?
it does, only temporary
itâs probably because local modlist is dedicated for singleplayer and this way it is kept and not overwritten each time
Sorry but no. Both answers are not correct.
I described exactly what the function of the mod handler is. To download the mods and restart your client to temporarily put them in the right order.
EVERYONE IF YOU WANT TO NOT SEE THAT SCREEN YOU NEED TO MANUALLY SET YOUR LOAD ORDER
Ok Starwalker. Lemme give this one last go.
The client modloader is a mod LOADER not mod LOAD ORDER SETTER.
It says âhey server, what order should I be in? Oh Im wrong? Let me tell the player this so they dont freak out while I get ready to restart the game in the right order to be compatible with the serverâ
Then it says âok Im going to restart the game using the modlist load order the server has instead of the one that the client has configured as a defaultâ and then does that.
It does not edit the modlist.txt on the clientâs local machine.
Only you have the power to set your load order and avoid this screen.
And to make this abundantly clear, because the people that are arguing against me are again, voicing PATENTLY FALSE information.
You. must. SET. your. load. order. manually. if. you. donât. want. to. see. that. mod. loader. screen.
Its. job. is. to. correct. your. mismatched. modlist.
Fact is: I donât mind the extra minute it takes for the restart 
Haha. Which is a.o.k. if thatâs good with you, but entirely counterproductive for OP, who is trying to potentially avoid an authentication failure.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.