Suggestion
For mad commands, we should be able to create a "file". If we had near 30 commands for, let's say, a SkyWars command, we should be able to make a "file" called "SkyWars Commands" so that when we do /cmd list we can only see half of our commands because we have so many @.@.
Commands in it - /cmd file new File Name
- /cmd file add File Name Command Name
- /cmd file delete/cancel File Name [save/remove] (<--- Saves commands in file or gets rid of them)
- /cmd file edit File Name [args]
- /cmd file merge File 1 File 2 (All file 2 commands would be put into file 1 commands with the file 1 name)
Thoughts anyone? I think this would be a great idea. Just @ me if you have any questions as to how it would function, or ideas, etc.
Thanks for your time,
~Sharks
For mad commands, we should be able to create a "file". If we had near 30 commands for, let's say, a SkyWars command, we should be able to make a "file" called "SkyWars Commands" so that when we do /cmd list we can only see half of our commands because we have so many @.@.
Commands in it - /cmd file new File Name
- /cmd file add File Name Command Name
- /cmd file delete/cancel File Name [save/remove] (<--- Saves commands in file or gets rid of them)
- /cmd file edit File Name [args]
- /cmd file merge File 1 File 2 (All file 2 commands would be put into file 1 commands with the file 1 name)
Thoughts anyone? I think this would be a great idea. Just @ me if you have any questions as to how it would function, or ideas, etc.
Thanks for your time,
~Sharks