Flow reference: Plugins
Anti-Nuke: Punish
Ban, kick or strip every role from the attacker.
Ban, kick or strip every role from the attacker.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
User — user
Choose the target user. {user} may be a command's selected user; {author} is the caller. Use an ID or the variable picker rather than a display name.
Input: Text with variable suggestions.
Format example, not a ready value for your server:
{executor.id}.Default:
{executor.id}.Punishment — mode
Choose the operating mode before other fields. Update versus create, acknowledgement mode and punishment mode have different consequences.
Input: Fixed choice.
Default:
strip-roles.Available choices (preserve the exact value):
strip-roles — Remove all roles (quarantine)kick — Kickban — BanReason — reason
Describe why the action is taken. Use a meaningful audit/support explanation and avoid sensitive personal details.
Input: Text with variable suggestions.
Default:
Anti-Nuke: limit exceeded.Outputs and next steps
out: Continue to the next step.failed: The operation failed; provide a safe error response.Test and troubleshoot
Install the corresponding plugin and configure its required accounts, channels and secrets. Test an API read before a write operation. An external-service error is not a reason to recreate the whole bot.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).