Modifying Environment.ini to define a custom wordlist type is incredibly useful when dealing with specialized data. Let us walk through a concrete example.
He had the config loaded. The syntax looked clean, the proxies were pulsing green, and he had just downloaded a fresh "combo" list—thousands of lines of potential logins. With a sense of triumph, he clicked .
If the basic troubleshooting steps do not resolve the issue, you may need to perform more advanced troubleshooting:
Check the box next to the wordlist type you want to use, or add it to the list. Click (disk icon) in the top menu. Re-load the configuration in your job runner. Modifying Environment
Open your OpenBullet folder and navigate to UserData > Configs .
Change your input file ( .txt ) to match this structure exactly.
Important: After editing Environment.ini , you must restart OpenBullet for the changes to take effect. The syntax looked clean, the proxies were pulsing
3. How to Fix: "This Config Does Not Support The Provided Wordlist Type" Here is a step-by-step approach to resolving this error. Method A: Match the Config to Your Wordlist
Update the Wordlist Type metadata inside OpenBullet's environment.
If a config is programmed to accept only Email:Pass combinations, but you attempt to run it using a wordlist imported as User:Pass (or vice versa), OpenBullet blocks the runner block from executing to prevent false negatives or engine crashes. How to Fix the Error Click (disk icon) in the top menu
Easy to accidentally swap inputs in the OpenBullet UI.
A broad category often used for single-string data like API keys, tokens, or URLs.
Method 1: Change the Wordlist Type in the Runner (Recommended) Open your active tab in OpenBullet.
When you see the message "This config does not support the provided wordlist type," it means there’s a between what the config expects as input and what your wordlist provides.