11-28-2016, 05:29 AM
I don't think there's an urge to get rid of the webadmin. It serves its purpose as an administration tool (except when it gets on the way of adopting YAML as standard config files
).
It also doesn't need to be fully rewritten as a "real" plugin, I think it can live as a "special snow flake" just fine. It would look and act as a plugin anyway still.
As for logins, permissions and such, it could be done this way: settings.ini holds the "root" account (could still be called admin), additional users would be identified by their in-game nicknames, credentials would then be handled by something like the Login plugin, permissions would be handled by the Core permissions system.
Without these plugins everyone would be considered a guest (unlogged in group) user unless they have the root password. So permissions and account management are completely optional.
Looks work-able for me, and mostly not over the top.
). It also doesn't need to be fully rewritten as a "real" plugin, I think it can live as a "special snow flake" just fine. It would look and act as a plugin anyway still.
As for logins, permissions and such, it could be done this way: settings.ini holds the "root" account (could still be called admin), additional users would be identified by their in-game nicknames, credentials would then be handled by something like the Login plugin, permissions would be handled by the Core permissions system.
Without these plugins everyone would be considered a guest (unlogged in group) user unless they have the root password. So permissions and account management are completely optional.
Looks work-able for me, and mostly not over the top.