From 370f01c0bf09aa7b55a7f34d631ccd8eef12c213 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 13 Aug 2025 08:09:16 +0300 Subject: [PATCH] Fix `!draupnir ban` command example to not include a dash A dash in the ban reason message makes Draupnir report this error: > There was an unexpected argument provided for this command. > draupnir ban [...reason] > Encountered unexpected keyword argument: all --- docs/configuring-playbook-bot-draupnir.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index d855c4059..0a9019e6e 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -259,7 +259,7 @@ The simplest and most useful entity to target is `user`. Below are a few example To create rules, you run commands in the Management Room (**not** in the policy list room). - (ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others` -- (ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake` +- (ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server, all users are fake` As a result of running these commands, you may observe: