Separating admin and config commands? #520
Replies: 6 comments 2 replies
-
Added to |
Beta Was this translation helpful? Give feedback.
-
I'm all for this idea (in fact I started doing it tonight as I was bored) but I think there is still a need for a |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Currently possible with |
Beta Was this translation helpful? Give feedback.
-
For example |
Beta Was this translation helpful? Give feedback.
-
Awesome! I love the admin commands that have been added so far, I've already used quite a few of them |
Beta Was this translation helpful? Give feedback.
-
So currently we have
/tardisadmin
(or/tadmin
as I'll call it) to handle all administrative functions of the plugin. Having config values and admin commands under the same command can be really confusing. For example, for a new admin it may be ambiguous whether/tadmin enter
changes an option related to TARDIS entry or enters a player's TARDIS. (Even if for us it seems obvious that it's the latter)Would it be feasible to separate these out into two separate commands,
/tadmin
and/tconfig
? I'd be open to creating a PR for this, but that's not a light task so I wanted to gauge how well the idea would be received first. It'd be very useful to have more admin commands, but adding these alongside the configuration commands only increases complexity.On the topic of more admin commands, I see this was talked about in #307, but the
tardissudo
command honestly seems like a pretty clunky way of controlling other players' TARDISes. It would probably be easier for server admins to have a collection of utilities to help players, like:If there are enough useful admin commands, then we shouldn't need tardissudo.
Beta Was this translation helpful? Give feedback.
All reactions