Skip to content
New issue

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

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

Already on GitHub? # to your account

Changed kits.cfg -> PluginConfigs/SignCommandKits.json #1

Merged
merged 1 commit into from
Feb 25, 2012

Conversation

stevenh
Copy link
Contributor

@stevenh stevenh commented Feb 22, 2012

This matches how the core config is done and prevents conflict with other plugins which may use kits.cfg which is pretty generic :)

@Scavenger3
Copy link
Owner

Hmm, The reason I didnt make a separate kits file is so that if you were using the kits plugin, you could have them both work to gether, and you didnt have to copy and paste the file if you wanted to change a kit.

However I guess this would probably be better.

@stevenh
Copy link
Contributor Author

stevenh commented Feb 23, 2012

You could always have add command to "import" the kits plugin config. This would also allow you to do any alterations that may be needed to make them compatible, if either end added additional features or changed the format.

Scavenger3 added a commit that referenced this pull request Feb 25, 2012
Changed kits.cfg -> PluginConfigs/SignCommandKits.json
@Scavenger3 Scavenger3 merged commit d22c29a into Scavenger3:master Feb 25, 2012
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants