Redo the security system, in order to remove the "/secu login" command and the global unlocking of the radio menu.
Define security roles.
Assign radio menus / commands to specific security roles.
When a player enters a slot, get the security info from the server hook and rebuild the radio menu based on the security role:
- all players get the "default" public menus and commands
- only players with the specific role (or above) get the secured menus and commands.
To ensure that only the right players get the right roles, we need to add these menus/commands specifically to a group - and remove them after the player leaves / disconnect (plan a fallback if the player rage-quits or has a technical issue, to make sure the commands do not stay in the slot for the next player to use).
For single-player, self-hosted multiplayer or for servers where the hook cannot be used, we may have other means of identifying the groups that need to have the secured roles:
- static, in the mission configuration
- based on the player name (find a way to get this from the mission API)
- ... TBD
Redo the security system, in order to remove the "/secu login" command and the global unlocking of the radio menu.
Define security roles.
Assign radio menus / commands to specific security roles.
When a player enters a slot, get the security info from the server hook and rebuild the radio menu based on the security role:
To ensure that only the right players get the right roles, we need to add these menus/commands specifically to a group - and remove them after the player leaves / disconnect (plan a fallback if the player rage-quits or has a technical issue, to make sure the commands do not stay in the slot for the next player to use).
For single-player, self-hosted multiplayer or for servers where the hook cannot be used, we may have other means of identifying the groups that need to have the secured roles: