[SUGGESTION] CreateKit Command
nandox5 opened this issue · 5 comments
For /createkit
so that the config comments dont get removed, why not move the kits to a kits.yml file
and have essentials read the kits from the kits.yml
Because that would break everyone's current setup. Though I do agree that the current config file is wayyyyy too big.
You could make the kits.yml thing use a config option and set that config option to false by default. That way, it wouldn't break any setups and it'd be optional
-----Original Message-----
From: "Trent Hensler" [email protected]
Sent: 22/02/2016 02:29 AM
To: "drtshock/Essentials" [email protected]
Subject: Re: [Essentials] [SUGGESTION] CreateKit Command (#430)
Because that would break everyone's current setup. Though I do agree that the current config file is wayyyyy too big.
—
Reply to this email directly or view it on GitHub.
and it probably would be an easy copy and paste fix from the current config to the kits.yml as long as the structure is kept the same (i dont see why it would change anyways)..
I think this is a larger issue of redoing the entire config setup instead of just looking at kits.
