ReactionRoles v1.1.1
Update Release
Features / Bug Fixes
- Fixed select menus removing the last selected role when choosing a new one.
- Fixed the same select menu issue for categories and sub-panels.
- Fixed select menu max-role checks so it validates the real final role count.
- Fixed sub-panel embeds being required even though the dashboard said optional.
- Fixed ReactionRoles dashboard saving showing FORBIDDEN when creating or editing panels.
- Fixed ReactionRoles config saving saying "structure does not match the default structure".
- Fixed old ReactionRoles configs having language data inside the main config.
- Added the missing command permission setting to the dashboard settings page.
This update mainly focuses on dashboard saving issues and select menu behavior. If you were having issues with roles getting swapped/removed or the dashboard refusing to save ReactionRoles configs, update to this version.
Features/Bug Fixes
- Added
Max Roles For This Panelto the Reaction Roles panel editor.- Kept the old global
max_roles_per_userasDefault Max Roles Per Panelfor backward compatibility.- Runtime enforcement now uses: category override, sub-panel override, panel override, then default.
- Multi-selects now validate the final selected count, so users can’t select 3 at once on a max-1 panel.
- Reaction-based panels now respect max-role and hierarchy validation too.
- Fixed auto-remove reaction behavior so removing the user’s reaction does not immediately remove the role again.
- Added role-based access rules: required, blocked, and bypass roles.
- Added access rules for panels, sub-panels, and individual role entries.
- Added
Max Roles For This Sub-panel.- Added an audit log channel for ReactionRoles.
- Added audit logging for denied attempts.
- Added audit logging for dashboard sends/deletes and slash-command reloads/resends.
- Added dashboard role pickers for the new access controls.
