Closed P3rf3ctXZer0 closed 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.
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
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 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.
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:
Processes
tab and it will show a menu for you to select/deselect a column from the view.Processes
tab and select Select column
in the menu. After that, pick any columns you want to show and select OK
.
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.
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:
Via a shortcut file:
.exe
file, select Create shortcut
(In case you're on Win11, you need to Show All Items
in the first right-click menu). A shortcut .lnk
file will be created in the same folder of the .exe
.Properties
.Shortcut
tab of the Properties
dialog, you will see Target
input box. Adding launch arguments/params by appending the said arguments to the Target
input box. (image below). Please read both footnotes for additional information[^1][^2].
OK
to save and close the dialog.Via command-line: (you can also write a batch script, too). Please note that command's syntax has the same rule in the second footnote[^2].
Command-line Prompt
program (search for cmd.exe
in the Start Menu if you don't know where it is).cd /d <path to the directory containing .exe>
. (E.g: cd /d I:\Servers\palworld\server
)PalServer.exe -port=<port number>
. (E.g: PalServer.exe -port=6969
).
start "" PalServer.exe -port=<port number>
. (E.g: start "" PalServer.exe -port=6969
), by doing this, you allow your Command-prompt
to continue without having to wait for PalServer.exe
's exiting.start
command in the alternative method above as you can safely close the cmd without worries in this case.[^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
This worked - thank you <3
I have reported this to devs but it seems like nothing can change default port.