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

Fixes #1235 (ark) #1236

Closed
wants to merge 4 commits into from
Closed

Fixes #1235 (ark) #1236

wants to merge 4 commits into from

Conversation

UltimateByte
Copy link
Contributor

@UltimateByte UltimateByte commented Jan 10, 2017

Fixes #1235

Ark had no config file out of the box because its directory didn't exist. Because of that, it wouldn't work out of the box.
Also, LGSM tried to alter config file even if it didn't exist. It's solved by an simple if -f check.

Working on this, I noticed another issue. Let's quote myself:

Admin password and servername are present into Ark but set within start parameters, so their edition by LGSM is pointless since they will be reset upon server shutdown into the config file, taking start parms values.

So I just removed fn_set_config_vars for Ark.

Ultimately, I have some concerns that need to be checked about Ark's default config file:
Port values might need to be removed from default config file since they are ignored and start parameters are used instead,. On top of that, those are not changed within the config file upon server shutdown to match start parameters, so in the end, if they're not used, they can be misleading. Somebody should test without them into the config file and see if it still works as intended. My guess is it does work perfectly.

Admin password and servername are present into Ark but set within start parameters, so their edition by LGSM is pointless since they will be reset upon server shutdown into the config file, taking start parms values.
Port values might need to be removed from default config file since they are ignored and start parameters are used instead,. On top of that, those are not changed upon server shutdown to match start parameters, so in the end, if they're not used, they can be misleading.
@dgibbs64 dgibbs64 changed the base branch from master to develop January 10, 2017 18:16
Copy link
Member

@dgibbs64 dgibbs64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we should have to option to mkdir the missing save directory if not there. This will mean the download of the config will not be prevented.

Also I saw that servername and rconpassword (which should be adminpassword) are being set in two places. It shoudl be set in the config rather than the parms. Unless there is a specific reason why its set in parms.

Finally please can you amend your branches to be called feature/ultimatebyte-XXX for branches that are only for develop branch and hotfix/ultimatebyte-XXX for urgent fixes (should be rare). This allows me to easily manage "git flow"

@UltimateByte
Copy link
Contributor Author

OK, relevant remarks, I'll remind them and make another PR.

@UltimateByte UltimateByte deleted the ultimatebyte-hotfix branch January 14, 2017 17:42
@UltimateByte UltimateByte changed the title Fixes #1235 Fixes #1235 (ark) Jan 15, 2017
@lock
Copy link

lock bot commented Jul 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants