Use Videos as the hub. Open Featured Guide Videos for evergreen walkthroughs ranked by views, creator authority, and page intent. Open Update Videos for freshness-first Atlantis and patch coverage.
Quick Guide
Players want videos, but update videos and evergreen guide videos need different ranking rules and different written follow-up pages.
- Use Featured Guide Videos for evergreen guide intent.
- Use Update Videos for Atlantis, patch, bucket, and badge videos sorted by publish date first.
- Use Contact to suggest a better video for a specific page.
- Keep each embedded video paused by default and let the player choose when to play.
Choose a video lane
The two video lanes solve different jobs. Update Videos answer what changed recently. Featured Guide Videos answer how to play better after the update window moves on.
- Evergreen guides: Featured Guide Videos
- Latest updates: Update Videos
How videos feed written guides
A video earns a page slot only when it matches that page's player problem. Broad videos can support hub context, while exact route videos belong on the matching guide page.
- Tips video: Drain the Lake Tips & Tricks
- Video suggestion: Contact
Videos hub routing
| Lane | Ranking rule | Best use |
|---|---|---|
| Featured Guide Videos | Views, channel authority, page intent | Evergreen guides and walkthroughs |
| Update Videos | Freshness, views, page intent | Atlantis, patches, new buckets, new badges |
Drain the Lake Videos FAQ
Why combine featured guides and update videos?
They are both video-entry problems. One hub makes the system easier while separate child pages keep the ranking rules clear.
Does Videos replace written guides?
No. Videos provide visual context. Written guides still hold steps, tables, source status, and version caveats.
Sources & Data References
This hub is built from public game data, player videos, search results, competitor wiki review, and manual gameplay checks. Exact mechanics stay unconfirmed until an official source or in-game review supports them.
Used for the game identity, developer name, public stats, update timestamp, badges, and official play destination.
Used to spot beginner confusion, update coverage, route claims, hard-mode mentions, and topics that need written guide support.
Used to compare page structure, guide gaps, title patterns, content depth, FAQ coverage, and player-facing layouts.
Used to decide which source paths are safe to mention and which links should stay pending until the exact official URL is confirmed.
Used to judge whether a page solves a real player problem, whether a guide feels useful, and whether a claim needs another check.