Fix missing variables in run.sh by escaping #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The variables
world_idandserver_portmeant to be in run.sh are evaluated as empty before being written to run.sh by both start.sh and Docker.sh. This means that when using run.sh to start the server, the values stored inworld_idandserver_portwere unused. Also, the server restart date was similarly evaluated during writing by start.sh, and would be stored in run.sh as the time the script was created.I've escaped them with a backslash (as was already done in Docker.sh for
$(date)), so the created file now contains the variables as intended. I've tested this on Ubuntu 25.04 and 24.04 using start.sh, and I've verified that the run.sh created by docker correctly contains the variables by temporarily addingcat run.shafter writing it in Docker.sh.