Headless server stuck on saving config

[futurepr0n]

Describe the bug After extracting assets, changing the Headless ?= to 1 from 0, I was successful in building but when executing the ./sm64coopdx I am getting stuck at the screen:

To Reproduce Steps to reproduce the behavior: build using make, go to build folder and run the headless executable

Expected behavior I am actually not sure whats supposed to happen next. I opened up a client on another machine and tried to directly connect via IP address it did not work. I tried looking for the public lobby with 0 people joined, that also was not successful. Anyone know how to properly spin up a dedicated server with the headless build that would be greatly appreciated.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information): Ubuntu 22

Additional context

[futurepr0n]

I think I figured it out now, I saw another post - using ./sm64coopdx --server 7777I was then able to use the client and connect to the ip and port. Is there any other useful server flags? Or a verbose mode, as I was not able to see any client connection info or anything in the terminal after a user connected. thanks!

[AgentXLP]

./sm64coopdx --help

[futurepr0n]

@AgentXLP

Unfortunately those weren't too helpful - From the config.txt itself I can see that its got

coopnet_ip net.coop64.us
coopnet_port 34197
coopnet_password
coopnet_dest 0

But when I tried supplying the password and connecting using the password only it was unsuccessful finding the lobby. It also does not appear to have a config flag for the coopnet server name. If I wanted to supply one how would I go about it?

coop_host_port 7777
coop_host_save_slot 1
coop_join_ip
coop_join_port 7777

What is the difference from the coop ports and the coopnet port? Would all need to be set to the same port? or all ports open on the router in order for coopnet to see the public server?

is there a way to load a mod from command line too if you wanted to run a modded server?

[Cooliokid956]

the mods enabled in the config are used when hosting with headless

[Paradox9955]

What is the difference from the coop ports and the coopnet port? Would all need to be set to the same port? or all ports open on the router in order for coopnet to see the public server?

coop_host_port is the port you use for direct connection coopnet_port is the port that the CoopNet servers use

Since headless servers can't use CoopNet, no one will see your server. They'll have to connect via IP/Port

[futurepr0n]

Thanks @Paradox9955 that was pretty much something I was trying to understand and now makes sense. So noone would be able to see the server, just join directly and thats neat. Will not worry about a server name or anything like that.

Are there any customizations that can be done with a headless server that are noteworthy? Is there any server messages you can throw on like a message of the day or a greeting? Any limitations to know about as well?

Great work everyone involved in the project and thanks to the members of the community supporting users and answering questions!