Setup

First steps

Open Cronos.exe, it should not require you to enter your license key again.
If you need to reset or copy your license again, visit the 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
  │   ├── redirect_urls.csv
  │   └── tasks.csv
  ├── sessions/
  │   ├── queue_positions.csv
  │   └── ticketmaster_sessions.json
  └── signups/
      ├── 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.

If you do not add a custom file, the bot will automatically use the default proxies.txt

Tasks

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 tasks.csv and will get you to In-Bot Task Setup.
• If multiple CSV files are filled, the bot will ask which file to use.

Tasks groups

When multiple task rows exist for the same module, the bot will also prompt you to select which task group (row) to run.

In-Bot Task Setup

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