-
-
Notifications
You must be signed in to change notification settings - Fork 303
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
Most recent PR merge is ignoring env vars #212
Comments
Related to #210 |
If you are able to please share the contents of your PalWorldSettings.ini. |
You've done an amazing job with this container but it's now not working for my friends and I as well. Unfortunately the configuration is not loading after #203 which we thought was caused by us! :D Here's an almost exact copy of my config (using Docker Swarm) which was working before #203:
Thanks again, sorry this happened, hope to be able to play tonight. |
I've already reverted to v0.18 which is working no special characters in server name or password. just simple single-word strings |
Please make sure that the Env variable values are quoted in the docker compose |
@NobleKangaroo If you do not quote your names/discription the following happens: ServerName="World of Pals",ServerDescription=Pikachu, I choose you!,AdminPassword="adminPasswordHere", Which invalidates the PalWorldSettings.ini |
See #222 |
Hi there, i can confirm the problem on my server. env variables are not applied. It appends with 0.19 update. I don't have specials characters in server name or password. I revert to 0.18 and it's working with same variables. EDIT: I made more tests, and i can see the starting log of the container are different between 0.18 and 0.19 (added at bottom). I don't know if it's important but there is a "unkown char" in the log after "CHECKING FOR EXISTING CONFIG", it displays "�" and in notepad++ it's SOH" Here is my Compose and PalWorldSettings.ini file if it can help.
0.18
0.19
|
Problem should be resolved in update 0.19.1 thanks to |
Awesome work on the docker. V0.18 is fantastic. Regarding this issue: I had the same issue on v0.19, I rolled back to v0.18 and it was working. I just tested updating to 0.19.1 and it's still setting default options. |
@PulsarFTW I've also change the docker-compose.yml example, could you try that with 0.19.1 |
If you are still having trouble after updating, please remove your PalWorldSettings.ini and restart your container. |
I had changed the PAL_EGG_DEFAULT_HATCHING_TIME and some other env vars and now I restarted the container and the hatching time is infinite (99 hours +++) and the worktime multiplier is also infinite, can't craft anything anymore. I reverted the changes, tried 0.18, 0.19, 0.19.1 restarted the container, deleted the default settings .ini but nothing helped so far. Is the server backup bugged for good now? //edit: okay so I made the mistake to use quotes around some of the env vars and now the |
I don't know how but when NOT quoting the settings, the server is operating fine and the server name and description are good but when quoting them, the server name appears as the first word with a quote at the beginning. For instance if I set As you mention, though, the PalWorldSettings.ini do look like this:
Specifically of note is the bit ServerPlayerMaxNum=20, HOWEVER that's still working and the name and description in-game are displaying as intended as well as the password is working and the player count is working. I don't know if there's some case where having a space would invalidate the ini but at least in my scenario, it appears that's not happening and in fact, quotes are causing issues. |
@NobleKangaroo are you sure you are on the latest image? The bug you are describing "only the first word with a quote" sounds like 0.18.0 |
@lrobles-iterable are you still experiencing this issue with 0.19.1? |
Closing this issue to merge all related issues into one: #239 |
Yes this was on 0.18.0. Thanks for confirming that. I'll give |
Describe the bug
After the most recent PR merge #203, settings in Palworldsettings.ini are being ignored.
Things such as server name, server password are not being set after removing them from the startup command
To Reproduce
Steps to reproduce the behavior:
Expected behavior
EITHER options that were previously added to the startup line should be set, or allow us to set our own startup command options
Screenshots
My env vars being set, but the server is named "Default palworld server" and no password is set
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)
docker-compose.yml contents
Container/Host Logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: