JunkTok 5 Nights Guide
Quick answer
JunkTok is framed around five nights from Monday through Friday. This page tracks night tasks, viewer pressure, creature difficulty, modifiers, elimination rules, and unlocks without guessing unverified values.
JunkTok publicly frames its challenge around Monday through Friday. Until in-game capture or official community evidence exposes exact night rules, treat the five-night structure as confirmed and every threshold, unlock, creature value, and modifier detail as unverified.
Five-Night Tracking Table
| Night | Main task | Viewer threshold | Creature pressure | Modifiers | Elimination rule | Unlocks |
|---|---|---|---|---|---|---|
| Monday | TBD from verified run | TBD | TBD | TBD | TBD | TBD |
| Tuesday | TBD from verified run | TBD | TBD | TBD | TBD | TBD |
| Wednesday | TBD from verified run | TBD | TBD | TBD | TBD | TBD |
| Thursday | TBD from verified run | TBD | TBD | TBD | TBD | TBD |
| Friday | TBD from verified run | TBD | TBD | TBD | TBD | TBD |
What To Record Each Night
| Field | Record only when visible | Why it matters |
|---|---|---|
| Objective | Exact UI wording, target count, timer | Players need to know what changes between nights |
| Viewer state | Starting rank, gains, losses, night-end result | Ranking pressure may decide survival |
| Scan targets | Creature, Slime, Portal, location, danger | EyeAI routes need night-specific evidence |
| Modifier | Name, trigger, benefit, drawback | Modifiers can change route advice |
| Failure point | Death, missed request, low rank, timer, other | This separates real strategy from summaries |
| Unlock | Character, perk, upgrade, achievement, condition | Unlock methods should not be guessed |
Monday To Friday Evidence Rule
Do not fill a night row from memory or expectation. Use an in-game screenshot, visible UI text, Steam post, Steam Community report, or another checkable source. If a player report conflicts with in-game testing, keep the row as TBD until the conflict is resolved.
Current Test Route
Start with a clean Monday run and write down the first objective before moving. After each scan, donation request, rank change, death, or night clear, record what changed and what stayed the same. Repeat the same note format for Tuesday through Friday so the final guide can compare nights instead of listing isolated tips.
Night-By-Night Note Format
Use the same note format for every run. Write the night name first, then the objective text, then the route choice. After that, record each visible system change in order. A useful Monday note might say that the first scan target appeared before any donation request. A useful Friday note might say that viewer pressure changed before the final objective. The exact values are still TBD until tested, but the order of events is already worth capturing.
| Step | Question to answer | Good note |
|---|---|---|
| Start | What does the night ask for first? | Exact objective text and starting viewer state |
| First route | What did the team choose to do? | Scan route, split roles, or donation request choice |
| First danger | What interrupted the plan? | Creature, Slime, Portal, modifier, timer, or request |
| Rank check | Did viewers change? | Visible gain, loss, rank movement, or no change |
| End state | Why did the night clear or fail? | Clear condition, death, elimination, low rank, timeout |
Solo, Duo, And Trio Notes
Record player count with every night. Solo notes should explain what the player had to check manually: scan target, viewer pressure, donation request, and escape route. Duo notes should show which player watched ranking and which player handled scanning. Trio notes should show whether the extra player made the night safer or only added noise. Do not assume trio is easier until the same night has been tested across player counts.
Viewer Threshold Notes
The most important five-night question is whether each night has a different viewer requirement or elimination pressure. Do not write a threshold unless the run shows it clearly. If the game only shows a rank tier, record the tier instead of converting it to a number. If a donation request changes viewers, write the request text, the response, and the before-and-after viewer state.
Creature Difficulty Notes
Creature pressure should be tied to the night where it was seen. Record whether the danger appeared during a scan, after a donation request, near a Portal, or near the end of the route. If a creature name is unknown, use the visible category and location instead of inventing a name. When the exact creature name becomes visible, update the row and link the finding to the EyeAI scanning guide.
Modifier Notes
Modifiers can change the safest route, but only if their effect is documented. Record the modifier name, when it appeared, whether it helped or hurt the team, and whether it changed scan, viewer, or survival choices. If a modifier appears on several nights, keep each observation separate until the pattern is tested.
Split Plan
This page should stay as the single five-night overview until there is enough evidence for separate night pages. Do not create /night-one/, /night-two/, /night-three/, /night-four/, or /night-five/ pages just to hold empty tables. Split only when a night has its own tested objectives, threats, modifiers, viewer rule, and unlocks.
Failure Modes
- Filling Friday unlocks because another horror game has a similar structure.
- Writing a viewer threshold without a screenshot or visible rank result.
- Mixing solo and trio results in the same row without labeling player count.
- Naming a creature before the game exposes the name.
- Treating a modifier as a permanent rule after one run.
- Creating five separate night pages before any night has enough unique evidence.
Evidence Links
| Source | Use it for |
|---|---|
| Steam store | Official Monday-Friday framing and feature wording |
| Steam Community | Player reports, screenshots, launch posts, and night-specific findings |
Five Nights FAQ
Does JunkTok have five nights? The public framing is Monday through Friday, so this guide tracks five nights as the confirmed structure.
Are the night thresholds known? Not yet. Viewer thresholds, elimination rules, and unlock conditions should stay TBD until visible in the game or official community evidence.
Should each night get its own page? Not before there is enough tested information. A single overview is more useful than five empty pages.
Current Decision Rule
Update a row only when the note can answer three questions: which night was tested, what visible event changed, and what evidence supports the value. If any answer is missing, leave the cell as TBD and record the question for the next run.