Closed githubnemo closed 11 years ago
Thanks a lot !
I think you should manage the 'train' option, like 'mego' does.
In fact I planned to remove bcticket as, as you said, it was not useful since 'mego' or 'sendto' did the job, but the support for command block was missing.
Maybe 'mego address [train]' should be an alias for 'bcticket player address [train]' and bcticket will contain all the code with train option support.
Another point is that "Usage" explanation is set in permissions.yml, so you just have to return false if args do not match and Usage will be displayed. No need to display error strings in this case.
I will probably do that in a few days.
The bcticket
command now supports the train
parameter and the usage is fetched from plugin.yml
by returning false
in the bcticket
method.
I thought it would be a good idea to isolate the bcticket
command in its own method.
The only thing missing now is the refactoring of mego
and sendto
.
Thank you !
Also fix bcticket in general as it didn't had any parameters or did something useful.
New syntax for bcticket:
or (for command blocks):