Server Stuck On Launch
-
SnoopDogsBlunt Couldn't edit my post but i have already deleted my server key.
-
Hello! I was having the exact same problem as you and after consistent digging through forums I found a solution. What I did was within the folder where you have your game and configs(should be called game server or something like that), make a folder called t6r first. Then within that folder make another folder called data. You then want to put your configs in this folder. This worked for me, let me know if it worked for you!
-
Thats a bad idea as the t6r folder will be phased out soon and is deprecated since a long time.
You simply have not put the folder in the correct place. (That the guide is outdated is not helpful, I know).
You have to put the files under %localappdata%/Plutonium/storage/t6
-
Xerxes said in Server Stuck On Launch:
You have to put the files under %localappdata%/Plutonium/storage/t6
you can make a new guide though with updated intructions!
-
Xerxes When you say "Files" which files are you referring to?
-
SnoopDogsBlunt the server configuration files.
-
Dss0 Im gonna have to wait till a new guide comes out cuz its still not working for me. Ty for the help though.
-
SnoopDogsBlunt the files need to go into C:\Users\yourusername\AppData\Local\Plutonium\storage\t6.. not into a folder called "localappdata" in your game folder.
If you type %localappdata% into the explorer target box or the windows "run" dialogue you'll get there (appdata folder is hidden by default).
-
Dss0 Jesus Christ it worked, thank you. Glad to know im a total dumbass lmao.
-
Just putting this here in-case someone has the same problem I did. I had a very similar issue where the server console would stick at "Loading fastfile seasonpass_load_zm" and I found the problem to be with my "dedicated_zm.cfg" in Plutonium's AppData location.
Within my config under the map rotation section at the very bottom, in copying and pasting different maps I had accidentally omitted the "sv_maprotation" and just left the "exec zm_[whatever_map].cfg map zm_[whatever_map]" command. In adding back "sv_maprotation" before the "exec" command, the issue was resolved and the server began to function normally.
