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.
Statistics Data Structure
The tool tracks statistics using theJoinerStats dataclass (from index.py:40-49):
Field Descriptions
| Field | Description | Incremented When |
|---|---|---|
total | Unused field (defaults to 0) | Never incremented in current implementation |
joined | Successfully joined servers | HTTP 200 response received |
captcha | Captcha challenges encountered | ”captcha_sitekey” detected in response |
captcha_solved | Captchas successfully solved | Solver returns valid solution |
failed | Failed join attempts | Generic errors or captcha solver failures |
locked | Locked/restricted tokens | HTTP 403 response received |
invalid | Invalid/unauthorized tokens | HTTP 401 response received |
current | Current number processed | Each response handled |
The
total field exists in the dataclass but is never used. The console title displays total_invites (a function parameter), not stats.total.Real-Time Console Title
The console window title updates continuously to show live statistics during execution.Title Format
Fromindex.py:223-239, the title is updated by a dedicated thread:
Example Title
Update Frequency
The title refreshes every 100 milliseconds (0.1 seconds) for smooth real-time updates.Thread Behavior
- Runs as a daemon thread - automatically exits with main program
- Uses a threading.Event signal to stop gracefully
- Handles errors to prevent crashes during title updates
Final Statistics Display
When the joining process completes, a comprehensive statistics summary is displayed.Output Format
Fromindex.py:286-301, the final statistics appear as:
Example Output
Color Coding
- Cyan - Informational (Total Processed, Captcha count)
- Green - Success metrics (Successfully Joined)
- Yellow - Warnings (Captcha Encountered)
- Red - Errors (Failed, Invalid, Locked)
Statistics Tracking Flow
Time Calculation
The tool tracks execution time from start to finish:{minutes} Minutes and {seconds} Seconds
Thread Safety
All statistics updates are thread-safe because:- Python GIL - Global Interpreter Lock ensures atomic integer operations
- Simple Increments - Only
+=operations, no complex mutations - Read-Only in Title - Title thread only reads, never writes
Why doesn't 'total' match the sum of other stats?
Why doesn't 'total' match the sum of other stats?
The
total field represents the number of invites to process, not the tokens. The sum of joined + failed + invalid + locked should approximately equal the number of tokens processed.Can captcha_solved exceed captcha count?
Can captcha_solved exceed captcha count?
No. The
captcha_solved counter is only incremented when a captcha is encountered AND successfully solved. It will always be less than or equal to captcha.Why might current not equal joined + failed + invalid + locked?
Why might current not equal joined + failed + invalid + locked?
Rate limited requests (HTTP 429) increment
current but don’t increment any success/failure counters. These are temporary failures that may be retried.Does the title update affect performance?
Does the title update affect performance?
No. The title update runs in a separate daemon thread and only performs a lightweight string formatting operation every 100ms. The impact is negligible.
Exit Statistics
After displaying final statistics, the tool:- Shows “Press Enter to exit…” prompt
- Waits for user to press Enter key
- Displays “Exiting in 3 seconds…” countdown
- Sleeps for 3 seconds before closing