# EU Tasks (AT/DE/NL/AE/NO/DK/CH/PL)

1. Follow **Encore IO\data\module\tasks** folder.

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

***

2. Open **tasks.csv** file with Ron's editor.

<figure><img src="https://877720333-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRusYC5jkBQT3lvwg4D17%2Fuploads%2F0Uq4inydHWc58VZroRAF%2Fimage.png?alt=media&#x26;token=ab5e7308-a626-4879-9f9c-0746d905da0c" alt=""><figcaption></figcaption></figure>

***

3. Fill in the file:

* **Proxy:**

{% hint style="info" %}
Bot will automatically add proxies from [proxies](https://encore-io.gitbook.io/tool/soft-setup/proxies "mention") files, however you can add them manually in tasks too if need.&#x20;
{% endhint %}

> No need to fill proxies in tasks if you already fill email in tasks

For launch EU initial drops (without login) you don't need to run accounts. Instead of accounts use proxies as EU events (not resale / without login) don't require account to join in queue, only IP. So 1 proxy is equivalent to logging in from 1 account. So 1 task line = 1 entrance in queue, which requires 1 proxy. Also you can try to use 1 proxy for several tasks.

* **Email (for resale & queue with login)**:

Email of [accounts](https://encore-io.gitbook.io/tool/soft-setup/accounts "mention") which you want to launch for [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention") & for queue with login mandatory. Make sure to complete [accounts-login](https://encore-io.gitbook.io/tool/soft-launch/accounts-login "mention") of accounts which you add.&#x20;

{% hint style="info" %}
In the case of a standard Euro queue without login, you can also add emails to the accounts if you want to automatically log into them during checkout
{% 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/URL in [bot-setup-and-launch](https://encore-io.gitbook.io/tool/soft-launch/bot-setup-and-launch "mention"). If you enter event via bot console, than it will launch all account for only entered event.
{% endhint %}

* [<mark style="color:blue;">\[🟡 on hold\]</mark>](#user-content-fn-1)[^1] **EventVfUrl for each account:**&#x20;

Enter VerifiedFan drop url which you receive via mail for each account which were selected for V&#x46;**.**&#x20;

{% hint style="info" %}
For each VF account, you must also fill out the **EventUrL** which you want to cart for each account so that the bot can cart specific event during VF drop. Make sure that **EventUrl** location match with your VF account win,
{% endhint %}

Bot support both format of VF links:

> <https://click.mailing.ticketmaster.com/>\
> <https://ticketmastereu.queue-it.net>

* **MinPrice - MaxPrice:**

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

* **Amount \[single/multiple]:**

> Multliple amount supported only for  [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention").

The number of tickets for reservation. Don't leave it blank. \
For resale tickets support multiple tickets amount with prioritization of search. To activate multiple amount you need to enter amount with prioritization.

{% hint style="info" %}
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.\
\
For example: `2,3,1`
{% endhint %}

* **Section:**

> Not supported for [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention")

{% hint style="info" %}
For Floor/GA/Letter sections make sure to use guide [floor-ga-sections-name](https://encore-io.gitbook.io/tool/vf-module-on-hold/eu-tasks-at-de-nl-ae-no-dk-ch-pl/floor-ga-sections-name "mention"). \
As floor standing sections name may differ on the backend from what is shown in the picture.
{% endhint %}

Choose a specific section for ticket purchase. If left blank, the bot will simply choose an available section (for example 204 / B16).&#x20;

* **Keywords - for filtering ticket type:**

> Work with [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention") and with setup \<Best offer - true>

Keywords work through ticket descriptions and help filter the necessary type of tickets. \
Support events with map and  [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention").\
\
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
```

* **BestOffer - True / False:**

{% hint style="info" %}
For events without map (like on screen) use only **BestOffer - True** mode.\
\
![](https://content.gitbook.com/content/RusYC5jkBQT3lvwg4D17/blobs/vbvuQxRFOtxRMX2tqRSg/telegram-cloud-photo-size-2-5210756896372413416-w.jpg)
{% endhint %}

> **True** - TM will auto-select the best available tickets. Price filter supported, section not.&#x20;
>
> **False** - Bot will select considering your setup for price and section.

* **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.

* **IsResale / IsResale2 - true or false:**&#x20;

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

"IsResale" and "IsResale2" should only be enabled separately:

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

* **RndResale - true or false:**&#x20;

An additional option for [eu-resale-tickets](https://encore-io.gitbook.io/tool/resale-setup/eu-resale-tickets "mention"). \
Enable the option only together with one of **"IsResale"** modes.

> **true** - enable RndResale option;
>
> **false** - disable RndResale option.

* **UnlockCode:**

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).

{% hint style="info" %}
**Codes pool.** If you need the codes not to be bound to specific accounts, then you need to add the codes to the console during task launch [bot-setup-and-launch](https://encore-io.gitbook.io/tool/soft-launch/bot-setup-and-launch "mention").\
Bot will randomly selects a code (each code used only once) from the pool for whichever accounts pass queue. If you use codes pool, than don't add codes in tasks.&#x20;
{% endhint %}

> Single UnlcockCode

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.

***

4. 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>

***

5. 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.

[^1]:
