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

[REQUEST] Multiple config files #22

Closed
SirFancyBacon opened this issue May 14, 2019 · 1 comment · Fixed by #26
Closed

[REQUEST] Multiple config files #22

SirFancyBacon opened this issue May 14, 2019 · 1 comment · Fixed by #26

Comments

@SirFancyBacon
Copy link
Contributor

SirFancyBacon commented May 14, 2019

Would it be possible to add a folder called "items" and within that folder any .conf file can be loaded per usual? the same limitations of only allowing one ID to be allocated would apply across all configs.
for example inside of weapons.conf if you had an item with an ID of 11, you could not also have an item with an ID of 11 within armor.conf

It would make managing configs with a lot of items much easier.

My config along has over 50 items in it, and it's annoying to find things 😉

If the same could apply to Pools that also would be amazing!

@obr-09
Copy link
Member

obr-09 commented Jul 18, 2020

Hello @hellbringer616 ,
Sorry the Pull Request stayed idle for so long, we now support multiple config files in Itemizer, starting with version 3.7.0.
I had an issue with the bintray release system, so I uploaded it as a Github release here.
You can now create folders instead of conf files (match the exact name without the ".conf" extension) and every configuration files within it will be read. I put a max recursion of 3 folders, so you can add subfolders too.

Don't hesitate to get in touch with me or Spook if you encounter any issue.

Side note with the /register command; it does not handle the multiple config files, so when registering an item it will put it in the items.conf file with every other existing items. It does not break the multi-file system though, but sorry for the inconvenience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants