JunkTok Beginner Guide: First Run Walkthrough
Quick answer
After the tutorial, start one focused run: choose a character, read the Monday objective, confirm the active perk or modifier, complete one safe EyeAI scan, watch donation and viewer ranking pressure, then spend upgrades only after you know what blocked progress.
This beginner guide starts after the tutorial. It does not guess the tutorial script, exact values, or best builds. Use it to make your first run readable: learn what the game asks on Monday, complete one EyeAI scan if it is safe, watch how the audience reacts, and record the first upgrade decision before trying to optimize.
After The Tutorial: Your First Run
- Choose one character and read the ability text before the run starts.
- Confirm the visible perk, modifier, or upgrade state instead of assuming every run begins the same way.
- Enter Monday and read the active objective before splitting up or chasing side events.
- Identify the nearest safe EyeAI target: Creature, Slime, or Portal.
- Complete one scan, then check donation requests, chat reaction, and viewer ranking movement.
- Spend upgrades on the problem that actually stopped progress: scanning, viewer pressure, survival, or recovery.
- Carry the same note format into Tuesday, Wednesday, Thursday, and Friday so later choices are based on evidence.
Need the system pages while you learn? Use How To Play for the full loop, EyeAI Scanning for scan targets, Viewer Ranking for audience pressure, and Characters, Perks, and Upgrades for build notes.
First-Run Checklist
| Step | What to check | Why it matters |
|---|---|---|
| Character | Ability text and any visible starting state | Prevents guessing what your run can solve |
| Monday objective | Exact objective wording at the start of the night | Keeps the team focused on the active task |
| Perk or modifier | Any random perk, modifier, or upgrade state shown before action begins | Separates repeatable advice from one-run luck |
| EyeAI target | Creature, Slime, or Portal | Builds scan recognition before route optimization |
| Viewer pressure | Donation requests, chat reaction, and ranking movement | Shows when audience systems begin affecting decisions |
| Upgrade point | What failed before the upgrade appeared | Makes the first build decision easier to explain |
What To Learn First
Learn target recognition before build ranking. A beginner who can identify one Creature, one Slime clue, or one Portal safely will understand the rest of the run faster than a player copying an unverified upgrade order.
Treat donation requests as information during the first run. Record the request, reward, penalty, and timing before deciding whether it is worth breaking your route.
Keep the group close enough to share calls. Solo players should stay narrow, duo players should split attention between scanning and viewer pressure, and trio players should assign one scanner, one viewer watcher, and one support caller.
What Not To Guess Yet
- Exact tutorial handoff text.
- Character, perk, or upgrade values.
- Donation thresholds or viewer ranking formulas.
- The safest route for every night.
- Whether Monday advice still works on Friday.
Beginner Evidence Log
| Field | Monday note | Later-night note |
|---|---|---|
| Objective | Write the exact text shown | Record what changed |
| First scan target | Creature / Slime / Portal | Compare risk and reward |
| Viewer pressure | First donation or ranking movement | Note timing changes |
| Upgrade moment | What problem appeared first | Whether the upgrade solved it |
| Failure reason | Scan, audience, survival, or recovery | Whether the same problem repeated |
Beginner FAQ
What should I do immediately after the tutorial? Pick one character, record the starting perk or modifier, read Monday's objective, complete one safe EyeAI scan, and check whether viewer ranking or donation pressure changed.
Should I chase every donation request? Not on the first run. Record the request and visible result before deciding whether it is worth leaving the scan route.
When should I care about builds? 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.
What is verified right now? Steam confirms one-to-three player co-op, 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.
First-Run Failure Modes
- Ignoring the UI objective because the team is exploring randomly.
- Splitting the group before anyone knows how risky scan targets are.
- Treating one failed scan as proof that a target is impossible.
- Forgetting to record the exact wording of the first perk, upgrade, or viewer request.