================================================================================
  fortnite_checker — Setup & Usage
================================================================================

REQUIREMENTS
------------
  - Python 3.10 or newer (https://python.org/downloads)
    During install, tick "Add Python to PATH"
  - Google Chrome installed (standard install, any recent version)
  - pip packages (install once, see below)


INSTALL DEPENDENCIES
--------------------
  Open Command Prompt or PowerShell in this folder and run:

    pip install requests websocket-client

  That's all you need.


COMBO FILE FORMAT
-----------------
  Plain text file, one account per line:

    email@example.com:password123
    user2@gmail.com:hunter2
    ...

  Lines without a colon are skipped automatically.


PROXY FILE FORMAT  (optional)
------------------------------
  Plain text file, one proxy per line. Supported formats:

    host:port
    host:port:username:password

  Example:
    123.45.67.89:10000
    mp.evomi.com:3000:myuser:mypassword

  Leave the proxy file prompt blank to run without proxies.
  Residential proxies are strongly recommended — datacenter IPs
  get blocked by the login endpoint.


RUNNING THE CHECKER
-------------------
  1. Open Command Prompt or PowerShell.
  2. cd into this folder.
  3. Run:

       python fortnite_checker.py

  4. When prompted:
       Combo file  : path to your combo .txt
       Proxy file  : path to your proxy .txt  (or press Enter to skip)
       Threads     : number of Chrome windows to open (1–20, recommended 3–5)

  Chrome windows will open automatically — don't close them while it runs.


OUTPUT FILES
------------
  After the run, results are written to:

    hits.txt   — valid accounts with V-Bucks, skin count, and login link
    bads.txt   — confirmed wrong password
    2fa.txt    — accounts locked behind 2-step verification
    nofn.txt   — valid Nintendo account but no Fortnite / Epic link
    retry.txt  — blocked or timed-out (re-run these with a fresh IP or proxy)
    errors.txt — malformed lines or unexpected crashes


TIPS
----
  - If you see a lot of RETRY, your IP or proxy pool is rate-limited.
    Either wait a couple of hours or switch to residential proxies.
  - Start with 2–3 threads. More threads = more Chrome windows = more RAM.
  - The checker requires an active internet connection throughout.
  - Each Chrome window uses its own isolated profile so sessions never mix.


TROUBLESHOOTING
---------------
  "Chrome not found"
    → Make sure Google Chrome is installed, not Chromium or Edge.

  "No Chrome instances responded"
    → Chrome took too long to start. Close any other Chrome windows and retry.

  "pip is not recognized"
    → Python wasn't added to PATH. Reinstall Python with the PATH option ticked.

  All RETRY, zero hits or fails
    → Your IP is rate-limited. Use residential proxies or wait it out.

================================================================================
