9 minutes ago, Flosstradamus said:

Anyway you can add Enshrouded to the list of game servers as well? Would be much appreciated

Please look at this post:

 

18 minutes ago, looped said:

Are there any examples of how to use bepinex with stationeers docker?

This is not possible in my container.

22 minutes ago, threadbare-node5157 said:

Has anyone managed to get their Palworld server to appear in the community server list? Mine is up, and people can connect and everything, but I'm not sure how to get it to be listed in the game...

You should look into the server status fist, they are experiencing massive problems currently:

Can anyone help me how to install mods on a Core Keeper server?

10 minutes ago, ich777 said:

Please look at this post:

 

Ah no worries I understand. Hopefully someone else can add it into the CA app and maintain it properly. If I had any clue on how you're able to do it i'd try to tackle it myself ha

1 minute ago, Flosstradamus said:

Ah no worries I understand. Hopefully someone else can add it into the CA app and maintain it properly. If I had any clue on how you're able to do it i'd try to tackle it myself ha

There is already a support thread there but it has not been added yet to CA:

 

18 minutes ago, ich777 said:

This is not possible in my container.

ok thanks.. Bummer

Is there a way to limit the memory allowed for Pal World and are there community recommendations for amount?

Edited January 25, 20242 yr by Glorithan
Spelling

39 minutes ago, Glorithan said:

Is there a way to limit the memory allowed for Pal World and are there community recommendations for amount?

Yes, but if you limit the RAM then the container will crash and restart, this could lead to a corrupt save file...

I have it currently limited to 40GB but the highest that I've seen so far with 9 concurrent players was 21GB

1 hour ago, looped said:

ok thanks.. Bummer

Sorry, but I don't support modding anymore, I only support basic functionality.

Any ideas on how to get the Palworld Docker to update to 1.3?  I've restarted it a few times, but still says the server version is different than the client. 

1 hour ago, ich777 said:

You should look into the server status fist, they are experiencing massive problems currently:

I still get the feeling that this docker isn't properly reading the PalWorldSettings.ini
The server is ignoring the parameters like server name and admin password.
Also, even if i insert an public ip in the ini file. The docker log shows, the public ip is missing and looks up an public ip.
It does so even if you set it in the env parameter to not look for an public ip.
Is this some selfwritten script or from the game developers?

Am i the only one with this issue?

 

The connection to the game server works with the public ip and dns too.

But i see in my history the default server name und i can join without a passwort, even when set.

 

Success! App '2394010' already up to date.
---Checking if configuration is in place---
---Configuration found, continuing...---
---Checking if PublicIP is in place---
---No PublicIP found in PalWorldSettings.ini, trying to obtain it...---
---Sucessfully obtained PublicIP: xx.xxx.xxx.xxx, adding to PalWorldSettings.ini
---Prepare Server---
 

Edited January 25, 20242 yr by varona
New Question + typo fix

3 minutes ago, varona said:

I still get the feeling that this docker isn't properly reading the PalWorldSettings.ini
The server is ignoring the parameters like server name and admin password.
Also, even if i insert an public ip in the ini file. The docker log shows, the public ip is missing and looks up an public ip.
It does so even if you say in the env parameter to not look for an public ip.
Is this some selfwritten script or from the game developers?

Am i the only one with this issue?

 

The connection to the game server works with the public ip and dns too.

But i see in my history the default server name und i can join without a passwort, even when set.

 

Success! App '2394010' already up to date.
---Checking if configuration is in place---
---Configuration found, continuing...---
---Checking if PublicIP is in place---
---No PublicIP found in PalWorldSettings.ini, trying to obtain it...---
---Sucessfully obtained PublicIP: xx.xxx.xxx.xxx, adding to PalWorldSettings.ini
---Prepare Server---
 

you are editing the ini from the Save folder, while the container is off?

Good afternoon, UnRaid Gamers, 

 

I am attempting to setup my Palworld server on my unraid setup. I am able to connect to the server via my localipaddress:8211 but when attempting to connect to the server via publicipaddress which is confirmed in the logs and whatismyip. I have gone through and made sure t hat the docker is using 8211 and setup port forwarding. I will provide pics for context. 

 

For additional context I do have plex setup and I am able to connect to my server remotely. 

4 minutes ago, nubbz1992 said:

Good afternoon, UnRaid Gamers, 

 

I am attempting to setup my Palworld server on my unraid setup. I am able to connect to the server via my localipaddress:8211 but when attempting to connect to the server via publicipaddress which is confirmed in the logs and whatismyip. I have gone through and made sure t hat the docker is using 8211 and setup port forwarding. I will provide pics for context. 

 

For additional context I do have plex setup and I am able to connect to my server remotely. 

Odd, this config looks like it should work. Maybe try setting the router to only accept UDP instead of both UDP and TCP. I couldn't imagine that would matter... but maybe??

OK, my turn... I have updated (and force updated) my Palworld server, enabled VALIDATE (and re-disabled it after saving) and yet my server is still showing 0.1.2.0.

 

Is there a way, from within the docker console, to see the Palworld version?:

 

Here is the log information on startup. Server has been stable since day 1.

21 minutes ago, wes.crockett said:

Odd, this config looks like it should work. Maybe try setting the router to only accept UDP instead of both UDP and TCP. I couldn't imagine that would matter... but maybe??

I have tried both. and followed a few different sites. https://hub.tcno.co/games/palworld/dedicated_server/ and https://tice.tips/gaming/palworld-port-forward/ the one thing i can't do is below powershell in unraid but it shouldn't matter. 

netsh advfirewall firewall add rule name="Palworld Port 27015" dir=in action=allow protocol=UDP localport=27015
netsh advfirewall firewall add rule name="Palworld Port 8211" dir=in action=allow protocol=UDP localport=8211

PalWorldSettings.ini where it has PublicIP="" should i key it as PublicIP=127.0.0.1 (except with my actual ip) Also, is there a thing in the ini that I need to setup so it is setup to be a publicip server for my friends to connect to?

 

Edited January 25, 20242 yr by nubbz1992

1 hour ago, dkersten said:

Any ideas on how to get the Palworld Docker to update to 1.3?  I've restarted it a few times, but still says the server version is different than the client. 

Please read this and the quoted post:

 

 

For me the update went just fine...

yes, put in your actual. be sure to stop the container, change the setting, then bring it back up.

In the container config, did you tell it to auto-update public IP? If not, do so.

46 minutes ago, varona said:

I still get the feeling that this docker isn't properly reading the PalWorldSettings.ini

Please read this post and also the linked post in there:

 

I do have it flagged as true for update public ip

21 minutes ago, wes.crockett said:

OK, my turn... I have updated (and force updated) my Palworld server, enabled VALIDATE (and re-disabled it after saving) and yet my server is still showing 0.1.2.0.

This can't work, you added Steam credentials, remove them and start over.

 

BTW are you the root user from Steam?

29 minutes ago, nubbz1992 said:

I am attempting to setup my Palworld server on my unraid setup. I am able to connect to the server via my localipaddress:8211 but when attempting to connect to the server via publicipaddress which is confirmed in the logs and whatismyip. I have gone through and made sure t hat the docker is using 8211 and setup port forwarding. I will provide pics for context. 

What's most likely is the cause of your issue is that your Hair Pin NAT is not working correctly.

Have you yet tried to connect to the container from outside your LAN with your public IP?

33 minutes ago, nubbz1992 said:

Also read this post:

 

3 minutes ago, ich777 said:

What's most likely is the cause of your issue is that your Hair Pin NAT is not working correctly.

Have you yet tried to connect to the container from outside your LAN with your public IP?

 I will be honest I am looking into Hair Pin NAT and I am not sure I know this process. I have an Asus GT6 on stock OS. I have not been able to connect to the container from outside my lan since I am a homebody. I have been able to confirm that my plex server is working.