René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Permissions Registry \u0026 Support for Vanilla's OP System","articleBody":"Through discussion in previous months on the discord, I think(?) the idea of supporting Bukkit-style permissions natively. We must, of course, additionally support the Vanilla-style OP system since it is actually weirdly a part of the protocol. This issue outlines our steps forward in implementing this feature, considerations, and future steps to complete it.\r\n\r\n## Now\r\nOur priority is to get something we can build on later, and this suits that need pretty well. The process of updating it shouldn't change much in existing usage of the permissions registry, which is a good sign that this path forward is the one to take.\r\n\r\nThe permissions system will involve two main parts:\r\n- The permissions registry which holds all information from the `perms.json` file after load-time (at the beginning of the server's execution or after some form of reload command). This is just a cache of the file on the disk already loaded into structures that will allow for easy querying.\r\n- The component that is attached to all `Player` entities that stores their permissions.\r\n\r\nAdditionally, something similar to these types will be used to store permissions:\r\n```rs\r\npub struct VanillaPermissions {\r\n    /// The OP level\r\n    level: u8,\r\n    /// Whether the player bypasses player count limits\r\n    bypasses_player_limit: bool\r\n}\r\n```\r\n\r\nHaven't figured out how to name this struct though\r\n```rs\r\npub struct FooPermissions {\r\n    /// A map of permission keys to values\r\n    permissions: HashMap\u003cString, String\u003e\r\n}\r\n```\r\n\r\nThis is the struct that will be used as a component.\r\n```rs\r\npub struct PlayerPermissions {\r\n    vanilla_permissions: VanillaPermissions,\r\n    foo_permissions: FooPermissions\r\n}\r\n```\r\n\r\nThere needs to be chaperone types to serde the permissions, but that's straightforward. \r\n\r\n\r\nThe registry type can be whatever works, probably something like a `HashMap\u003cUuid, CombinedPermissionsStorage\u003e`.\r\n\r\n\r\nIt's important to maintain compat, so OP level should be saved to the `ops.json` file.\r\n\r\n\r\nThe op level should have a magic key `minecraft.opLevel` or similar that causes it to be written into the vanilla permissions instead of the bukkit-style system.\r\n\r\n### **For now, permissions should be able to be queried, added, loaded on server load, saved on player leave (at a minimum)**\r\n\r\n## Soon\r\nThe things described in this part of the issue are things we need to do soon, but aren't requirements (nor should they be added) for the first implementation of the system.\r\n\r\nHigher priority:\r\n- [ ] **Typed permission values**\r\n- [ ] **Quill support for permissions**\r\n\r\nLower priority:\r\n- [ ] Commands to query permissions information\r\n- [ ] Utility trait to make querying permissions easier","author":{"url":"https://github.com/ambeeeeee","@type":"Person","name":"ambeeeeee"},"datePublished":"2021-09-25T11:00:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/484/feather/issues/484"}