Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect time unit in AUTO_SAVE_SPAN description #586

Closed
4 tasks
MusclePr opened this issue Jul 25, 2024 · 0 comments · Fixed by #589
Closed
4 tasks

Incorrect time unit in AUTO_SAVE_SPAN description #586

MusclePr opened this issue Jul 25, 2024 · 0 comments · Fixed by #589
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@MusclePr
Copy link
Contributor

Describe the bug

Incorrect time unit in AUTO_SAVE_SPAN description.
x: Time between autosaves (minutes)
o: Time between autosaves (seconds)

To Reproduce

Steps to reproduce the behavior:

  1. AUTO_SAVE_SPAN=30
  2. Check the timestamp frequency of Pal/Saved/SaveGames/0/*/Level.sav.
  3. AUTO_SAVE_SPAN=60
  4. Check the timestamp frequency of Pal/Saved/SaveGames/0/*/Level.sav.

Expected behavior

AUTO_SAVE_SPAN=30 is 30 miniuites frequency by README documents.

Actual behavior

AUTO_SAVE_SPAN=30 is 30 seconds frequency.

Screenshots

nothing.

OS information (IMPORTANT)

  • OS: Debian 12.5
  • Palworld Version: 0.3.3.55731
  • Docker Image Version: 0.38.2

Hardware information (IMPORTANT)

  • CPU: INTEL Core i-9 13900K
  • Memory: 192GB DDR-5

docker-compose.yml contents (IMPORTANT)

docker-compose.yml
services:
  pal:
    container_name: pal
    image: thijsvanloef/palworld-server-docker:latest
    restart: no
    stop_grace_period: 30s
    tty: true
    ports:
      - "8211:8211/udp"
    volumes:
      - ./palworld:/palworld/
    environment:
      REST_API_ENABLED: true
      AUTO_SAVE_SPAN: 30

Container/Host Logs (IMPORTANT)

Logs
****EXECUTING USERMOD****
usermod: no changes
****Checking for new Palworld Server updates****
Current Version: 8939748203712584968
The server is up to date!
****Checking for available container updates****
The container is up to date!
****GENERATING CONFIG****
Using Env vars to create PalWorldSettings.ini
****Compiling PalWorldSettings.ini****
Compiling PalWorldSettings.ini done!
****GENERATING CRONTAB****
No Cronjobs found
****Starting Server****
./PalServer.sh -port=8211 -queryport=27015
The file already exists: /palworld/Pal/Binaries/Linux/steamclient.so
Shutdown handler: initalize.
5.1.1-0+++UE5+Release-5.1 1008 0
Disabling core dumps.
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
Setting breakpad minidump AppID = 2394010
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
Game version is v0.3.3.55731
REST API started on port 8212
Waiting for REST API(8212) port to open to show player logging...

Additional context

Bug Report Checklist

  • I searched for my issue on the Known issues page
  • I searched for my issue in the Closed issues
  • I have included all relevant information required above.
  • I am willing to fix this bug
@MusclePr MusclePr added the triage Deciding urgency label Jul 25, 2024
@thijsvanloef thijsvanloef added bug Something isn't working documentation Improvements or additions to documentation and removed triage Deciding urgency labels Aug 4, 2024
@thijsvanloef thijsvanloef linked a pull request Aug 4, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants