From 91d2cbead7ec0a4eac63985335fe5df089323fb0 Mon Sep 17 00:00:00 2001
From: Your Name <you@example.com>
Date: Wed, 26 Aug 2020 22:33:43 +0200
Subject: [PATCH] add --force to the CLI example in the dev guide

---
 docs/hashcat-plugin-development-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/hashcat-plugin-development-guide.md b/docs/hashcat-plugin-development-guide.md
index 078aa64d0..6abd74992 100644
--- a/docs/hashcat-plugin-development-guide.md
+++ b/docs/hashcat-plugin-development-guide.md
@@ -539,7 +539,7 @@ Additionally there is a couple of command line parameters that you want to use:
 Typically a developer command line for hashcat looks the following:
 
 ```
-$ rm -rf kernels $HOME/.nv; ./hashcat -m XXXXX hash.txt word.txt --potfile-disable --self-test-disable -n 1 -u 1 -T 1 --quiet --backend-vector-width 1 -d 1
+$ rm -rf kernels $HOME/.nv; ./hashcat -m XXXXX hash.txt word.txt --potfile-disable --self-test-disable -n 1 -u 1 -T 1 --quiet --backend-vector-width 1 -d 1 --force
 ```
 
 If you need to printf from without a _loop kernel, keep in mind that you need to add a branching manually for a specific loop position.