search

Aperture-Development / MSync-2

Version 2 of MSync - Fully working and extra steak
https://www.Aperture-Development.de
GNU General Public License v3.0
12 stars 1 forks source link

Rank storage & allservers group #38

Closed Bryantdl7 closed 4 years ago

Bryantdl7 commented 4 years ago

I have all my servers set to dstm-build currently, for the sake of testing before I adjust things.

In this state, I have two groups:

image

I thought maybe it just made two different groups, but then I looked at my mrsync table: image For the sake of consistency, I dropped myself out of the mrsync table, and the tbl_users, reconnected, and disconnected. I went back to being on the rank of owner, in group 1.

So it appears that ranks which are set up to go to any server are in the allservers category. Is allservers to be interpreted as the overall wildcard ranks between all servers, or the group the server is in?

Is there supposed to be two sets of groups? This might just be a documentation limitation causing this confusion, let me know.

ApertureDevelopment commented 4 years ago

Yes it is. The allservers group is for any data that is supposed to be the same on all servers. The possibility to change the Server_Group exists to allow server admins to seperate their servers into multible teams, while maintaining the same database. The "allservers" group exists to tell the plugin that the data is supposed to be not server_group specific, but on all servers.

A simelar system is used by a Minecraft plugin called "LuckPerms" they call it server-context https://github.com/lucko/LuckPerms/wiki/Context#contexts-provided-by-luckperms

I am still working on writing the MSync wiki, but that explaination on their wiki should explain my intention behind the server_group

Bryantdl7 commented 4 years ago

Got it. You might want to copy what you just said and put it in the wiki with a title as a general overview for now, that explains it enough so people understand going forward.