How To Play JunkTok: Beginner Guide & First Run Tips
Quick answer
Start a run, choose a character, read the active objective, scan Creatures, Slime, or Portals for EyeAI, watch viewer ranking pressure, use upgrades against the problem blocking progress, and carry the same evidence format through all five nights.
JunkTok is available on Steam now. This guide explains the playable loop after onboarding: start a run, read the current night objective, identify EyeAI scan targets, keep viewer pressure visible, choose upgrades around the problem the run creates, and repeat that evidence through Friday.
New after the tutorial? Start with the Beginner Guide for a first-run checklist, then return here for the broader loop across solo, duo, trio, EyeAI, viewer ranking, and five-night progression.
Core Loop
- Start a run with a character, the current random perk, and any visible run modifier.
- Enter Monday and read the active objective before splitting up or chasing side events.
- Identify official EyeAI targets: Creatures, Slime, and Portals.
- Scan the safest visible target first, then record what changed on the UI.
- Watch donation requests, chat reaction, and viewer ranking pressure while the team works.
- Use level-up upgrades and character abilities to solve the problem the run is actually creating.
- Repeat the same evidence format through Friday instead of assuming every night behaves like Monday.
The short version: tutorial completed, character chosen, perk or upgrade checked, objective scanned, EyeAI target confirmed, viewer ranking watched, and five nights survived.
Core System Priorities
| Priority | What to learn | Verification state |
|---|---|---|
| Objective text | What the current night asks the team to do | Pending in-game capture |
| Scan recognition | What a Creature, Slime, and Portal look like | Official target types confirmed; exact examples pending |
| Viewer pressure | When donation requests and ranking changes appear | System confirmed; thresholds pending |
| Build choices | Which character, perk, or upgrade changes the run | System confirmed; exact values pending |
| Route safety | Whether solo, duo, or trio changes the safest first scan | Pending repeated runs |
| Night escalation | What changes from Monday through Friday | Five-night structure confirmed; exact changes pending |
Solo, Duo, And Trio Route
Solo players should keep the route narrow. Read the objective, identify one nearby EyeAI target, scan it, then check viewer ranking before moving deeper into the night. Do not try to test every perk, request, and scan target in one run.
Duo players should split attention, not disappear from each other. One player leads target recognition and scanning while the other watches donation requests, chat reaction, and ranking movement. Swap roles after a failed scan or a new upgrade so both players understand the pressure points.
Trio players can cover the most information if each role stays clear: scanner, viewer watcher, and support. The support player should call character ability use, perk or upgrade changes, and route danger instead of wandering for unrelated discoveries.
Mistakes That Actually Hurt
- Chasing donation requests before your team understands scan targets.
- Ranking perks or upgrades before the game shows exact values.
- Treating Monday advice as Friday advice without checking what escalates.
- Splitting a trio so far apart that scan calls and viewer pressure stop being shared information.
Night-by-Night Evidence
The Monday-through-Friday structure is the backbone of the guide. Record the objective shown at the start of each night, the first scan target you can safely reach, when viewer rank pressure appears, and whether the team is removed or penalized for falling behind. Do not merge all nights into one general tip list. Players will want to know what changes on Tuesday, Wednesday, Thursday, and Friday.
For each night, capture the same fields: starting objective, common scan target, first dangerous event, donation request timing, useful character ability, useful perk, upgrade moment, and exit condition. Mark a field verified only when it comes from visible in-game text, the public Steam page, an official post, or checkable player evidence.
Evidence Links
| Source | Use it for |
|---|---|
| Steam store | Official feature list and one-to-three player wording |
| Steam Community | Player questions, screenshots, and post-launch route reports |
How To Play FAQ
What should I learn first? Learn what counts as a scan target before optimizing builds. A player who can identify a Creature, Slime, and Portal will understand the rest of the run faster.
How should a team structure a run? Read the night objective, choose the safest visible EyeAI target, keep one player aware of viewer ranking pressure, and make upgrade choices from the problem that appears first.
Should I chase every donation request? Not at first. Record the reward and penalty before deciding whether a request is worth breaking your scan route.
What is verified right now? Steam confirms the one-to-three player structure, Monday-through-Friday nights, EyeAI scans for Creatures, Slime, and Portals, viewer ranking pressure, donation requests, characters with unique abilities, random perks, and level-up upgrades. Exact thresholds, values, and route timings still need in-game evidence.
When should builds matter? Builds matter once you know what problem the run is creating. If the team is failing scans, value scan safety. If the team is losing viewers, value audience and request tools. If the team is dying late, value survival and repositioning.
Route Failure Modes
- Ignoring the UI objective because the team is exploring randomly.
- Splitting the group so far that scan calls and viewer pressure stop being shared.
- Treating one night as proof that the same route works through Friday.
- Publishing perk, upgrade, or viewer request advice without recording the exact wording.