legoduded / palworld-worldoptions

A tool for creating WorldOption.sav and applying the PalWorldSettings.ini for dedicated servers
132 stars 14 forks source link

No matter what port I use if it is not 8211 its ignored. #18

Closed P3rf3ctXZer0 closed 4 months ago

P3rf3ctXZer0 commented 4 months ago

I have reported this to devs but it seems like nothing can change default port.

P3rf3ctXZer0 commented 4 months ago

opera_4ynGdkTk7c 1

P3rf3ctXZer0 commented 4 months ago

AnyDesk_eye5yi05U8 1

Leayal commented 4 months ago

@P3rf3ctXZer0 According to Palworld Docs. You can try setting launch argument -port=<number>. For instance, -port=7777 should make the server use UDP port 7777.

legoduded commented 4 months ago

as @Leayal mentioned the -port launch argument should work. I believe the publicport value in the ini might be for the public port others should use to connect to your server when you're in the community server list. But I'm also just guessing

Leayal commented 4 months ago

as @Leayal mentioned the -port launch argument should work. I believe the publicport value in the ini might be for the public port others should use to connect to your server when you're in the community server list. But I'm also just guessing

My guess is the same, I think the values in the configuration is used to advertise server's address so that the in-game server browser can list your server properly.

P/s: I think this is regarding to some specific setups that a server uses different numbers for public port and private port (or internal port) in NAT configuration (or port forwarding configuration), which then you can make server bind to the private port number, while setting the .ini configuration to report your server should be connected via a different port number of the public IP.

P3rf3ctXZer0 commented 4 months ago

@P3rf3ctXZer0 According to Palworld Docs. You can try setting launch argument -port=<number>. For instance, -port=7777 should make the server use UDP port 7777.

This is the first thing I tried.

Leayal commented 4 months ago

This is the first thing I tried.

Can you try setting both -port and -publicport params (like image below)? I think the -port params should work as long as it's set properly.

You can check whether you've launched the server with params by looking at Task Manager's Command Line column in the Processes tab. In case you don't see the column:

P3rf3ctXZer0 commented 4 months ago

Yes but not now. I will pin this on to list. I have a lot going on. Also when people say launch argument how do you set a launch argument not running through steam? I get my palworld from steamcmd and launch directly the PalServer-Win64-Test-Cmd.exe directly.

Leayal commented 4 months ago

Yes but not now. I will pin this on to list. I have a lot going on. Also when people say launch argument how do you set a launch argument not running through steam? I get my palworld from steamcmd and launch directly the PalServer-Win64-Test-Cmd.exe directly.

First is that while you can launch PalServer-Win64-Test-Cmd.exe directly, launch the bootstrap PalServer.exe is much more recommended, for UE games.

To add "launch argument", you have two ways to get it done:

[^1]: The Target can contains the full path to .exe within double quotes ", if you have this case, append the launch argment AFTER the double quotes of the .exe's path. The space to split arguments is required in any cases. [^2]: The double quotes and the space are special characters: Arguments are separated by spaces. As long as a your one argument contains a space, they must be wrapped within the double quotes to to let Windows know that it is just one argument containing the space. This same rule applies to the .exe path (which leads to the note above). Notice I added a space after the .exe path (image above).

Happy playing, @P3rf3ctXZer0

P3rf3ctXZer0 commented 4 months ago

This worked - thank you <3