US/CA/EU tasks
Tasks file for Ticketmaster US/CA/EU & Livenation US
Last updated
Tasks file for Ticketmaster US/CA/EU & Livenation US
Last updated
Follow Encore IO\data\module\tasks folder & Open tasks.csv
All filters can be updated in real-time during launched tasks
Email of Accounts 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
To run accounts for different events. Recommend to fill if you need to launch accounts for different events.
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.
Setup minimal and maximal price for tickets. Bot will only fetch tickets within this price range [for example 0-1500].
The number of tickets for reservation. Don't leave it blank.
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.
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.
Choose a specific section(s) for carting. If left blank, the bot will simply choose an available section.
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.
Section name: For Floor/GA/Letter sections use guide GA sections name 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). 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:
110Multiple sections cart:
A1,110,A2,A3Range of sections:
A1~A3,110~113,115Priority for carting:
A1~A3,110~113,115,*
Option to exclude sections that you do not want to cart, also supports ranges of sections (same as for sections).
Only work when UseMap is set to true.
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 - 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.
The codes are needed for pre-sale drops; after entering the code, access to carting is unlocked. Tasks won't stop now if unlock code is wrong. If you fill code in tasks file - each code will be bound to account. Codes in task support also feature to "Reload tasks file on the fly" (described 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.
If you need the codes not to be bound to specific accounts, then you need to add the codes in Codes pool 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.
Keywords work through ticket descriptions and help filter the necessary type of tickets. Works only for events with map. You can use keywords in various combinations:
Positive (to include type): +standard
Negative (to exclude type): -platinum;-side;-obstructed
Mix (include & exclude): +standard;-platinum
true (recommended) - bot will cart directly from map, includes GA tickets.
false (for no map events) - bot will cart only seats from quickpick. captcha works as on UK.
Ticket carting option specifically by seats rather than by rows. It's the same as selecting seats on a map rather than from a list.
If set true - the task will automatically switch to monitoring mode after carting instead of stopping it. This way, same account will be able to cart again.
Set true to activate Internal monitoringmode on task
Set false to use regular monitoring without internal
Put Proxies 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.
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 OtpPreSendMinutes.
PreSendOtptrue +ForceQueueWaittrue - to pre-send OTP
PreSendOtpfalse - account will send OTP as usual when waiting room is up.
If queue is active on event, bot won't PreSendOtp, bot will join current queue.
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
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.
The configuration is available/work only when UseMonitorWatchdog is enabled:
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.
true - task will only monitor without carting attempts
false - task will monitor & cart as usual
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
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.
For example, if you want to separate your accounts for Drop.
You can edit tasks file during drop, when tasks already launched in
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.
