Filly Discord Token Filler uses a combination of configuration files to control its behavior. All configuration files are located in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Nuu-maan/Filly-Discord-Token-Filler/llms.txt
Use this file to discover all available pages before exploring further.
input/ directory.
Configuration Files
config.json
Main configuration file for captcha settings, threading, delays, and join limits
tokens.txt
Discord authentication tokens for joining servers
invites.txt
Discord server invite links to join
proxies.txt
HTTP/HTTPS proxy list with session rotation support
Directory Structure
Quick Start
Configuration Options
Main Settings
Number of concurrent threads for joining servers. Maximum threads used is the minimum of this value and the number of available tokens.
Whether to run without proxies. Set to
false to use proxies from input/proxies.txt.Maximum number of servers each token will join. Tokens that reach this limit are saved to
output/filled_tokens.txt.Delay in seconds between join attempts per thread. Set to
0 for no delay.Captcha Settings
See the Captcha Configuration page for detailed captcha solver setup.Output Files
The tool automatically creates output files in theoutput/ directory:
- joined.txt - Tokens that successfully joined servers
- invalid.txt - Tokens that returned 401 (unauthorized)
- locked.txt - Tokens that returned 403 (forbidden/locked)
- captcha.txt - Tokens that encountered captcha challenges
- failed.txt - Tokens that failed for other reasons
- failed_token.txt - Tokens that failed due to “Unknown Message” errors
- failed_captcha.txt - Tokens that failed due to captcha solver issues
- filled_tokens.txt - Tokens that successfully reached max_joins limit
Invalid and locked tokens are automatically removed from
input/tokens.txt to prevent reuse.Best Practices
Troubleshooting
All tokens are getting locked
All tokens are getting locked
- Increase the delay between requests
- Use proxies to distribute requests
- Check if your tokens are fresh and valid
- Reduce the number of concurrent threads
Captcha solver not working
Captcha solver not working
- Verify your API key is correct in
config.json - Check your captcha service balance
- Ensure the service name matches exactly (case-sensitive)
- Review the Captcha Configuration page
Proxies not being used
Proxies not being used
- Set
"proxyless": falseinconfig.json - Verify proxy format in
input/proxies.txt - Check proxy authentication credentials
- See Proxy Configuration for format details