Settings
Proper configuration is a key component of your success
Last updated
Proper configuration is a key component of your success
Last updated
ImapHost/ImapPort keep by default. For adding multiple IMAP use Multiple IMAPguide.
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.
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
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.
Current order by default: Invizible > BrightData > CapSolver > CapSolverProxy > Enigma
CapSolverProxy is same CapSolver, but use your own proxies for solving captcha
Select a single provider to handle additional captcha during login
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
To activate password auto-reset during Accounts loginset true. If your account get locked, bot will automatically reset password during login:
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.
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.
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 rotating lines
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.
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
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
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
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.
Maximum number of OTP sending attempts.
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.
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).
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
Delay in checking new SMS OTP messages. Default value is 10 , do not recommend setting less.
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.
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
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.
Supports live changes
Delay between launching tasks for Cart drop module to not start all tasks at one time.
Timeout for proxy after a ban. Default is 120 seconds.
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.
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.
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.
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.
The maximum number of tasks that the share queue option will apply to.
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":true - deactivate
"QueueTasksLimitAmount" - enter the number of tasks you want to join the queue at once
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.
Supports live changes
Internal monitor refresh frequency: in seconds
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.
To activate exporting queue position results in CSV, set true. Bot will export ready CSV after queue in <Encore/logs/queue> folder:
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
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.
To use In-bot browser auto-loginoption set:
"InbotBrowser":true,
To use Extenstion auto-login option set:
"InbotBrowser":false,
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.
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.
2) Add your current Discord webhook token to the end of the link:
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.
1) Add the Discord webhook token to the end of the link:
2) Then, insert the resulting link as a webhook in your settings.
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
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.
CartWebhook - successful carting;
QueueWebhook - successful passing queue;
AccountWebhook - successful TM Signup module registration notification;
MonitorWebhook - receive pings from monitors.
[CapSolverProxy support Captcha proxy]
[support Captcha proxy]
You can get a new API key by topping up your (leave API key field empty) or recharge if you have key already.
/ / [not supported]
Set only PhoneResetPassword true in
Set false in + set PhoneResetPassword true in for specific accounts
Only for
Purple part at the end of link is your Discord webhook token, which you will need to add to the link: ?token=8dAPzFzvGtcTpAwyBmVd6Z9V1_nh4vNVbOwXWJ4k9MsWSYd7VragPDtd
