Replies: 1 comment
-
Another thing I thought of while doing some web dev, it's how good is the migrations system on Laravel. That would be cool too. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some of you know that I don't have enough time to properly contribute to the project, so most of what I can do is to offer my opinions and quick fixes. Now, given that we are in the early stage of v2.0, there are some things I would like to see implemented for v3.0.
1. A proper ModuleManager class
If you think about modules being one of the main distinguisheable features of AzerothCore, it comes to my mind how is it that it doesn't implement a ModuleManager class.
I see it as a class that can list installed modules, showing which are enabled, the version and author. It could enable/disable modules too, modifying in-memory config. All through commands for admins.
This idea would require a new hook for modules so they forcefully have to register with the Manager and updating all the modules so they implement this new hook and a "enabled" config.
2. An evolution of the RBAC adapted to modules
A thing that we have talked about in the past is how the RBAC system (permissions) implemented by TrinityCore IS NOT what AzerothCore needs, as it doesn't address the issue of modules having to add new permissions without conflicting with other modules.
My ideal system would be something like the one implemented by Minecraft servers (CraftBukkit, Spigot) where permissions are strings composed by dot-separated nodes, like "core.accounts.modify".
More on this:
3. Statistics!
I know everyone hates these "send data about usage to XXXX" options that comes with newer software nowadays, but seeing it from an analytical point of view it really helps to understand how is people (devs, admins, commoners) using our project and which are most common modules. (Hello data science?)
The idea would be an "opt-in" data reporting, so we can gather it somewhere and do analysis over it, obviously as an open source dataset with anonymous origin.
So that's it, three things I would love to see in AzerothCore, but sadly I can't do myself (too busy with family, work, own server). 😢
C'mon guys, this is your opportunity as a dev to learn new things and keep growing! 🤣
Beta Was this translation helpful? Give feedback.
All reactions