Chain Coordinator

Chain Coordinator User Guide

Use the Chain Coordinator to see who attacks next, choose targets, and reserve milestone hits. This guide covers public members and tacticians. You do not need to install anything, create an account, or supply a Torn API key.

Attack one at a time. Follow the tactician's instructions. The application does not attack for you.

Start with the section for your role:

Open the board

Open the dashboard link shared by your faction and select Chain Coordinator. If you have been given a direct link ending in /chain, open that link.

You can view the queue, countdowns, target links, milestones, and completed attacks without signing in. Sign in only when you need to make changes or enter a drawing.

Understand your access

The application has two shared PINs. Your faction will tell you which one to use. Your application role comes from the PIN you enter; it does not automatically follow your rank or API permissions in Torn.

Action Not signed in Public PIN Tactician PIN
View the board and open Torn links Yes Yes Yes
Change the attack queue when unlocked No Yes Yes
Change the attack queue when locked No No Yes
Lock or unlock the board No No Yes
Enter or withdraw from an open milestone drawing No Yes, even when locked Yes, even when locked
Manage milestones, run drawings, or assign winners No No Yes
Change either PIN through the website No No No

Public editing applies to the shared queue, not just your own assignment. Coordinate changes with the tactician and avoid changing another member's assignment without agreement.

Sign in

  1. Select Sign in at the top of the board.
  2. Enter the five-digit PIN provided for your role.
  3. Select Sign in in the popup.
  4. Check the access indicator:
    • Public · editing: you can change the queue.
    • Public · read-only: you are signed in, but a tactician has locked queue editing.
    • Tactician: you can edit the queue and manage the board lock and milestones.

If the PIN is rejected, check it with the person who provided it. Repeated failed attempts temporarily block sign-in; wait 15 minutes if the app tells you to do so.

Select Sign out when finished, especially on a shared device. Sessions expire after 30 minutes without interaction. Simply leaving the page open does not keep editing access active.

Only the server owner can change PINs. If your role's PIN is changed, sign in again with the new PIN after the server has been restarted.

Public members: what to do during a chain

  1. Open the board and find your assignment in the queue.
  2. Watch the label beside your assignment:
    • NEXT ATTACK: you are responsible for the next attack, when the tactician calls for it.
    • ON DECK: one attacker is ahead of you. Be ready, but wait.
    • UPCOMING: wait for your turn.
  3. When you are next, check the assigned target and follow the tactician's timing instructions. A target may still be hospitalized or away from Torn.
  4. Select Attack Target ↗ in the NEXT ATTACK panel. This opens Torn in a new tab; log into Torn there if needed.
  5. Confirm that you are the assigned attacker and that the target is correct. Start the attack yourself in Torn when instructed.
  6. Report the outcome to the tactician and return to the board. If the attack failed or the target was unavailable, say so; do not mark it as successfully completed.
  7. If the queue has not advanced, let the tactician handle Complete & Next, unless they have asked you to do it and public editing is available.

Before selecting Complete & Next, reread the current NEXT ATTACK panel. API verification or another editor may already have advanced the queue. The button completes the assignment currently shown, which might now belong to someone else.

The board updates automatically. Opening an attack link does not reserve the target, perform an attack, or advance the queue.

If the board is locked

You can still view the board, open Torn links, and participate in open milestone drawings while signed in. Queue editing controls disappear or become unavailable.

You do not need to sign out or enter your PIN again when a tactician unlocks the board. Editing returns automatically if your session is still valid. If you need a queue change while locked, ask the tactician.

Tacticians: running a chain

Prepare the board

  1. Sign in with the tactician PIN and confirm the indicator says Tactician.
  2. Review any existing queue entries and milestone reservations. Saved assignments remain until someone changes them; opening the page does not start a new queue.
  3. Decide whether members should edit the queue. Select Lock board to restrict queue editing to tacticians, or Unlock board to allow signed-in public members to help.
  4. Add the first few assignments and put them in the intended order.
  5. Tell members how you will announce the attack window and who should report completions.

Any signed-in tactician can lock or unlock the board. Locking does not sign public members out. Sign out only ends your own session and leaves the board's lock state unchanged.

Manage each turn

  1. Confirm the NEXT ATTACK member is ready and their target is suitable.
  2. Watch the countdown and call the attack at the time you choose. The faction may normally wait until roughly one minute remains, but the countdown is advisory.
  3. Wait for the member's result. If API verification confirms an eligible chain-extending attack, the queue can advance automatically.
  4. If the member confirms completion and the queue has not advanced, use Complete & Next for that assignment. This advances immediately without waiting for Torn's API.
  5. If the member cannot take the turn, use Skip / Defer, or edit the assignment as appropriate.
  6. Confirm the newly promoted NEXT ATTACK member before calling the next turn.

Add and change queue assignments

These controls are available to tacticians at all times, and to signed-in public members while the board is unlocked.

Add an assignment

  1. Select + Add Assignment.
  2. Search for and select the Friendly faction member who will attack.
  3. Search for and select the Enemy faction member they should attack.
  4. Review the enemy's location, hospital information, and last confirmed update.
  5. Select Save Assignment. The new assignment is added to the end of the queue.

You can also select Assign target beside an enemy in the availability section to open the assignment form with that target selected.

The same target is normally blocked from appearing in multiple active assignments. Use Allow this target in multiple active queue positions only when the tactician deliberately wants that target reused.

Reorder, edit, complete, or defer

Control What it does
Drag a queue row Moves it to another position; the order saves immediately.
↑ / ↓ Moves a row one position; useful on phones or with a keyboard.
Edit Changes the attacker or target. Select Save Assignment to apply it.
Delete Removes an active or deferred assignment. Use Skip / Defer if you may want to restore it.
Complete & Next Moves the current assignment to Completed attacks and promotes the next attacker immediately.
Skip / Defer Removes the current assignment from the active queue without marking it completed.
Restore to end In Skipped / deferred, returns that assignment to the end of the queue.

Reordering needs no separate Save button. If another editor changed the board first, the app refreshes the saved state and asks you to review your change. Check the new order before trying again.

Expand Completed attacks to check results:

Later API confirmation of a manual completion does not advance the queue a second time. Completed history cannot be edited or deleted through the queue controls.

Read timers and target availability

The chain countdown updates every second using the most recent API observation. It is a local estimate between API updates.

Estimated time remaining Display
Above 2 minutes Normal
2:00–1:01 Prepare
1:00–0:31 Attack window
0:30–0:16 Urgent
0:15–0:01 Critical
0:00 Expired estimate — awaiting confirmation

The app handles warm-up and cooldown separately. No active chain means the last confirmed chain count was zero; it does not mean faction API access was denied.

Use Enemy availability to find confirmed Okay members in Torn or enemies approaching hospital release. Hospitalized enemies can be assigned ahead of time.

Expected Release — Awaiting Confirmation means the estimated hospital timer reached zero. It does not confirm the enemy is available. Wait for updated status or check Torn before attacking. Traveling and abroad targets also need their location checked.

Check whether information is current

The Live connection indicator means the browser is receiving board updates. It does not by itself mean Torn's API information is fresh.

Expand API Live / Inactive / Error for the last successful chain update, attack-verification status, and any error details.

Manual queue controls remain usable during a Torn API outage. If the browser itself is disconnected, wait for reconnection before relying on the displayed order or assuming a change saved.

Public members: enter a milestone drawing

A milestone reserves an actual chain hit, such as hit #100. Queue position 4 is not chain hit #4. Milestone reservations and the attack queue are separate.

  1. Sign in with the public PIN.
  2. Select Milestone Tracker, View Milestones ↗, or Enter Drawing ↗ in the status panel.
  3. Open the milestone marked Drawing Open.
  4. Under Enter this drawing, select your own faction member name.
  5. Select Enter drawing and confirm that your name appears in the participants list.
  6. To leave before entries close, select Withdraw beside your name.

You can enter open drawings even when the attack board is locked. Each member gets one entry per drawing. Entries do not automatically carry over to future drawings, and previous winners can enter new ones.

Names use the honor system: the shared PIN does not identify your Torn account. The interface allows signed-in members to withdraw listed entries, so take care to withdraw only your own unless the tactician has asked you to help.

Once entries close, public members cannot join or withdraw. If your name is missing from the selection, first check whether you are already entered; otherwise ask the tactician to check the friendly roster.

When the drawing starts

Watch the countdown and winner reveal. Skip animation stops the motion while you wait for the same shared result; it does not change the winner or reveal them early. Refreshing does not reroll the drawing.

If you win, coordinate with the tactician. Winning does not add you to the queue or give you permission to attack immediately. The tactician still arranges the actual attack order and timing.

Tacticians: manage milestones

Run a drawing

  1. Open Milestone Tracker and expand the milestone you want to reserve.
  2. Select Open drawing, then tell members entries are open.
  3. Review the participants. Select Close entries when the entry period is over.
  4. If necessary, use Remove entry to remove an invalid entry before starting.
  5. Select Start drawing. At least one participant is required. Starting also closes entries if you have not already done so.
  6. Wait for the winner reveal. Only one drawing can run at a time.
  7. Arrange the winner's attacker/target assignment in the normal queue and tell them when to attack.

Open drawings well before the milestone hit. A fresh chain update reaching that hit marks the milestone completed and closes its entries.

Assign a member without a drawing

  1. Expand the milestone.
  2. Under Assign manually, choose the faction member.
  3. Select Assign member.
  4. Arrange their attack separately in the queue.

If someone is already assigned, the form is labelled Override assignment. Using it replaces the current reservation; assigning manually also cancels an open or closed drawing for that milestone. Previous assignment history is retained.

Change or reuse milestones

Control When to use it
Create milestone Add a chain hit number that is not already configured.
Chain hit number / Enabled / Save configuration Change an unused hit number or enable/disable a milestone. Cancel an active drawing before disabling it. Reset an existing reservation before changing its hit number.
Cancel drawing Stop an open or closed drawing before it starts.
Open new drawing (override) Replace an existing reservation with a new drawing for an enabled, uncompleted milestone.
Reset reservation Clear the current reservation and drawing so the milestone can be reused. History remains available.
Remove milestone Remove the milestone from the active list while retaining its history.

A drawing already in progress must finish before its milestone can be changed. Resetting a completed milestone requires fresh API confirmation that a new or inactive chain is below that milestone's hit number.

Expand Winner & drawing history to review earlier results. Completed · chain hit reached confirms chain progress only; it does not prove the reserved member performed that hit.

Quick troubleshooting

What you see What to do
Read-only and no editing controls Sign in if you need to edit or enter a drawing.
Public · read-only You are signed in and the board is locked. Ask a tactician for queue changes.
Controls disappear while you are editing Check whether the board was locked or your session expired. Review the saved state before retrying.
A queue-change or stale-update message Another change arrived first. Review the refreshed queue, reopen the form if needed, and retry only if the change is still appropriate.
Missing friendly members or enemies Wait for a successful roster update and tell the tactician if it persists.
Your target is still hospitalized at zero The timer is an estimate. Wait for confirmation or ask the tactician for a different target.
Disconnected · reconnecting Wait for automatic reconnection. Check the refreshed queue before acting.
Verification unavailable but the board works Report the result to the tactician; manual completion can continue while the host checks the API issue.
A milestone is completed but its winner has not attacked Completion tracks the chain hit, not the winner's identity. Ask the tactician to review what happened.

When reporting a problem, include the visible error, the time it happened, and what you were trying to do. Do not share PINs or API keys in screenshots.