[DONE] Groups and permissions refactor - Printable Version +- Cuberite Forum (https://forum.cuberite.org) +-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html) +--- Forum: Development (https://forum.cuberite.org/forum-13.html) +--- Thread: [DONE] Groups and permissions refactor (/thread-1540.html) |
RE: Groups and permissions refactor - xoft - 08-04-2014 If you separate permission groups from the groups, there's nothing left in the groups. The prefix, postfix and color would be tied to the rank, not to a group. RE: Groups and permissions refactor - AntherusCraft - 08-04-2014 I mean there would be 2 groups, the permission-group and the rank iteself. So you can list permission-groups instead of extending another rank, that was my point. I'm still confused because of the "Player:" thing... Wouldn't it be easier to just make 2 lists like so: http://pastebin.com/rqFL1AX6 ? RE: Groups and permissions refactor - xoft - 08-04-2014 What you're calling groups will be ranks in the new system. The "player <-> rank <-> permissiongroups[]" has nothing to do with the config files, it is how the relations will be represented inside MCS: each player will be assigned to a single rank, and each rank will have several permissiongroups assigned to it. Nothing more. The actual configuration will be in a database, probably four tables: PlayerRanks: - PlayerUUID - PlayerName - RankName (links with a Ranks record) Ranks: - RankName - Prefix, Postfix, etc. PermissionGroups: - GroupName - RankName (links with a Ranks record) PermissionItem: - GroupName (links with a PermissionGroups record) - Permission RE: Groups and permissions refactor - AntherusCraft - 08-04-2014 Okay, i get it now, looking forward to it But i still think there should be also commands to manage them... RE: Groups and permissions refactor - xoft - 08-04-2014 Yes, those will need to be provided through Core, though. RE: Groups and permissions refactor - xoft - 08-04-2014 I guess the most important question for a server admin is: is it okay to put the configuration into a DB, where it isn't really editable from the outside? You will need to use the in-game commands, the server console or the WebAdmin to edit the permissions and everything. RE: Groups and permissions refactor - NiLSPACE - 08-04-2014 I think the WebAdmin alone should suffice for the configuration, but giving players ranks should be done in both WebAdmin and (in-game) commands. RE: Groups and permissions refactor - bearbin - 08-04-2014 I'd say a DB is fine, as long as the tools for editing are very good, and the database doesn't suddenly end up corrupted and unusable. (the main problems with database-based systems) RE: Groups and permissions refactor - AntherusCraft - 08-04-2014 Yeah i think the WebAdmin would be okay too, command would be confusing for most Players. If you are an Admin/Owner of a Server you should definetly have acces to the WebAdmin. Using a database is the best solution too, because for those Server who are planning on doing multiple servers (like 90% of the Servers today) it would be easier to have access to the ranks from every single Server. RE: Groups and permissions refactor - archshift - 08-05-2014 You can also manage DBs with outside software, so that's not that much of a problem IMO |