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.

This page documents all available configuration options for Filly Discord Token Filler. Configuration is stored in input/config.json.

​
Configuration File Location

The configuration file must be located at: 
input/config.json

​
JoinerConfig DataClass

The configuration is loaded into the JoinerConfig dataclass (index.py:31-38): 
@dataclass
class JoinerConfig:
    delay: int
    proxyless: bool
    threads: int
    max_joins: int
    captcha: Dict

​
Top-Level Configuration

​
threads
integer
default:"10"
required
Number of concurrent threads to use for joining servers.
  • Controls how many tokens can be processed simultaneously
  • Limited by the number of available tokens (index.py:249)
  • Higher values increase speed but may trigger rate limits
Example:
"threads": 10
​
proxyless
boolean
default:"true"
required
Whether to run without proxies.
  • When true: Runs without proxies (direct connections)
  • When false: Loads proxies from input/proxies.txt (index.py:84)
  • Proxy format supports session ID randomization (index.py:85-87)
Example:
"proxyless": true
​
max_joins
integer
default:"100"
required
Maximum number of servers each token should join.
  • Limits how many invites each token will process
  • Tokens that reach this limit are saved to output/filled_tokens.txt (index.py:270-271)
  • Actual joins limited to available invites (index.py:248)
  • Tracked per-token via TokenManager.increment_joins() (index.py:267)
Example:
"max_joins": 100
​
delay
integer
default:"1"
required
Delay in seconds between join attempts.
  • Sleep duration after each join operation (index.py:220-221)
  • Set to 0 to disable delay
  • Helps avoid rate limiting
Example:
"delay": 1

​
Captcha Configuration

​
captcha
object
required
Configuration for captcha solving services.The captcha object contains settings for automatic captcha detection and solving.
​
captcha.solve_captcha
boolean
default:"true"
required
Enable or disable automatic captcha solving.
  • When true: Automatically detects and solves captchas (index.py:189)
  • When false: Skip captcha solving, joins will fail if captcha is encountered
  • Captcha detection checks for "captcha_sitekey" in response (index.py:189)
Example:
"solve_captcha": true
​
captcha.service
string
default:"razorcap"
required
The captcha solving service to use.Supported services:
  • razorcap - RazorCap API (solver.py:55)
  • hcoptcha - HCOptcha API (solver.py:127)
  • csolver - CSolver API (solver.py:33, uses hardcoded API key)
  • capmonster - CapMonster Cloud (solver.py:203)
Service mapping defined in index.py:119-125.Example:
"service": "razorcap"
​
captcha.apikey
string
required
API key for the selected captcha solving service.
  • Required for all captcha services
  • Used in solver.py:13 as api_key
  • Different services require different API keys
Example:
"apikey": "3e5fc347-dfd8-4b12-9ca3-e57f931c5fbc"
​
captcha.proxyless
boolean
default:"false"
required
Whether to solve captchas without proxies.
  • When true: Solves captchas directly without proxy (solver.py:22-23)
  • When false: Uses proxies from input/proxies.txt for captcha solving (solver.py:18-20)
  • Independent from the top-level proxyless setting
Example:
"proxyless": false

​
Complete Example Configuration

{
    "threads": 10,
    "proxyless": true,
    "max_joins": 100,
    "delay": 1,
    "captcha": {
        "solve_captcha": true,
        "service": "razorcap",
        "apikey": "3e5fc347-dfd8-4b12-9ca3-e57f931c5fbc",
        "proxyless": false
    }
}

​
Browser Configuration Variables

These variables are defined in index.py and used for browser fingerprinting:
​
chrome_version
integer
default:"133"
Chrome version used for user agent and sec-ch-ua headers.Defined in index.py:27:
chrome_version = 133
​
sec_ch_ua
string
Chrome user agent client hints header value.Defined in index.py:28:
sec_ch_ua = f'"Google Chrome";v="{chrome_version}", "Chromium";v="{chrome_version}", "Not;A=Brand";v="8"'
Value:
"Google Chrome";v="133", "Chromium";v="133", "Not;A=Brand";v="8"
​
user_agent
string
User-Agent string for HTTP requests.Defined in index.py:29:
user_agent = f'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/{chrome_version}.0.0.0 Safari/537.36'
Value:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36

​
Input Files

  • input/tokens.txt - Discord tokens to use (one per line)
  • input/invites.txt - Discord invite codes (one per line)
  • input/proxies.txt - HTTP proxies (required when proxyless: false)

​
Output Files

  • output/joined.txt - Successfully joined tokens (index.py:147)
  • output/invalid.txt - Invalid/unauthorized tokens (index.py:153)
  • output/locked.txt - Locked tokens (index.py:160)
  • output/captcha.txt - Tokens that encountered captcha (index.py:191)
  • output/failed_token.txt - Failed due to token issues (index.py:167)
  • output/failed_captcha.txt - Failed due to captcha solver issues (index.py:173)
  • output/failed.txt - Other failures (index.py:178)
  • output/filled_tokens.txt - Tokens that reached max_joins limit (index.py:270)

​
Notes

  • Configuration is loaded using json.loads() and unpacked into JoinerConfig dataclass (index.py:243)
  • Missing required fields will cause the application to fail at startup
  • Invalid JSON syntax will prevent the configuration from loading
  • Thread count is automatically limited by available tokens (index.py:249)
  • Max joins is automatically limited by available invites (index.py:248)

Build docs developers (and LLMs) love

Get started for freeTalk to us