Flow reference: Plugins
Level Role Rewards
Give the roles for every level the member reached, e.g. 5=@Active, 10=@Regular (Leveling plugin).
Give the roles for every level the member reached, e.g. 5=@Active, 10=@Regular (Leveling plugin).
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
Member (blank = author) — 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.
Default: ``.
Rewards (level=role per line) — rewards
Map level thresholds to fixed role IDs using the format shown in the editor. Verify every role and its hierarchy before testing.
Input: Multiline text.
Format example, not a ready value for your server: `5=@Active
10=@Regular
25=@Veteran`.
Default:
{env.LEVEL_ROLES}.Keep lower reward roles — stack
Whether members keep roles for all achieved reward levels instead of only the highest one.
Input: On/off switch.
Editor guidance: Off: members only keep the role of their highest reward.
Default:
true.Outputs and next steps
out: Continue to the next step.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).