Setup

First steps

Open Cronos.exe, it should not require you to enter your license key again.
If you need to reset your license, visit the Whop dashboard.

When installed correctly, the following folders and files are generated:

Cronos/
├── Cronos.exe
├── config.json
├── accountgen/
│   ├── accounts.csv
│   ├── proxies.txt
│   └── tasks.csv
├── queue/
│   ├── proxies.txt
│   └── tasks.csv
└── signups/
    ├── accounts.csv
    ├── emails.csv
    ├── proxies.txt
    └── tasks.csv

Proxies

Cronos supports the following proxy formats:

• HTTP: host:port
• HTTP with authentication: host:port:username:password

Using multiple proxy files

If you want to use more than one proxy file for a module, you can create an additional file manually.
For example:

proxies2.txt

When the bot detects multiple proxy files inside a folder (e.g. queue), it will prompt you to select which file to use before starting your tasks. It will then only use proxies from the selected file.

If you do not add a custom file, the bot will not prompt you and will automatically use the default:

proxies.txt

Separate Proxies per Module

Each module in Cronos requires its own proxies file. They do not share or mix proxies.

You will need to set up proxies for:

• accountgen/proxies.txt
• signups/proxies.txt
• queue/proxies.txt

Make sure each folder has the correct proxies file inside, as the bot will only use the proxies placed in that specific folder.

CSV Files

Cronos uses CSV files to manage tasks, accounts, and signups.
Each module has its own CSV files, and you can also add custom files if needed.

By default, the bot will read from the tasks.csv file inside the relevant module’s folder.

If a CSV file is empty, the bot will not prompt you to run CSV tasks.
If multiple CSV files are filled, the bot will ask which file to use.
When multiple task rows exist for the same module, the bot will also prompt you to select which task group (row) to run.

CSV tasks are required for Ticketmaster modules but optional for others.

Queue Tasks CSV

File:

queue/tasks.csv

Headers:

Module,Mode,Quantity,URL,Email,Password,Start Time,Stop Time,Proxy File

• Module – The module to run (e.g., Ticketmaster).
• Mode – The mode within that module.
• Quantity – How many tasks to run.
• URL – The target link.
• Email, Password – Login details if required by the module.
• Start Time, Stop Time – Optional scheduling fields.
• Proxy File – Optional field to specify a proxy file.

Proxy File Behavior

• If Proxy File is left empty → the bot will default to using proxies.txt in the same folder.
• If you enter a custom proxy file name → make sure that file exists in the same folder (e.g. proxies2.txt).

Scheduling Tasks

• Use the format:
  • 12:01:10 (hours:minutes:seconds)
  • 12:00 (hours:minutes only)
• Always use your local timezone (the time your PC is set to).
• Both Start Time and Stop Time are optional.

Examples:

• If only Start Time is filled → tasks wait until that time to start.
• If only Stop Time is filled → tasks start immediately and stop at the specified time.
• If both are filled → tasks run within that time window.

Manual Configuration Instead of CSV

Even if tasks.csv is filled, the bot will prompt you before running CSV tasks.
At this prompt you can select Cancel, which lets you manually configure tasks for the module instead.

Notes

• CSV files must always be saved before attempting to start tasks.
• Further explanation of the required fields will be discussed in the module category sections.