# UK tasks (+IE/AU/NZ/MX)

## 1. Opening **tasks.csv** file (Ron's editor)

> Follow **Encore IO\data\module\tasks** folder & Open tasks.csv

<div align="left"><figure><img src="https://content.gitbook.com/content/RusYC5jkBQT3lvwg4D17/blobs/1UNMZOBE8Uf1nsGUUgF7/image.png" alt="" width="563"><figcaption></figcaption></figure></div>

* UK 🇬🇧 / IE 🇮🇪 / AU 🇦🇺 / NZ 🇳🇿 / MX 🇲🇽 task file:

<figure><img src="https://877720333-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRusYC5jkBQT3lvwg4D17%2Fuploads%2Fhw9duUOAz6UoUkDJAarR%2Fimage.png?alt=media&#x26;token=8a5d57ba-0e9d-4a61-99ec-bc7f74256cff" alt=""><figcaption></figcaption></figure>

***

## 2. Task file setup

### **Email (+guest mode):**

Email of [accounts](https://encore-io.gitbook.io/tool/soft-setup/accounts "mention") which you want to launch on drop or for monitoring. \
Accounts must already be logged in

* How to activate guest mode instead of accounts?

To activate Guest mode, enter the following in the email field instead of accounts:

> guest\_1 \
> guest\_2\
> and so on

{% hint style="info" %}
Recommend to use Guest mode only for monitoring in combination with Watchdogs and `OnlyMonitor:true`
{% endhint %}

***

### **EventUrl for each account**

> To run accounts for different events. Recommend to fill if you need to launch accounts for different events.&#x20;

Enter url of the event for which you want to launch a specific account. With that feature you can run each account for different events. Make sure to enter EventUrl for each account if you want to use that feature.&#x20;

{% hint style="info" %}
For activation **event url for each account**  just leave blank when need to enter event ID in [bot-setup-and-launch](https://encore-io.gitbook.io/tool/soft-launch/bot-setup-and-launch "mention"). If you enter event via bot, than it will launch all account for only entered event.
{% endhint %}

***

### **MinPrice - MaxPrice**

Setup minimal and maximal price for tickets. Bot will only fetch tickets within this price range \[for example 0-1500].

***

### **Amount**

The number of tickets for reservation. Don't leave it blank.&#x20;

* Bot  support single & multiple tickets amount with prioritization of search. To activate multiple amount you need to set **UseMap - true** & enter amount with prioritization. For example: `4,3,2`
* The prioritization works from left to right, first the bot will search for the first number of tickets, if not found, it will move on to the next one.&#x20;
* The bot will also automatically consider the ticket limit. It will select the maximum available value of your multiple amount within this limit. So if you are unsure of event limit , it's recommended to use multiple amount.

***

### **Section**

Choose a specific section(s) for carting. If left blank, the bot will simply choose an available section.&#x20;

{% hint style="success" %}
The prioritization works from left to right, first the bot will search for the first section, if not found, it will move on to the next one. Prioritization works only if the `section` value is included in `SortOrder`.
{% endhint %}

* *Section name:* For Floor/GA/Letter sections use guide [ga-sections-name](https://encore-io.gitbook.io/tool/soft-setup/us-ca-eu-tasks/ga-sections-name "mention") to use right naming. As floor standing sections name may differ on the backend from what is shown in the picture.
* *Sections range:* For range of sections use `~` between it like `110~115,A1~A3`. For range option - sections should be listed in order in the manifest as well ([ga-sections-name](https://encore-io.gitbook.io/tool/soft-setup/us-ca-eu-tasks/ga-sections-name "mention")). If it's not in order in the manifest of event than you need to separate it with `,` as usual.
* *Sections priority:* Add a comma with an asterisk asterisk `,*` at the end to set priority (not filter) for carting specific sections (if still in stock) like `101,110~115,*`. If the prioritized sections are not in stock, the bot will cart any available section, taking into account the filters. If no asterisk is used, the bot will map only the listed sections and no others.

Variants example:

> Single section cart:  `110`
>
> Multiple sections cart:  `A1,110,A2,A3`
>
> Range of sections: `A1~A3,110~113,115`
>
> Priority for carting:  `A1~A3,110~113,115,*`

### Exclude section

{% hint style="info" %}
Use that option only separately from the sections field
{% endhint %}

Option to exclude sections that you do not want to cart, also supports ranges of sections (same as for sections).&#x20;

***

### Sort order \[prioritization]

{% hint style="success" %}
Only work when `UseMap` is set to `true`.
{% endhint %}

Feature sorts all found seats (after classic filters) using the specified values with prioritization from left to right. You can rearrange or remove values. If a prioritized section or value is missing, the bot will skip it and use the next parameter for sorting:

```
section,price,ticket_amount,row,total_amount
```

* `section` - priority is given to specific sections if they are specified by the user.
* `price` - sorts by ticket price.
* `ticket_amount` - when multiple quantity are specified in amount, priority is given to the highest value.
* `row` - selects the lowest available row considering current filters and priorities.
* `total_amount` - sorts by the number of available tickets in a row. rows with the most available seats are prioritized, as the more tickets available, the higher the chance of carting them.

Scenarios example:

* Scenario A: `price`,`section`, `ticket amount`, `row`

The bot first sorts by price, then within each price range, searches for the section, then looks at the number of tickets available in that section, and finally selects the lowest row.

* Scenario B: `section`, `price`, `ticket amount`, `row`

The bot first sorts all seats by section, then within each section filters by price, then looks at the number of tickets available in that price range, and finally selects the lowest row.

***

### **Unlock codes**

The codes are needed for pre-sale drops; after entering the code, access to carting is unlocked. If you fill code in task - each code will be bound to account.  Codes in task support also feature to "Reload tasks file on the fly" (described below in section 5).

* Single UnlockCode

Use it if you have only one code or sure that your code will 100% match. \
One code per account: 1 account = 1 presale code. Code will be linked to the account.

* Multiple UnlockCodes

`CDEAWL234EBB,CDECGHEBHOGHJ,FDFGD43FDFDFD`

You can enter multiple codes separated by commas; they will be linked to the task account. Thus, if one of the codes doesn't work, the bot will automatically move on to the next code until one works.

* [codes-pool](https://encore-io.gitbook.io/tool/soft-setup/codes-pool "mention")

If you need the codes not to be bound to specific accounts, then you need to add the codes in [codes-pool](https://encore-io.gitbook.io/tool/soft-setup/codes-pool "mention") file. Bot will randomly selects a code from the pool for whichever accounts pass queue. Each code used only once, used codes tracked based on the event ID.&#x20;

{% hint style="info" %}
To activate [codes-pool](https://encore-io.gitbook.io/tool/soft-setup/codes-pool "mention"), enter codes pool file names (with.txt) in `UnlockCode` in tasks instead of code. You can assign multiple code files to tasks, but only one file per task.&#x20;
{% endhint %}

***

### **Keywords (for filtering ticket type)**

Keywords work through ticket descriptions and help filter the necessary type of tickets. Support events with map and  [uk-resale-tickets-ie-au-nz-mx](https://encore-io.gitbook.io/tool/resale-setup/uk-resale-tickets-ie-au-nz-mx "mention") via "IsResale2". \
\
You can use keywords in various combinations:

{% hint style="info" %}
Keywords can be anything, just match ticket description. Also can use abbreviations, as long as one word is contained in the other ("platinum" > "plati")
{% endhint %}

> Positive (to include type): +standard&#x20;
>
> Negative (to exclude type): -platinum;-side;-obstructed
>
> Mix (include & exclude): +standard;-platinum

```
Popular keywords: standard | platinum | side (for side view) | obstructed
```

***

### **UseMap (true or false)**

{% hint style="info" %}
Bot will automatically switch modes if an event does not have a map.
{% endhint %}

* **true** - bot will cart directly from map, includes GA tickets;

Higher speed, but a higher risk of account bans. Even when using monitor proxies, this does not help, because this mode performs direct carting, not monitoring. You should set a high `CartAttemptDelay` to reduce the risk of bans.

*Filters:* Only works price & keyword filters, but with 2 nuances: price includes fees and TM may suggest alternative tickets if an exact match is not found.

* **false** - bot will cart only seats from quickpick (for no map events)

Lower chance of bans, but slower speed. This is the standard monitoring mode — basically the opposite. All filters supported, the price filter works as usual

***

### **Monitor proxy \[UseMonitorProxy]**

Put [proxies](https://encore-io.gitbook.io/tool/soft-setup/proxies "mention") for monitoring in **"MonitoryProxy.txt"** file in module folder & Set **true** to use separate proxies for monitoring for your task. The bot will randomly assign proxies from this file and replace them from the same file if they get banned.

> **true** - bot will use **"MonitoryProxy.txt"** only for monitoring;
>
> **false** - bot will use account proxies from **"Proxy.txt"** for monitoring.

***

### **DeliveryRegion** (t**o extend cart timer)**

Fill in the `Delivery region` with one of the options; by default, it is recommended to select `other`. With using that feature you will get cart timer extend \[\~5 min]

{% hint style="info" %}
Available regions may vary depending on the drop/region. Current example is for UK.&#x20;
{% endhint %}

> Fill region in tasks as on screen:
>
> * For `OTHER` fill in tasks `other` (recommended)
> * For `GREAT BRITAIN` fill in tasks `great britain`
> * For `N. IRELAND` fill in tasks `n. ireland`

<figure><img src="https://877720333-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRusYC5jkBQT3lvwg4D17%2Fuploads%2F99xEK0trpLjfkL0uVr6c%2Fimage.png?alt=media&#x26;token=3f74b55b-0ca1-4f74-a2b8-df9209806f9d" alt=""><figcaption></figcaption></figure>

***

### Option to change `Did` without restarting

You can now change the value in the link (after `did=`) without restarting the task

{% hint style="info" %}
For example, the working link turned out to be <https://www.ticketmaster.co.uk/lewis-capaldi-london-17-09-2025/event/350062D9EDD88180?did=artpre> and your tasks are already running. You just need to insert the value after `did=` - in this case: `artpre`
{% endhint %}

<div align="left"><figure><img src="https://877720333-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRusYC5jkBQT3lvwg4D17%2Fuploads%2F6iY8bJkBHFxPxnxYvZRU%2Fimage.png?alt=media&#x26;token=2e9f1ba3-d5c3-4887-a173-455c3778d26d" alt="" width="375"><figcaption></figcaption></figure></div>

***

### UseInternalMonitor to activate [internal-monitoring](https://encore-io.gitbook.io/tool/soft-launch/tickets-monitoring/internal-monitoring "mention")

{% hint style="info" %}
Internal monitoring works only with `UseMap` true

Full information how to setup in [Internal monitoring](https://encore-io.gitbook.io/tool/soft-launch/tickets-monitoring/internal-monitoring)
{% endhint %}

* Set `true` to activate [internal-monitoring](https://encore-io.gitbook.io/tool/soft-launch/tickets-monitoring/internal-monitoring "mention") mode on task
* Set `false` to use regular monitoring without internal

***

### **PreSendOtp/ForceQueueWait** (**true or false)**

Set true for both options for tasks which you want to pre-send OTP before waiting room/queue is up. Bot will pre-send OTP at at the time specified in [settings](https://encore-io.gitbook.io/tool/soft-setup/settings "mention") `OtpPreSendMinutes`.

> `PreSendOtp` true + `ForceQueueWait` true - to pre-send OTP&#x20;
>
> `PreSendOtp` false  - account will send OTP as usual when waiting room is up.

{% hint style="warning" %}
If queue is active on event, bot won't `PreSendOtp`, bot will join current queue.
{% endhint %}

{% hint style="info" %}
You can set time when you want bot to pre-send OTP in [settings](https://encore-io.gitbook.io/tool/soft-setup/settings "mention"):

* Tasks should be already launched by that time you set in `OtpPreSendMinutes`
  {% endhint %}

***

### Email OTP

Option to enable Email OTP depending on the OTP type set for the event:

* **true** -  bot will use Email OTP
* **false** - bot will use SMS OTP

***

### **IsResale / IsResael2** (**true or false)**

{% hint style="info" %}
Check current recommended setup in [uk-resale-tickets-ie-au-nz-mx](https://encore-io.gitbook.io/tool/resale-setup/uk-resale-tickets-ie-au-nz-mx "mention") page and discord server.
{% endhint %}

**IsResale / IsResale2** should only be enabled separately.&#x20;

> **true** - bot will cart only resale tickets;
>
> **false** - bot won't cart resale tickets, only standard.

***

### CD monitor limit <a href="#usemonitorwatchdog-entire-option-activation" id="usemonitorwatchdog-entire-option-activation"></a>

Monitoring attempt limit before the task stops.

> 0 - no limit

### CD cart limit

Сarting attempt limit before the task stops

> 0 - no limit

***

### UseMonitorWatchdog entire option activation <a href="#usemonitorwatchdog-entire-option-activation" id="usemonitorwatchdog-entire-option-activation"></a>

Activation of the entire watchdog option for monitoring; task mode for watchdog is configured via `IsWatchDog`.

* **true** - watchdog option for the task is activated and setup via `IsWatchDog`.
* **false** - bot will run as a regular task without the watchdog option. no ping from watchdogs tasks.

### IsWatchDog mode setup for UseMonitorWatchdog <a href="#iswatchdog-mode-setup-for-usemonitorwatchdog" id="iswatchdog-mode-setup-for-usemonitorwatchdog"></a>

The configuration is available/work only when `UseMonitorWatchdog` is enabled:

{% hint style="info" %}
If necessary, you can set all tasks to `IsWatchDog` true
{% endhint %}

* **true** - task will monitor and ping others watchdogs tasks: As soon as one of the watchdog tasks ping, all watchdogs tasks (regardless of whether IsWatchDog true or false) will be started immediately.
* **false** - tasks will be in standby mode waiting for ping from IsWatchDog true tasks to start.

### Only monitor (no carting) <a href="#only-monitor-no-carting" id="only-monitor-no-carting"></a>

* **true** - task will only monitor without carting attempts
* **false** - task will monitor & cart as usual

{% hint style="success" %}

#### Variation of setup depending on your goals

<img src="https://877720333-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRusYC5jkBQT3lvwg4D17%2Fuploads%2FlTTbLjz0GQcTx3SBkGYL%2Fimage.png?alt=media&#x26;token=a3ebb09c-3e5d-4e7d-baf7-de17d38af534" alt="" data-size="original">
{% endhint %}

***

### Monitor Delay

You can add a monitor delay separately for each task to have more customized monitoring. If left empty, the bot will use your current `monitordelay` from [settings](https://encore-io.gitbook.io/tool/soft-setup/settings "mention")

***

### Cart & Queue webhook

You can add a separate webhook URL for each task to receive notifications for each task individually. If left blank, the default webhook will be used from [settings](https://encore-io.gitbook.io/tool/soft-setup/settings "mention").&#x20;

{% hint style="info" %}
Support duplicate & server webhooks option
{% endhint %}

***

## 3. M**ultiple task files support**

You can create **multiple task files**. For example, if you want to separate your accounts for Drop.

{% hint style="info" %}
While [bot-setup-and-launch](https://encore-io.gitbook.io/tool/soft-launch/bot-setup-and-launch "mention") you will be prompted to choose a task file to run or you can just run all accounts.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/RusYC5jkBQT3lvwg4D17/blobs/0EnYVBga4RvGVZxBYvP5/image.png" alt=""><figcaption></figcaption></figure>

***

## 4. **Reloading tasks file on the fly**

Feature to "**Reload tasks file on the fly"**, when tasks already launched in [bot-setup-and-launch](https://encore-io.gitbook.io/tool/soft-launch/bot-setup-and-launch "mention"):

Just change your task file and save it, bot will update launched tasks filters and codes automatically.

* No need to relaunch tasks, bot will update all auto after you edit and save file;
* You can change all filters and presale code beside "Email" & "EventUrl";
* You can change the code in tasks after they are launched, but you need to have at least some random code in the task before the queue starts. Before the queue starts, you can also change empty code;
* You can't only add new tasks or remove current tasks, when it's launched.
