Skip to content

fix(ts3server): correct ts3server config file name in comment#2200

Merged
dgibbs64 merged 1 commit intoGameServerManagers:developfrom
borzaka:patch-1
Feb 22, 2019
Merged

fix(ts3server): correct ts3server config file name in comment#2200
dgibbs64 merged 1 commit intoGameServerManagers:developfrom
borzaka:patch-1

Conversation

@borzaka
Copy link
Copy Markdown
Contributor

@borzaka borzaka commented Feb 19, 2019

Description

It's ts3server.ini, not ts3-server.ini
It's only in the comment, not in actual code.

Type of change

  • Bug fix (change which fixes an issue)
  • New feature (change which adds functionality)
  • New Server (new server added)
  • Refactor (restructures existing code)
  • This change requires a documentation update

Checklist

  • My code follows the style guidelines of this project
  • This pull request links to an issue
  • This pull request uses the develop branch as its base
  • I have performed a self-review of my own code
  • I have squashed commits
  • I have commented my code, particularly in hard to understand areas
  • I have made corresponding changes to the documentation if required

It's ts3server.ini, not ts3-server.ini
@ghost ghost added the status: triage label Feb 19, 2019
@borzaka borzaka changed the title Correct ts3server config file name Correct ts3server config file name in comment Feb 20, 2019
@dgibbs64 dgibbs64 changed the title Correct ts3server config file name in comment fix(ts3serveR): correct ts3server config file name in comment Feb 22, 2019
@dgibbs64 dgibbs64 changed the title fix(ts3serveR): correct ts3server config file name in comment fix(ts3server): correct ts3server config file name in comment Feb 22, 2019
@dgibbs64 dgibbs64 merged commit 0ef3dac into GameServerManagers:develop Feb 22, 2019
@ghost ghost removed the status: triage label Feb 22, 2019
@borzaka borzaka deleted the patch-1 branch February 22, 2019 22:23
@lock
Copy link
Copy Markdown

lock Bot commented Feb 23, 2020

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 and limited conversation to collaborators Feb 23, 2020
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