Skip to main content

Documentation 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.

Filly Discord Token Filler uses a combination of configuration files to control its behavior. All configuration files are located in the 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

project/
├── input/
│   ├── config.json      # Main configuration
│   ├── tokens.txt       # Discord tokens (one per line)
│   ├── invites.txt      # Invite codes (one per line)
│   └── proxies.txt      # Proxy list (one per line)
├── output/
│   ├── joined.txt       # Successfully joined tokens
│   ├── invalid.txt      # Invalid tokens
│   ├── locked.txt       # Locked tokens
│   ├── captcha.txt      # Tokens that encountered captcha
│   ├── failed.txt       # Failed join attempts
│   └── filled_tokens.txt # Tokens that reached max joins
└── index.py             # Main script

Quick Start

1

Configure captcha solver

Edit input/config.json to set up your captcha solver service and API key.
{
  "captcha": {
    "solve_captcha": true,
    "service": "razorcap",
    "apikey": "your-api-key-here",
    "proxyless": false
  }
}
2

Add tokens

Add your Discord tokens to input/tokens.txt, one per line:
MTIzNDU2Nzg5MDEyMzQ1Njc4OQ.GaBcDe.FgHiJkLmNoPqRsTuVwXyZ
email:password:token
username:password:token
3

Add invites

Add Discord invite codes to input/invites.txt, one per line:
abc123xyz
https://discord.gg/example
discord.gg/another
4

Configure proxies (optional)

If using proxies, add them to input/proxies.txt:
username:password@proxy.example.com:8080
username:password@proxy.example.com:8080:sessionid
Set "proxyless": false in config.json.

Configuration Options

Main Settings

threads
number
default:"10"
Number of concurrent threads for joining servers. Maximum threads used is the minimum of this value and the number of available tokens.
proxyless
boolean
default:"true"
Whether to run without proxies. Set to false to use proxies from input/proxies.txt.
max_joins
number
default:"100"
Maximum number of servers each token will join. Tokens that reach this limit are saved to output/filled_tokens.txt.
delay
number
default:"1"
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 the output/ 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

Rate Limiting: Discord has aggressive rate limiting. Use delays and proxies to avoid detection.
  • Start with a small number of threads (5-10) and increase gradually
  • Use a delay of at least 1-2 seconds between requests
  • Rotate proxies with session IDs to distribute requests
  • Monitor the output files to identify problematic tokens

Troubleshooting

  • Increase the delay between requests
  • Use proxies to distribute requests
  • Check if your tokens are fresh and valid
  • Reduce the number of concurrent threads
  • 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
  • Set "proxyless": false in config.json
  • Verify proxy format in input/proxies.txt
  • Check proxy authentication credentials
  • See Proxy Configuration for format details

Build docs developers (and LLMs) love