Thai Ticket Major
Thai Ticket Major General Guide
Last updated
Thai Ticket Major General Guide
Last updated
Click Create Task on the task page and configure your own task information, as shown in the figure
For the sale of ticket purchase configuration names, ticket info group needs to be configured. For details, see Ticket Info configuration Configuration instructions: After configuring the ticket info group, when purchasing tickets, the name/email in the ticket group information will be randomly selected to fill in. Each ticket group information will only be used once in one ticket. If the task does not configure ticket group information, the names of all tickets will be randomly generated.
The link needs to be configured with a specific release page link.
No need to configure profile
For the configuration of the price option, the recommended configuration range is a price range of 100 more. For example: for a ticket with a fare of 9900, you need to set 9900-10000. In this configuration, you can add a fare of 9900. Other priority configuration rules are common
Seat selection strategy: You can choose from three options: seats next to each other, seats in the same row, and any available seats. The difficulty is in order from difficult to easy. It is recommended to choose any seat.
The minimum quantity is set to 1. The quantity is the maximum purchase quantity for each order. It is subject to the actual page. Add it according to your needs.
Payment methods can be selected: Manual/Alipay/WeChat/UnionPay
The event time is configured according to actual needs. It is only necessary to configure the sales of different shows at the same time.
Area: configured according to the area on the specific map for sale, supporting priority, for example: D1, D2, D3, D4
Row: configured according to the number of rows on the specific seat map for sale, supporting priority, for example: A, B, C, D, E
It supports up to 5,000 tasks running at the same time. Generally speaking, it is recommended to run about 3,000 tasks at the same time.
An account needs to be configured. The ratio of the number of tasks to the number of accounts is 1:1. Each account requires a unique passport number. The same passport number can only purchase one order in a release.
Start all tasks 10-15 minutes in advance. For some popular sales events, it is recommended to start tasks 30-60 minutes in advance to allow accounts to log in first. Otherwise, starting tasks close to the release time will cause difficulty in logging in to the account.
Configure event notifications in the notification settings. The configured event notifications will send webhook information.
It is recommended to configure event notification: Reserved items in cart, checked out
If you need to view the pass queue link, you can additionally turn on the event notification: passed queue, passed queue (stopped)
Passed queue tasks are tasks that will continue the purchase process. Passed queue (stopped) means that the purchase process has been terminated for some reason after the task has passed the queue. You can click the pass queue link to make manual checkout urgently.
Choose a high-quality proxy. A poor-quality proxy may not be able to pass the queue.
The seat selection strategy needs to be configured according to different sales and different needs. If you are seats in the same row, it will be more difficult. It is recommended to give priority to "any seat" to lock the car faster.
After passing the queue in pro mode, the task will send a webhook message after the car is successfully locked. You need to manually click the checkout link in the webhook to pay manually. The locking time is generally 8 minutes. There is no need to manually log in to the account after passing the queue.
Log in to discord on the computer you use to check out in advance, confirm that the webhook configuration is correct, install chrome, and install the latest version of the Spider browser plug-in on chrome.
