JunkTok Viewer Ranking Guide
Quick answer
Viewer ranking is one of JunkTok's highest-value launch systems to track: players need to know how audience is gained, how donation requests work, and what ranking threshold keeps a run alive.
What Viewer Ranking Controls
Steam describes teams competing for the top viewer ranking while handling donation requests and paranormal objectives. That means viewer ranking should be treated as a core survival system, not just a score display.
What To Capture First
| Question | Field to record | Why it matters |
|---|---|---|
| How do you gain viewers? | Action, viewer gain, timing | This becomes the main optimization route |
| What are donation requests? | Request text, reward, penalty, timer | Players will search for whether requests are worth doing |
| What ranking is safe? | Threshold, night, solo/co-op state | This affects survival planning |
| What makes ranking drop? | Missed request, damage, slow scan, death | Prevents bad habits |
Ranking Log Template
| Night | Request or event | Viewer change | Rank change | Reward | Penalty | Best response |
|---|---|---|---|---|---|---|
| Monday | TBD | TBD | TBD | TBD | TBD | TBD |
Early Strategy
Do not treat every donation request as mandatory until the penalty is known. In a new run, the safer habit is to finish a scan route, check viewer pressure, then decide whether the current request is worth the risk.
What To Verify Next
This guide should track tested viewer gains, donation request examples, ranking thresholds, and solo/co-op differences for players searching how to get more viewers in JunkTok.
How To Test Viewer Gain
Viewer rank pressure needs its own evidence because it may connect several systems at once. A scan may raise audience. A donation request may add viewers but create danger. A death, missed scan, or ignored request may drop the team. Record the visible number or rank before and after each major action so the page can explain cause and effect instead of repeating that ranking exists.
The best current test is a short route with intentional notes. Start a run, write the starting viewer state, complete one scan, record the change, accept or skip one donation request, record the change, then end the night and note whether rank affected survival. Repeat the test in solo and co-op if possible.
Evidence Links
| Source | Use it for |
|---|---|
| Steam store | Official viewer rank and donation request wording |
| Steam Community | Player reports about requests, ranking thresholds, and elimination rules |
Viewer Ranking FAQ
Is viewer ranking optional? Treat it as required until tested. The official wording makes it sound tied to survival and nightly pressure.
Are donation requests always worth doing? Not by default. Judge each request by reward, penalty, time pressure, and danger, and keep unknown values marked until they are visible in-game.
What should this page become later? It should become a practical "how to get more viewers" guide with ranked actions, request examples, thresholds, and mistakes.
Ranking Failure Modes
- Recording only final rank without the action that changed it.
- Treating donation requests as flavor when they may affect survival.
- Missing whether solo, duo, and trio receive different request timing.
- Mixing audience gain advice into the general how-to-play page instead of giving it a dedicated answer.
Current Decision Rule
Track ranking changes as a sequence, not a single score. Write down the action before the change, the visible viewer result, and the night-end consequence. If a donation request gives viewers but causes a death, the guide should say that tradeoff clearly. That is the difference between a score page and an actual strategy page.