mirror of
https://github.com/PHIDIAS0303/ExpCluster.git
synced 2026-09-21 17:04:00 +00:00
bbassieandClaude Fable 5
eb715cc176
With the lua side checking permission names directly there is no transform to derive them from, so each permission is listed with its name. This was also the chance to drop the legacy action and flag buckets, which only reflected how the old config was written: - exp_scenario.bypass.* for entity protection, nuke protection, the deconstruction log, and reports. - exp_scenario.decon.* for the two deconstruction levels, with descriptions which say what they gate. - exp_scenario.player.* for admin, spectator, instant respawn, and system commands. - exp_scenario.chat.commands, and exp_scenario.gui.player_list.kick and .ban for the player list buttons which were never commands. Commands derive their permission as exp_scenario.command.<name>, so assign-role, unassign-role, and get-roles get scenario permissions rather than the core ones they mapped to before. The in game command is bounded by the lower role check, while core.user.update_roles is not, so granting it to moderators would have let them change any role from the web ui. Dropped: defer_role_changes, which priority replaced; command/give-warning, which no role held and the player list now checks create_warning for; and command/report, which was never defined. clear-tag/always is renamed to tag_clear.always to match the command it belongs to. _ipc and _sudo are added so every command has a definition. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>