Settings

Proper configuration is a key component of your success

1. Follow Encore IO folder and open settings file.

If necessary, you will be able to change all delays in live during active tasks without restarting bot

2. Fill in the settings file:

Enter the key from the dashboard:

{
"License":"Your key",

Add your IMAP email with IMAP password from IMAP setup:

ImapHost/ImapPort keep by default. For adding multiple IMAP use Multiple IMAPguide.

"Imap":[
  {
    "ImapHost":"imap.gmail.com",
    "ImapPort":993,
    "ImapEmail":"Your imap gmail",
    "ImapPassword":"Your imap password"
  }
],

Add captcha solvers API keys in settings:

Register on captcha services & add enough balance. Then copy API key.

Signup & get captcha API on the dashboard. Select use pay per usage option, no need to buy separate packages.

You can get a new API key by topping up your balance (leave API key field empty) or recharge if you have key already.

Create an account on their Dash & get API key.

Full setup for Bright Data in Captcha harvester guide

Signup & get captcha API on the dashboard. Use pay per usage option

Open a ticket on their Discord server to receive and top up your API key

  "Captcha":{
    "TwoCapKey":"",
    "CapMonsterKey":"",
    "CapSolverKey":"",
    "AutoSolveKey":"",
    "EnigmaKey":"",
    "CaptchaFunKey":"",
    "InvizibleKey":"",

Set solver order depending on the provider

The bot automatically detects which solvers are available and use solvers in order from top to bottom. Auto-switching providers after two consecutive failures. Task stops after two complete cycles of attempting all configured solvers. You can change the order by rearranging them.

If a solver fails twice in a row, it is put on a 5-minute cooldown. After 5 minutes, one attempt is made to determine if the solver can be used again or if the cooldown is extended. Cooldowns are task-specific, not global

  • Current order by default: Invizible > BrightData > CapSolver > CapSolverProxy > CaptchaFun > Enigma

  • CapSolverProxy is same CapSolver, but use your own proxies for solving captcha

    "TmptSolverOrder":[
      "Invizible",
      "BrightData",
      "CapSolver",
      "CapSolverProxy",
      "CaptchaFun",
      "Enigma"
    ]
  },

Set captcha solver for additional captcha at login

Select provider to handle additional captcha during login. Support CapSolver and CaptchaFun. By default set Capsovler. 

    "CaptchaService":"CapSolver",

AYCD inbox support

AYCD guide: https://aycd.zendesk.com/hc/en-us/articles/14821162472855-Inbox-Mail-Task-Templates-Create-Mail-Task-Template

  • AycdInboxKey - set your Aycd Inbox key

  • AycdInboxTemplate - template name from AYCD

If the emails aren't forwarded or aren't a catchall you can use the default template. That will match the to: of the email to the mail credential in AYCD and pull the code.

So for example if you have 10k outlook emails in inbox that aren't forwarded, as longa s they have IMAP connected (so like oAuth signed in) the default template will work

    "AycdInboxKey":"",
    "AycdInboxTemplate":""
  },

Add SMS API providers & Modems.

How to find API of each provider explained in API providers & Modems. Note, that TextChestAsyncKey (512 lines) has separate SMS API.

  • Ejoin modem key should be added in the following format: ip:port:user:pass

To use multiple Ejoin use: ip1:port1:user1:pass1;;ip2:port2:user2:pass2

  • For the TextVerified provider, you need to enter API in the following format: "TextVerifiedKey": "email;api_key"

  • For Twilio API, you need to fill it in the following format: sid;token

 "Phones":{
    "SeatToolsKey":"",
    "WeRentSimsKey":"",
    "TextChestKey":"",
    "TextChestAsyncKey":"",
    "TextVerifiedKey":"",
    "SeatHeroesKey":"",
    "EjoinKey":"",
    "WiredKey":"",
    "SmsPassKey":"",
    "SimServiceKey":"",
    "TwilioKey":"",
    "QuickTextKey":""
    "SimWorldKey":"" 
  },

Auto reset password.

To activate password auto-reset during Accounts loginset true. If your account get locked, bot will automatically reset password during login:

Password reset updates the password in Accountsacross all TM regions

  "TicketMaster":{
    "AutoResetPassword":true

Sale wait delay (in seconds)

Supports live changes

When the bot detects a timer on the sale page, it will automatically refresh it using delay. As soon as the waiting room or queue appears, the bot will automatically start your tasks. The given delay is the interval in seconds for refreshing the drop page. For regular drops keep it default. 

    "SaleWaitDelay":60,

Queue check delay (in minutes)

Supports live changes

The interval for checking whether the queue token is still active during monitoring. If token is not active, the bot will re-enter the queue. By default setup (15), the bot will check the token every 15 minutes. You can reduce it if notice that your token expires too fast.

    "QueueCheckDelay":15,

Monitor limit for Internal monitoring

Number of ticket search attempts by monitor. If the ticket is not found within this number of attempts, it switches back to internal monitoring.

For MonitorLimit must be a specific value; -1 is not supported.

    "MonitorLimit":30,

Phone Activate Before Otp

  • For rotating lines

If you are using the WeRentSims provider's active lines (always online numbers), set "PhoneActivateBeforeOtp" to false

Attempts to activate phone before sending OTP. By default bot activate phone number after sending OTP. But when you activate that option bot will activate line before send OTP. In that way bot sends OTPs one at a time per port instead of all at once. 

    "PhoneActivateBeforeOtp":false,

Phone reset password for all accounts

Option to activate password reset via a phone number for all accounts. To reset pass via phone: SMS provider & phone number should be added in Accounts

true - enable password reset using phone numbers for all Accounts

false - bot will reset password via email (IMAP) or via phone for specific Accounts

  • PhoneResetPassword for all accounts:

Set only PhoneResetPassword true in Settings

  • PhoneResetPassword for specific accounts:

Set false in Settings + set PhoneResetPassword true in Accounts for specific accounts

    "PhoneResetPassword":true,

Randomize unlock codes

Option to randomize the order of codes for each task.

True - bot will use a shuffled code order

False - bot will proceed codes in order

    "RandomizeUnlockCodes":false,

Code retry delay & retry limit

Supports live changes

If the bot uses the wrong code by default during carting, it will stop the task. However, with this retry, the task will remain active for all retry attempts.

RetryLimit - Sets a limit on the number of retry attempts for entering unlock codes RetryDelay - Specifies the delay between code retry attempts

If you put code in tasks, but drop without code, bot will try option wihtout code and work.

    "CodeRetryDelay":4000,
    "CodeRetryLimit":1

Timeout waiting for OTP (in seconds)

Supports live changes

Option to specify timeout waiting for OTP. Default is 10 minutes (600 seconds). This is the delay before resending the OTP, as sometimes the second OTP arrives faster than the first one.

    "OtpWaitDelay":600,

Max OTP send attempts

Maximum number of OTP sending attempts.

    "MaxOtpSendAttempts":4,

Amount of attempts before OTP methods auto-switch: SMS ↔️ Email.

    "MaxOtpSwitchSendAttempts":2,

Timeout waiting for SMS OTP (in seconds)

Supports live changes

Option to specify timeout waiting for SMS OTP. Default is 1,5 minutes (90 seconds). This is the delay before resending the SMS OTP, as sometimes the second SMS OTP arrives faster than the first one.

    "OtpSmsWaitDelay":90,

Phone activation delay

Only for rotating lines

Timeout for the provider to activate the number. If activation does not occur, the bot moves on to the next task. If your provider has a slow activation process, you can increase the waiting timeout (delay).

    "PhoneActivationDelay":90,

OTP pre-send feature

To activate feature set in tasks file <PreSendOtp - true> for tasks you want pre-send OTP:

  • For events without timer set additionally true for <ForceQueueWait>

Set time when you want bot to pre-send OTP on tasks before waiting room/queue opened Your tasks should be launched by that time you set, so bot can pre-send OTP on tasks. As soon as queue/waiting room is up, tasks with pre-send OTP will instant join queue.

How to set time correctly? For example, drop start 1:00 if you set :25 bot will send OTP at 0:25.

  • Your tasks should be already launched by that time set in settings for pre-send

  • For waiting room which opened on :45, set 30-35 in settings

  • For waiting room which opened on :30, set 20-25 in settings

  • For API providers & Modems numbers with rotation you can set 30 minutes earlier due to delays: set 15 for :45 waiting room & set 00 for :30 waiting room

    "OtpPreSendMinutes":35,

Sms Poll Delay (in seconds)

Delay in checking new SMS OTP messages. Default value is 10 , do not recommend setting less.

    "SmsPollDelay":10,

Cart Block Delay

Supports live changes

Delay in seconds between requests from a single proxy to prevent 403 proxy error during carting. Feature activates if you do not have any backup proxies left to replace a banned one.

Error 403 (proxy) on carting explanation

This error occurs when one proxy is used for 2+ carts within a short period. TM temporarily bans the IP when you make multiple carts from that IP within a short timeframe. This is commonly seen when accounts are started at the same time for multiple events and start carting at the sale time.

    "CartBlockDelay":30,

Cart Attempt Delay

Supports live changes

Delay between cards in seconds to avoid possible account clip for multiple cart attempts.

For safety run recommend to use default value - 10 seconds

Extra safety setup for tests - 20 seconds

    "CartAttemptDelay": 10,

Cart Change Proxy

The option to change or not change the proxy during carting in case of a temporary proxy ban.

For safety run recommend to not change proxies - set false.

    "CartChangeProxy": false,

Cart Drop Start Delay [in ms]

Supports live changes

Delay between launching tasks for Cart drop module to not start all tasks at one time.

    "CartDropStartDelay":0,

Proxy rest delay (in sec)

Timeout for proxy after a ban. Default is 120 seconds.

    "ProxyRestDelay":120,

No proxy delay (in sec)

If the proxy is banned and no other proxies are available, the bot will retry the request after this time. Default is 120 seconds as well.

    "NoProxyDelay":120,

Row Amount after sorting

After all the sorting via SortOrder in tasks, the bot will take the 5 (by default) best available rows and choose a random one among them. This can potentially increase the ticket purchase success rate.

    "RndRowAmount":5

Share Queue OTP option

With <ShareQueueOtp> - true bot will use a single OTP to join the queues for multiple events on the same account. So if you've already sent an OTP from the account for one event, the bot will use the same OTP to join the queue for another event on the current instance.

Feature work across instances, so you can run events on several instances with ShareQueueOtp

    "ShareQueueOtp":false

Share Queue 🇪🇺

Use it only for queue without login. If queue with login set it false.

Option to automatically share the queue pass of the first task that has passed through the queue with other tasks. As a result, some tasks will pass through the queue immediately after the first pass.

    "ShareQueue":false,

Max Share Tasks 🇪🇺

The maximum number of tasks that the share queue option will apply to.

    "MaxShareTasks":5

Queue tasks limit

Tasks number limit on simultaneous entry in queue, work in same way for pre-send option. Recommend using this option if you're experiencing issues with slow OTP reading.

  • "QueueLimitTasks":true - activate option | "QueueLimitTasks":false - deactivate

  • "QueueTasksLimitAmount" - enter the number of tasks you want to join the queue at once

If set to :50, the bot will add up to 50 tasks to the queue at once. So when 1 task finishes, 1 new task enters

   "QueueLimitTasks":false,
   "QueueTasksLimitAmount":50,

Internal monitor poll

Mode for internal monitoring. Bot will periodically refresh for new places instead of waiting for pings about new places from TM. Can help with events where the standard mode doesn't work.

    "InternalMonitorPoll":true,

Internal monitor delay

Supports live changes

Internal monitor refresh frequency: in seconds

    "InternalMonitorDelay ":5

Autofill cvv for in-bot browser

Works only with in-bot browser and enabled Card loader feature

  • True - bot will autofill cvv during checkout on payment page

  • False - you'll need manually fill cvv

    "PaymentAutoCvv":false

Cart proxy switcher

Option to change cart proxy via reaction in discord webhook - a random proxy is selected from the file located at the path specified by CartProxyFile [setup guide]

  • CartProxyFile - path to the file with proxies for changing cart proxy

Random proxy will be selected from the file located at the path specified by CartProxyFile

By default, the path is set to data/cartProxies.txt, but you can place the file in any other folder — just make sure to provide the correct path so the bot can find it.

  • CartProxyAuto - set true to activate automatic proxy rotation. With this opetion bot after carting will automatically use proxy from the cartProxies.txt file for checkout.

   "CartProxyFile":"data/cartProxies.txt",
   "CartProxyAuto":false

UseOldDb option for cookies 🟡

Old feature, need to add line manual

With that option accounts cookies will be in Accounts.csv as before instead of .DB file. Not recommend to use.

    "UseOldDb":true

Queue positions in CSV

To activate exporting queue position results in CSV, set true. Bot will export ready CSV after queue in <Encore/logs/queue> folder:

Works for all queues and logs the position as soon as a task enters the queue.

   "QueueCsv":true,

Monitoring settings

Modify if necessary or keep the default recommended settings:

Retry delay [supports live changes]- retry interval, recommended to keep it default Monitor delay [supports live changes]- the interval for monitoring available tickets

  "RetryDelay":3500,
  "MonitorDelay":3000,

Display/hide event in success

Configure the option to display or hide the event ID in public success.

true - your carted event ID will be shown in members server server;

false - event ID will be hidden.

  "SendEventInfo":true,

Select Carting & Checkout option

"InbotBrowser":true,

"InbotBrowser":false,

  "InbotBrowser":true,

Inbot browser dimensions

You can change if need inbot browser dimensions - height & width

  "InbotBrowserHeight":768,
  "InbotBrowserWidth":1024,

Duplicate & server webhooks option to prevent rate limits

Use that options if you have issue with discord rate limit on webhooks. So you can open link in your browser and receive webhooks there.

How to find your discord webhook token and add it to URL?

  • Your webhook: https://discord.com/api/webhooks/1255645768287649876/8dAPzFzvGtcTpAwyBmVd6Z9V1_nh4vNVbOwXWJ4k9MsWSYd7VragPDtd

  • Purple part at the end of link is your Discord webhook token, which you will need to add to the link: https://encsoft.app/?token=8dAPzFzvGtcTpAwyBmVd6Z9V1_nh4vNVbOwXWJ4k9MsWSYd7VragPDtd

  • Option I. Duplication of webhooks to server. You will receive webhooks on discord and on server via link.

1) Set true in settings to activate discord webhook duplication to server. 

  "ServerWebhook":true,

2) Add your current Discord webhook token to the end of the link:

https://encsoft.app/?token=[your discord wh token]

3) Then open the resulting link in your browser. Webhooks will be send to discord and server.

  • Option II. Fully server webhooks - webhooks will directly to our server via link without Discord.

Option II fully bypass discord rate limit.

1) Add the Discord webhook token to the end of the link:

https://encsoft.app/?token=(your discord wh token)

2) Then, insert the resulting link as a webhook in your settings.

  "CartWebhook":"https://encsoft.app/?token=(your discord wh token)",
  "QueueWebhook":"https://encsoft.app/?token=(your discord wh token)"
https://encsoft.app/?token=(your discord wh token)

3) And open the link in your browser to receive webhooks. In this option, all webhooks will go only to the server. In this case, you will not encounter the Discord rate limit problem

You can also use mix setup. For example, use option I for carted webhook and option II for queue webhooks (since there are usually more of them).

IMAP polling (for gmail)

Special option if the standard gmail is experiencing issues on its side (like can't read OTP). Use only in case of problems, as this function is slower than standard. Set true to activate.

  "ImapPolling":false,

Set discord webhook for notifications

Server-side webhooks, in addition to bypassing Discord rate limits, have a checkmark feature that allows you to mark webhooks in case of checkout.

CartWebhook - successful carting;

QueueWebhook - successful passing queue;

AccountWebhook - successful 🇺🇸 TM Signup module registration notification;

MonitorWebhook - receive pings from monitors.

  "CartWebhook":"webhook link for carting notifications",
  "QueueWebhook":"webhook link for queue pass notifications"
  "AccountWebhook":"webhook link for signup notifications"
  "MonitorWebhook":"webhook for pings when monitor tasks start/stop
}

3. Save file and go ahead! 🚀

PreviousCaptcha proxyNextCaptcha harvester

Last updated