mirror of
https://github.com/PHIDIAS0303/ExpCluster.git
synced 2026-09-21 17:04:00 +00:00
Every call site of expcore.roles now uses exp_roles, and the legacy module, its config, and the glue which refreshed guis on role events are deleted. Where a file only renamed the require and the permission strings the change is mechanical; the rest: - Jail is now "give the Jail role" and unjail "take it away". The role has a higher priority than every other so holding it suppresses them, which is what stashing and restoring the roles was for. - The command role authority derives exp_scenario.command.<name> from the command name, and the role parsers use player_outranks rather than comparing indexes with their own root check. - The admin and spectator triggers, and the gui refresh on role changes, live in exp_scenario/control/roles.lua; the system commands trigger stays with the command authority. - The player list warn button is keyed on create_warning, the permission the command behind it already required, and report on create_report. Both were keyed on names no role held, so only root ever saw them. - The warps and tasks configs say exp_roles where they said expcore.roles. - The role tables the readme and player list read are replaced by get_player_names and get_roles. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
22 lines
594 B
Lua
22 lines
594 B
Lua
--[[-- Control - Roles
|
|
Applies the in game effects of the player permissions defined by the scenario
|
|
]]
|
|
|
|
local Gui = require("modules/exp_gui")
|
|
local Roles = require("modules/exp_roles")
|
|
|
|
Roles.define_permission_trigger("exp_scenario.player.admin", function(player, state)
|
|
player.admin = state
|
|
end)
|
|
|
|
Roles.define_permission_trigger("exp_scenario.player.spectator", function(player, state)
|
|
player.spectator = state
|
|
end)
|
|
|
|
return {
|
|
events = {
|
|
--- @diagnostic disable-next-line: access-invisible
|
|
[Roles.events.on_player_roles_changed] = Gui._ensure_consistency,
|
|
}
|
|
}
|