LAIJUN DOCS

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.

  1. On the first start the window asks for your key. Paste the one you got on Discord.
  2. The key binds to this PC. One key runs on one PC at a time.
  3. Changing machines? Use Move key on the new PC — the old one is released.
Where your data lives. Accounts, sessions, proxies, tasks and logs are kept on your PC, in %APPDATA%\laijun. Passwords, cookies and cards are stored sealed for your Windows user.

The window

TabWhat it holds
TasksGroups on the left, the tasks of the group you picked on the right. This is where you start and stop.
AccountsSign-ins the tasks may use: e-mail (or phone) and password, per site.
ProxiesYour proxy lists, in named groups, with a check for each group.
InfoBuyer details some checkouts ask for.
CodePresale and member codes.
CardCards the payment window may type for you.
SessionsSigned-in sessions: when each was saved, last proven alive, and when it runs out.
CheckoutsWhat your tasks have held and ordered.
SettingsSolver keys, the Discord webhook, the look of the window.

Your first task

  1. Save who buys. An account in Accounts, or a signed-in session in Sessions (see below which a site wants).
  2. Make a group. In Tasks, press + beside “Task groups”, name it and pick the site.
  3. New task. Paste the event's link, pick a mode, the account or session, how many tickets, and what you want (dates, prices, areas).
  4. Start. The row shows each step the task takes. Held seats turn the row green — IN CART.
  5. 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

  1. Sign in to the site in your browser.
  2. Export the site's cookies with a cookie-export extension (a JSON list), or copy them as name=value; name=value.
  3. 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.
SiteProxy
KKTIXNeeded — Cloudflare's check is solved through the task's own proxy.
TicketPlusNot needed for a few tasks.
TixCraft, ibonUse the same exit the session was saved on.
Interpark Global, Melon GlobalRecommended 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.

KeyUsed for
CapSolverreCAPTCHA tokens on sign-ins that ask for one, and Cloudflare's check when Laijun's own solver does not get through.
EzCaptchaAn alternative for Cloudflare's check.
Discord webhookWhere 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

FieldHow to write it
LinkThe event's page as you see it in the browser. Some sites also take the event's code or number.
TicketsHow many in the one order.
DatesWords of the show's date or name, in your order of preference: 12-20, 12-21. Empty = any.
PricesThe prices you take (2800, 3800) or a lowest and highest. Empty = any.
AreasWords of the area's name, best first. A區+搖滾 = both words, !視線 = never this.
CodeA presale or member code, when the sale asks for one.
Start atA time to begin; the task waits armed until then.
CountMake 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.

ModeWhat the task does
BuyWaits for the sale and takes the seats. While nothing is free it keeps looking.
Buy + holdBuys, 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 buyAs Buy, taking what another task of this PC just read instead of asking again.
WatchLooks for seats and tells the Standby tasks. Buys nothing.
StandbySigned in and silent until a Watch task calls. “+ code” reads the picture code ahead; “+ form” loads the ticket form ahead too.
QueueWaits in a waiting room and brings back the pass.
Shared passBuys with a pass another task earned in the waiting room.
Sign inSigns the account in, saves the session, stops.
Keep sessionLooks at the account now and then so the sign-in stays alive.
OrdersLists what the account holds.
ProfileSaves a name and ID number as the account's pre-fill.
Join fan clubJoins an organiser's fan club (some sales are for fans only).

Site by site

SiteSigns in withModesAfter the hold
KKTIXSession or accountBuy · Buy + hold · Sign in · Profile · Orders · Join fan clubPay on the order's page, or ATM transfer
TixCraftSessionBuy · Watch · Standby (+ code, + form) · Keep session · OrdersCart, or card page
TicketPlusAccount (phone)Buy · Sign inCheckout in the payment window
ibonSessionBuy · Queue · Keep session · OrdersCart, ATM transfer, or card
Queue-it—QueueThe 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.

  1. Make one Watch task for the event, with the areas and prices worth waking for.
  2. Make your buying tasks Standby — one per account — in the same group.
  3. Start them all. The Standby rows say Waiting For Restock; the Watch row says what it sees.
  4. 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.

ChoiceWhat happens
Stop in the cartThe 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 transferThe task places the order for bank transfer and shows the account to pay into. (ibon; KKTIX with Buy + hold.)
Card in LaijunThe 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.
Mind the clock. A hold is a countdown. The row and the Discord message both say how long it lasts.

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

StatusMeaning
ArmedWaiting for the start time you set.
Sleeping to …Signed in and ready; waiting for the sale.
Watching / Waiting For RestockNothing free right now; the task goes on by itself.
In the queue / In lineThe site's own line. “Ahead” counts who is in front where the site says.
IN CARTSeats held. Pay before the time shown runs out.
READY TO PAYHeld, with the checkout's details already filled in.
ORDEREDThe order is placed; the row says how to pay it.
PASSEDThrough 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 saysWhat to do
…session is not signed in any moreSave a fresh session, or give the task an account to sign in with.
Cloudflare kept checking this exitThat 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 firstTixCraft: save the session again from your browser and use the same exit.
Mobile Verification NeededKKTIX: verify the account's mobile number on the site first.
…no ticket type matchesYour prices or names leave nothing. The row lists what the event really has.
…asks for a code or an answerPut 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.