Laijun docs
Everything the window does, in the order you will meet it. Ten minutes from a fresh install to a task that holds seats.
Install and activate
Laijun is one Windows program. Unpack it anywhere and open Laijun.exe.
- On the first start the window asks for your key. Paste the one you got on Discord.
- The key binds to this PC. One key runs on one PC at a time.
- Changing machines? Use Move key on the new PC — the old one is released.
%APPDATA%\laijun. Passwords, cookies and cards are stored sealed for your Windows user.The window
| Tab | What it holds |
|---|---|
| Tasks | Groups on the left, the tasks of the group you picked on the right. This is where you start and stop. |
| Accounts | Sign-ins the tasks may use: e-mail (or phone) and password, per site. |
| Proxies | Your proxy lists, in named groups, with a check for each group. |
| Info | Buyer details some checkouts ask for. |
| Code | Presale and member codes. |
| Card | Cards the payment window may type for you. |
| Sessions | Signed-in sessions: when each was saved, last proven alive, and when it runs out. |
| Checkouts | What your tasks have held and ordered. |
| Settings | Solver keys, the Discord webhook, the look of the window. |
Your first task
- Save who buys. An account in Accounts, or a signed-in session in Sessions (see below which a site wants).
- Make a group. In Tasks, press
+beside “Task groups”, name it and pick the site. - New task. Paste the event's link, pick a mode, the account or session, how many tickets, and what you want (dates, prices, areas).
- Start. The row shows each step the task takes. Held seats turn the row green — IN CART.
- Pay. Open the held order from the row; it opens in Laijun's payment window, signed in.
Accounts
An account is a sign-in a task can use by itself. Add them one at a time or paste many, one per line: email:password. Give each its site.
- TicketPlus signs in by phone. Write the number with its country code in front, no plus sign:
886912345678. - Sites that sign in through Google or Facebook (TixCraft) cannot use a password — save a session instead.
- A task that signs an account in saves the result on the Sessions page, so the next task does not sign in again.
Sessions
A session is a sign-in that already happened — the site's cookies. Use one where a site has no password sign-in, or where you would rather sign in by hand once.
Saving one from your browser
- Sign in to the site in your browser.
- Export the site's cookies with a cookie-export extension (a JSON list), or copy them as
name=value; name=value. - In Sessions, press Add session, pick the site, paste, and say how many hours it lasts if the cookies do not.
What the page shows
Last checked is the last time a task proved the session signed in. A task that uses a session refreshes its cookies and pushes its end out; a task that finds it signed out marks it expired. The bar runs from green to red as the end comes closer.
Proxies
Paste your lines into a named group, one per line, as host:port:user:pass (or host:port). Check tells you which answer.
- A task takes the line that matches its place in its group — task 1 the first line, task 2 the second, and round again.
- Where Cloudflare turns an exit away, the task moves to the group's next line by itself.
- An exit close to the site makes every step faster. For Taiwan's sites, a Taiwan or Hong Kong exit is the one to have.
| Site | Proxy |
|---|---|
| KKTIX | Needed — Cloudflare's check is solved through the task's own proxy. |
| TicketPlus | Not needed for a few tasks. |
| TixCraft, ibon | Use the same exit the session was saved on. |
| Interpark Global, Melon Global | Recommended once you run more than a couple of tasks. |
Settings and keys
Laijun earns most of what a site asks for by itself. A few things need a service of your own; put its key in Settings and press Test.
| Key | Used for |
|---|---|
| CapSolver | reCAPTCHA tokens on sign-ins that ask for one, and Cloudflare's check when Laijun's own solver does not get through. |
| EzCaptcha | An alternative for Cloudflare's check. |
| Discord webhook | Where held seats are announced. |
Tasks and groups
A group belongs to one site. Its tasks share nothing but that — each has its own link, mode, account and proxy line.
What a task can be told
| Field | How to write it |
|---|---|
| Link | The event's page as you see it in the browser. Some sites also take the event's code or number. |
| Tickets | How many in the one order. |
| Dates | Words of the show's date or name, in your order of preference: 12-20, 12-21. Empty = any. |
| Prices | The prices you take (2800, 3800) or a lowest and highest. Empty = any. |
| Areas | Words of the area's name, best first. A區+搖滾 = both words, !視線 = never this. |
| Code | A presale or member code, when the sale asks for one. |
| Start at | A time to begin; the task waits armed until then. |
| Count | Make this many copies of the task in one go. |
Wheelchair and other concession areas are never taken unless a word of yours names them.
Modes
The same name does the same job on every site that has it.
| Mode | What the task does |
|---|---|
| Buy | Waits for the sale and takes the seats. While nothing is free it keeps looking. |
| Buy + hold | Buys, then fills in the buyer form so the order waits for payment instead of lapsing. With “ATM transfer” it becomes a bank-transfer order. |
| Fast buy | As Buy, taking what another task of this PC just read instead of asking again. |
| Watch | Looks for seats and tells the Standby tasks. Buys nothing. |
| Standby | Signed in and silent until a Watch task calls. “+ code” reads the picture code ahead; “+ form” loads the ticket form ahead too. |
| Queue | Waits in a waiting room and brings back the pass. |
| Shared pass | Buys with a pass another task earned in the waiting room. |
| Sign in | Signs the account in, saves the session, stops. |
| Keep session | Looks at the account now and then so the sign-in stays alive. |
| Orders | Lists what the account holds. |
| Profile | Saves a name and ID number as the account's pre-fill. |
| Join fan club | Joins an organiser's fan club (some sales are for fans only). |
Site by site
| Site | Signs in with | Modes | After the hold |
|---|---|---|---|
| KKTIX | Session or account | Buy · Buy + hold · Sign in · Profile · Orders · Join fan club | Pay on the order's page, or ATM transfer |
| TixCraft | Session | Buy · Watch · Standby (+ code, + form) · Keep session · Orders | Cart, or card page |
| TicketPlus | Account (phone) | Buy · Sign in | Checkout in the payment window |
| ibon | Session | Buy · Queue · Keep session · Orders | Cart, ATM transfer, or card |
| Queue-it | — | Queue | The pass link |
Good to know
- KKTIX holds a fresh order for about three minutes; the buyer form stretches that to ten, a bank-transfer order to an hour. The account's mobile number must be verified on KKTIX.
- TicketPlus keeps one held order per account. A task lets go of an old one before it buys.
- TixCraft checks the browser before it shows anything: save the session from the browser you signed in with, and run the tasks on the same exit.
Watch and Standby
When a show is sold out and seats come back in ones and twos, ten tasks that each look every few seconds are ten times the noise for the same seats. So one task looks, and the rest wait.
- Make one Watch task for the event, with the areas and prices worth waking for.
- Make your buying tasks Standby — one per account — in the same group.
- Start them all. The Standby rows say Waiting For Restock; the Watch row says what it sees.
- When seats show, every Standby task is told where, and goes for them at once.
Standby + code has a picture code read before the wait, and Standby + form the ticket form of an area as well. Both cut steps out of the moment that counts.
Cloudflare
Some sites stand behind Cloudflare's “checking your browser” page. Laijun clears it with its own solver, which starts with the window.
- The check is solved on the task's own connection, so what it earns works for that task.
- It needs the task to have a proxy.
- A solve takes roughly twenty to forty seconds. Tasks do it when they start — long before the sale — so it costs nothing at the bell. Start your tasks early.
- If the solver fails three times on one exit, the task moves to the next proxy line; with a CapSolver or EzCaptcha key saved, that service is tried too.
Paying
Each task carries one choice for what happens after the seats are held.
| Choice | What happens |
|---|---|
| Stop in the cart | The task ends with the seats held. Open the row: the order opens in the payment window, signed in, and you pay as you would in a browser. |
| ATM transfer | The task places the order for bank transfer and shows the account to pay into. (ibon; KKTIX with Buy + hold.) |
| Card in Laijun | The order is handed in and the bank's card page opens in the payment window. A saved card can be typed for you; the code your bank sends is yours to enter. |
Notifications
Paste a Discord webhook into Settings and press Test. From then on, every hold is announced with the event, the seats, the price, the exit it went out on and the time left to pay.
What the row says
| Status | Meaning |
|---|---|
| Armed | Waiting for the start time you set. |
| Sleeping to … | Signed in and ready; waiting for the sale. |
| Watching / Waiting For Restock | Nothing free right now; the task goes on by itself. |
| In the queue / In line | The site's own line. “Ahead” counts who is in front where the site says. |
| IN CART | Seats held. Pay before the time shown runs out. |
| READY TO PAY | Held, with the checkout's details already filled in. |
| ORDERED | The order is placed; the row says how to pay it. |
| PASSED | Through a waiting room; the row holds the pass link. |
| Stopped — … | The task cannot go on. The sentence says why, and what to change. |
When a task stops
| The row says | What to do |
|---|---|
| …session is not signed in any more | Save a fresh session, or give the task an account to sign in with. |
| Cloudflare kept checking this exit | That proxy is not let through. Use another line or group. |
| Connection failed (proxy?) | Run Check on the proxy group; dead lines show there. |
| …wants this browser checked first | TixCraft: save the session again from your browser and use the same exit. |
| Mobile Verification Needed | KKTIX: verify the account's mobile number on the site first. |
| …no ticket type matches | Your prices or names leave nothing. The row lists what the event really has. |
| …asks for a code or an answer | Put the presale code, or the answer to the organiser's question, in the task's Code field. |
Still stuck? Every run writes a log beside your data. Bring the task's number to the Discord and someone will look with you.