JunkTok Co-op Guide
Quick answer
JunkTok supports one to three players. The useful co-op split is scanner, ranking watcher, and flexible support, adjusted for solo, duo, or trio play.
Choosing Group Size
| Setup | Best use | Main risk |
|---|---|---|
| Solo | Learn scan targets and UI timing without team noise | Missing viewer pressure while focused on scans |
| Duo | Split scanning and ranking calls | Both players may chase the same objective |
| Trio | Cover scan, viewer, and support roles | Too much chatter can hide important callouts |
Role Split
| Role | Job | Callout format |
|---|---|---|
| Scanner | Find Creatures, Slime, and Portals | Target, location, danger |
| Ranking watcher | Track donation requests and viewer ranking | Request, timer, reward or penalty |
| Support | Protect the route and test build effects | Ability, perk, upgrade, cooldown |
Player-Count Co-op Test
Run one solo attempt, one duo attempt, and one trio attempt if possible. Record whether enemy pressure, scan timing, donation requests, or viewer ranking thresholds change with player count.
Mistakes That Actually Hurt
- Calling only enemy danger and forgetting viewer ranking pressure.
- Letting every player scan while no one watches donation requests.
- Assuming trio is automatically safer before testing scaling.
- Ranking a character as best before checking whether the ability helps solo and co-op differently.
What To Verify Next
As more runs are documented, this page should include recommended team roles by night, best trio compositions, and a solo survival checklist.
How To Test Player Count
The most useful co-op update is not a generic "play with friends" tip. It is a comparison of what changes between solo, duo, and trio. Run the same early route in each setup and record whether scan timing, target danger, viewer rank pressure, donation request frequency, or enemy behavior changes. If nothing changes, say that clearly. If something scales, put the scaling note in the table instead of hiding it in prose.
Evidence Links
| Source | Use it for |
|---|---|
| Steam store | Official one-to-three participant wording |
| Steam Community | Player reports about co-op stability, matchmaking, and team size |
Duo Plan
A duo should avoid both players doing the same job. Put one player on scan discovery and one player on viewer pressure. The scan player calls the target category and danger. The rank player calls donation requests, timer pressure, and whether the team can afford to delay. If the duo fails, record whether the failure came from missing scans, losing viewers, dying during a route, or misunderstanding a build choice.
Trio Plan
A trio can cover more ground, but only if callouts stay short. A good trio has scanner, rank watcher, and support. The support player should not wander randomly; they should test character abilities, cover scan routes, and call upgrade or perk changes. This page should identify whether trio scaling changes the safest route once repeated runs show the pattern.
Co-op FAQ
Is trio always best? Not automatically. Trio may be stronger if roles matter, but it can be worse if danger scales or communication becomes noisy.
Can solo players use this guide? Yes. Solo play uses the same roles in sequence: scan first, rank pressure second, build choices third.
What should a team record? Record role, night, target, request, viewer change, death or failure point, and the build choice involved.
Current Decision Rule
If a team is losing runs before Friday, do not change every role at once. Change one variable per attempt: first communication, then scan priority, then donation request handling, then build choice. That makes the failure readable. A guide based on one changed variable is more useful than a broad tip that says "coordinate better" without showing what coordination fixed.