By default, the session name is now set in the GameUserSettings.ini file rather than on the command line, to mitigate a possible bug in Ark that causes it to always use the default port of 7777 when there are spaces in the session name.
Hello, im not sure if its something im doing wrong, or something that your aware of, but for some reason any mods that is a 'skin' does not seem to install, it just says "mod install failed". Example is "modern structure skins" found on the curse forge website, ModID is "1020402" All other mods work fine for me, but any mods that are 'skin mods' just simply wont work.
Edit: Dont worry, i found out you just go to the mods section in game and sub to the skin mods there.
Hi, thanks for highlighting this, glad to hear you got it sorted.
I'll look into why skins mods seem to work differently, and maybe add a warning that they need to be subbed in the game mods section to make them work.
Its because of the new update, you sub to the skin mods yourself, if other people also have that mod they can see the skin, if they dont then they can't.
Unless there is a server setting for it im unaware about.
If your server is running but not showing up in the server lists, it's usually because of port forwarding issues, but it can also be due to missing root certificates. This caused me a few hours of frustrated hair pulling when ASA first came out. I followed the instructions here and it fixed the problem for me.
I have an odd request. When you get the chance, can you add an option to not override the gameusersetting.ini with the session name set in arkasm. It seems there is a bug, or very weird design choice, where if you have spaces in you session name in the start cli it will not respect a non-default port. So I tried to set up a second server on port 7779-7780, and the start cli showed it in the cli and it shows up in the server list, but if you try to connect it just connects you to the server using the default port 7777.
Removing the spaces fixes it, and my understanding is that the gameusersettings.ini session name will trump the cli name if it is different according to the people who figured out that this was what was going on, although I haven't gotten around to testing that part myself.
So I would like the option to have the session name in arkasm not have spaces but the one in the actual gus.ini to have the spaces so it shows up in the server list with spaces.
I'm still trying to come up with an elegant solution to this, it's taking a bit longer than I'd hoped because I wasn't able to work on it over the weekend as planned. But, I'll try and get an update out asap.
The solution I settled on was to change the default behaviour to set the Session name in the .ini file, rather than via the command line. Hopefully this will fix the issue you were having, let me know if it is still not working.
← Return to Server Manager
Comments
Log in with itch.io to leave a comment.
Version 1.53 now available
Hello, im not sure if its something im doing wrong, or something that your aware of, but for some reason any mods that is a 'skin' does not seem to install, it just says "mod install failed". Example is "modern structure skins" found on the curse forge website, ModID is "1020402" All other mods work fine for me, but any mods that are 'skin mods' just simply wont work.
Edit: Dont worry, i found out you just go to the mods section in game and sub to the skin mods there.
Hi, thanks for highlighting this, glad to hear you got it sorted.
I'll look into why skins mods seem to work differently, and maybe add a warning that they need to be subbed in the game mods section to make them work.
Its because of the new update, you sub to the skin mods yourself, if other people also have that mod they can see the skin, if they dont then they can't.
Unless there is a server setting for it im unaware about.
When will the abberation map be added?
In the next update, which should be out tomorrow.
Awesome. Thank you!
Followed everything that was given and the damn thing wont show up, hours wasted to try and get this horse crap to go....
If your server is running but not showing up in the server lists, it's usually because of port forwarding issues, but it can also be due to missing root certificates. This caused me a few hours of frustrated hair pulling when ASA first came out. I followed the instructions here and it fixed the problem for me.
a quick question. Does this support clusters or group servers? Thank you for all the work you are doing on this!
It can set the cluster id, so it should work with clusters and group servers.
thanks. I was looking at the thumbnail and it had in bold text that it only runs one server. So was wondering about clusters.
Currently multi-server management is a bit buggy, but I'm working on making it better.
I have an odd request. When you get the chance, can you add an option to not override the gameusersetting.ini with the session name set in arkasm. It seems there is a bug, or very weird design choice, where if you have spaces in you session name in the start cli it will not respect a non-default port. So I tried to set up a second server on port 7779-7780, and the start cli showed it in the cli and it shows up in the server list, but if you try to connect it just connects you to the server using the default port 7777.
Removing the spaces fixes it, and my understanding is that the gameusersettings.ini session name will trump the cli name if it is different according to the people who figured out that this was what was going on, although I haven't gotten around to testing that part myself.
So I would like the option to have the session name in arkasm not have spaces but the one in the actual gus.ini to have the spaces so it shows up in the server list with spaces.
Hi zerepsj,
I'll certainly look into this for you, it sounds like a strange bug and I'll see what I can come up with as a workaround.
I'll hopefully have something sorted by early next week at the latest, and I'll post here when it's done.
I'm still trying to come up with an elegant solution to this, it's taking a bit longer than I'd hoped because I wasn't able to work on it over the weekend as planned. But, I'll try and get an update out asap.
The solution I settled on was to change the default behaviour to set the Session name in the .ini file, rather than via the command line. Hopefully this will fix the issue you were having, let me know if it is still not working.
Just have time for a quick test right now, seems to work. I'll let you know if I run into any issues, thanks!
Been looking for a better manager! This looks like it will fit the bill! Thank you!!!
Thanks for the nice comment. Please let me know if you find any bugs, or if you have any suggestions for improving it.