Jonathan Coates b3738a7a63 Use permission APIs for the /computercraft command ... - Add a generic PermissionRegistry interface. This behaves similarly to our ShaderMod interface, searching all providers until it finds a compatible one. We could just make this part of the platform code instead, but this allows us to support multiple systems on Fabric, where things are less standardised. This interface behaves like a registry, rather than a straight `getPermission(node, player)` method, as Forge requires us to list our nodes up-front. - Add Forge (using the built-in system) and Fabric (using fabric-permissions-api) implementations of the above interface. - Register permission nodes for our commands, and use those instead. This does mean that the permissions check for the root /computercraft command now requires enumerating all child commands (and so potential does 7 permission lookups), but hopefully this isn't too bad in practice. - Remove UserLevel.OWNER - we never used this anywhere, and I can't imagine we'll want to in the future.		2023-08-27 12:22:40 +01:00
..
wrapper	Update to Gradle 8.x	2023-06-29 20:10:17 +01:00
libs.versions.toml	Use permission APIs for the /computercraft command	2023-08-27 12:22:40 +01:00