Regia Plays · Existing-library strategy

Resident Evil Requiem: turn the library into a viewer journey

A detailed, evidence-led plan for extracting more discovery, watch time, and series continuation from the Resident Evil Requiem videos already live—without misleading packaging, fake urgency, or a content dump.

Bottom line: do not solve this with more tags or more uploads. The highest-leverage repair is a connected system: specific event packaging → one exact destination → clean episode/playlist continuation → measurement before the next release. The current library already contains 13 long-form RE9 parts and 4 Shorts. It needs clearer entry points and fewer generic “session” packages.
17
public RE9 uploads audited

13 long-form parts + 4 Shorts in the API snapshot.

4
published Shorts

The two older story-led Shorts earned the only meaningful early signal; the two newest were too fresh to diagnose.

1 route
every viewer needs next

Short → matching episode; episode → next episode + chronological playlist.

1. What the evidence says now

This audit is a packaging and structure audit, not a claim that any individual video has “failed.” The channel is very early and the latest Shorts are only hours old in the captured data. YouTube Analytics retention, traffic-source, and viewed-vs-swiped data were not available through the current reporting read at audit time; do not substitute guesses for those metrics.

Shorts signal worth respecting

“She Wasn’t the Girl You Met…”: 880 views / 16 likes at snapshot. “Every Country Wanted This Virus…”: 756 / 4. Both package a concrete story surprise or lore claim rather than generic gameplay.

Do not over-read the newest pair

Escape the Care Center and Who Is Trapped Inside? were at 2 and 3 views soon after release. Four Shorts landed in about eight hours. That is insufficient evidence of a bad hook and makes simultaneous testing impossible.

Long-form entry problem

Several long parts have useful story or setting labels. Others are “Full/Survival Horror Session,” which describes a format rather than a reason for a stranger to click. Every existing VOD can remain live; the repair is better packaging and clear onward routing.

Market signal, not imitation: a public YouTube search for “Resident Evil Requiem” is dominated by very short character reactions, specific mechanics/discoveries, lore revelations, scares, and named moments—not generic clips. Use that only to decide what to look for in your own footage. Never borrow another creator’s footage, title claims, character names, or spoilers unless the exact beat is visibly present in Regia Plays footage.

Specific audit defects to repair before making more content

The mistake is not too few links; it is offering many competing exits. Each asset should have one primary continuation. Secondary links exist only to preserve the series route.

SurfaceUseExact limit / setupWhy
Short related videoLink the exact full episode that contains the moment.1 related video per Short. Example: Care Center / observation-room Shorts → Part 4. Lore/Emily moments → Part 10 if that is the verified source.It is the clearest in-player bridge. YouTube says the control can showcase a Video, Short, or Live in the Shorts player.
Short descriptionPlain-language fallback: “Watch the full Part 4: [URL].”1 full-episode URL; optionally one playlist URL only if it does not bury the primary link.Useful fallback; it is not a substitute for Related video.
Long-video end screenSpecific next part, full chronological playlist, Subscribe.3 elements, not four: Next Part + RE9 playlist + Subscribe. Start 15–20 seconds before a natural end.One decision is obvious; the playlist saves viewers who want to start earlier.
Info cardsOne contextual playlist/video card at a natural transition.0–2 used deliberately; YouTube technically permits up to 5. Never stack them and do not put one in the end-screen window.Cards interrupt. Use when the viewer has a reason to choose, not because a slot exists.
Long-video descriptionNext episode + series playlist, after the first two factual lines.2 internal links max: Next Part and “Start the series / full playlist.”Creates a readable route without looking like link spam.
Pinned commentOne natural question plus the same primary route.1 pinned comment, only where comments are enabled and the question is real.Conversation first; link second. Do not paste the same engagement-bait comment everywhere.
Long-form end-screen rule: YouTube allows end screens in the last 5–20 seconds of a video, requires a video to be at least 25 seconds long, and allows up to four elements on standard 16:9. Use only three for this series. Cards and video watermarks are suppressed during the end-screen period, so never schedule a card there.

Recommended series topology

  1. Short: an event from Part N → Part N via Related video.
  2. Part N: end screen → Part N+1 + the RE9 chronological playlist + Subscribe.
  3. Part 13: end screen → a “best starting point” (Part 1 or an eventual story-recap) + chronological playlist + Subscribe.
  4. Playlist: manual oldest-to-newest order. Do not describe it as auto/newest-first if the viewer needs a story sequence.

3. Metadata that actually matters

Title: build an entry point, not a file name

YouTube permits titles up to 100 characters. That is a ceiling, not a target. For this small channel, a title should perform two jobs: tell search what game this is, and make a browse viewer understand the specific promise before “Part X.”

Best long-form formula

[specific visible event] | Resident Evil Requiem PS5 Gameplay – Part N

Use only a truthful visible event: location, puzzle, escape, reveal, chase, or objective.

Best Short formula

[curiosity / consequence] | Resident Evil Requiem #Shorts

One curiosity. The actual event answers it inside the clip; no vague “wait for it.”

Do not lead with

Full Survival Horror Session, Gameplay #N, or a long string of platform/game keywords.

They are accurate format labels but weak first reasons to click.

Title checklist before changing an existing video

  1. Can the title be proven from this exact footage? If not, source-review it first.
  2. Does the first clause name a scene, place, objective, danger, or reveal rather than “session”?
  3. Does “Resident Evil Requiem” appear once, naturally?
  4. Is PS5 useful to the viewer here? Keep it for the gameplay series; remove filler elsewhere if the title becomes crowded.
  5. Is the part number at the end in parentheses or after a dash—not the opening hook?
  6. Change a title only with a thumbnail/packaging hypothesis and a measurement window; do not bulk-edit all 13 blindly.

Thumbnail rules for the existing long videos

Description template

[One factual line about the event in this part.]\n[One factual line about the goal / tension.]\n\n▶ Watch next: [Part N+1 URL]\n▶ Start the RE9 series: [chronological playlist URL]\n\nChapters\n00:00 [truthful opening]\n…\n\nResident Evil Requiem PS5 gameplay from Regia Plays.

Descriptions can be up to 5,000 characters. Use the first two lines for the human promise, not a repeated keyword paragraph. Add chapters only when their labels are truthful and helpful. Part 10 already has substantive chapters; most of the other long videos do not.

Tags: use a compact hygiene set, not a growth tactic

Official YouTube guidance is unusually clear: title, thumbnail, and description matter more for discovery; tags play a minimal role except for commonly misspelled content. Do not spend hours chasing tags and do not put a wall of tags in a description.

Long-form base tags (use 8–12 total, then add only 2–3 scene-specific tags):

resident evil requiemresident evil requiem gameplayresident evil requiem ps5resident evil requiem walkthroughre9resident evil gameplayps5 gameplaysurvival horror gameplayregia plays

Specific-tag examples: Part 4 → resident evil requiem care center care center escape blood specimen. Part 6 → resident evil requiem antique coin inventory puzzle. Part 10 → first verify the canonical in-game spelling, then use that term once consistently.

Shorts: tags are optional. Keep the title clean; use 3 relevant hashtags maximum in the description: game, series shorthand, format. Never add unrelated franchise characters, trends, “fyp,” or a competitor’s name merely to chase search.

4. Existing long-form title audit: preserve truth, repair generic packaging

The following are recommendations, not live edits. Any rewrite marked “source-review” must be validated against the footage before changing the public title. This audit intentionally does not invent events for generic parts.

PartCurrent packageAssessmentRecommended action
1Cinematic Horror SequenceP1 Specific enough to be a starting point, but “cinematic” is generic.Source-review the first memorable story threat/reveal; otherwise retain and improve thumbnail + playlist route.
2Mysterious Body CutsceneKEEP / TEST A concrete hook.Candidate format: Mysterious Body Cutscene | Resident Evil Requiem PS5 Gameplay – Part 2. Pair with a clear still, not generic darkness.
3Exploring the Dark KitchenP2 Has a setting but little consequence.Source-review for the object, scare, or objective inside the kitchen; keep only if that is the truthful episode promise.
4Escape the Care CenterKEEP Strong, concrete, linked to existing Shorts.Use as the destination for every verified Care Center / observation-room Short. Add end screen, playlist URL, chapters, and precise thumbnail.
5Survival Horror SessionP0 Generic file-format language.Source-review and retitle around its actual best moment. Do not merely add “full.”
6Antique Coin & Inventory PuzzleKEEP / TEST A search-intent object + puzzle.High potential for a source-verified utility Short or focused “how I solved it” cut. Do not call it a solution guide unless it actually teaches the solution.
7Finding the Final ComponentKEEP / TEST A goal with forward motion.Use an object/goal thumbnail. Consider a “where is the final component?” utility cut only after footage review.
8Full Survival Horror SessionP0 Generic and extremely long.Find one or two self-contained events inside it; use those to package a better title/thumbnail or editorial highlight, not a duplicate full session.
9Exploring the Flooded CityKEEP / TEST Clear setting; needs a visual promise.Use the most readable flooded-city threat/location frame; identify a concrete discovery or danger for the first two description lines.
10Alpus Virus & Raccoon CityP1 FACT CHECK Strong lore package but the current Shorts/descriptions show a spelling inconsistency: “Alpus” vs “Elpis.”Check the owner footage / official in-game subtitle once, adopt one canonical spelling everywhere, then route lore/Emily Shorts to this part.
11Dark Room ExplorationP0 Too broad; little search or browse promise.Source-review for the threat, item, puzzle, or escape in the room and retitle from that event.
12Through the Overgrown RuinsP2 Atmospheric, but needs a stronger image.Keep only if the ruins are visually distinct; otherwise surface the real encounter/goal in the title.
13Full Survival Horror SessionP0 Generic ending package.Source-review its actual finale/reveal/objective. As final part, end-screen should point to a best entry and playlist, not a nonexistent next part.
Do not do a blind title rewrite pass. First review source and thumbnail per P0 part, create a concrete hypothesis, then update 2–3 titles at a time. A title that sounds stronger but misstates the footage will damage trust and retention.

5. Shorts system: how to make them from this library

What a good RE9 Short is

A Short is not a miniature episode trailer. It is a complete one-event story that works for a viewer with no Part-1 context: a visible threat, discovery, reveal, decision, scare, puzzle payoff, or odd line of dialogue. Its job is to create curiosity and give a clear route to the full episode.

BeatTargetRule
0–1 secondVisible question or payoff imageStart on the readable face/object/threat, not a dark corridor or brand slate.
1–4 secondsContext in one sentenceUse only copy the footage proves: “Someone is trapped behind the glass.”
4–25 secondsEscalation / actual sceneNative game audio remains primary. Lower captions must pause when in-game subtitles need room.
25–45 secondsPayoff or unresolved turnLength follows the scene. A 7–15 second shock is valid; a 40–55 second cut is valid only if real dialogue/reaction sustains the same event.
Final 1–2 secondsOne routeSmall text: “Full Part 4 linked.” The Related-video selector does the functional work.

What the owner transcript already suggests (must be visually verified)

Part 10’s local caption evidence contains several candidate story beats. They are discovery hypotheses, not automatically approved Shorts: the frame, game subtitles, and full scene must be inspected before any edit.

Immediate queue decision: do not release four more Part-10 lore clips. Build an 8–10 candidate bank across Parts 1–13, score it, then release only the best one roughly every 24 hours while the current Shorts obtain their first real distribution/retention data.

Candidate scoring gate before editing

QuestionScore 0–5
Can a stranger understand the visual threat/question in the first second?0–5
Does the clip contain a real escalation and payoff—or a satisfying unresolved turn?0–5
Can it work without explaining five minutes of lore?0–5
Does native audio/dialogue add emotion or clarity?0–5
Is there one exact episode to link afterward?0–5

Release candidates scoring 20+/25. Keep lower-scoring clips as source notes, not uploads.

6. Subscribe bell icons, reminders, and useful functionality

Should a subscribe/bell icon be at the end?

No persistent animated bell icon. It is not a functional YouTube subscription control, competes with the payoff, and is especially wasteful in a Short. For long-form, use YouTube’s real Subscribe end-screen element alongside Next Part and Playlist. That is functional and does not obscure gameplay.

Use a spoken or small on-screen CTA only after a viewer has received value:

Should there be reminders?

Special functionality worth adding

Chapters

Prioritize Parts 4, 6, 7, 9, 10, 13. Truthful descriptive chapters make long VODs navigable and reveal searchable entry points.

Accurate captions

Especially for dialogue/revelation-heavy RE9 scenes. Captions help comprehension and give you a trustworthy source index for future Short selection.

Channel home sections

Feature the chronological RE9 gameplay playlist and the RE9 Shorts playlist. A first-time visitor should immediately see “start here” and “quick highlights.”

Thumbnail/title tests

Use Studio testing where available for the P0 generic parts. Change one hypothesis at a time and wait for a meaningful number of impressions.

Pinned comment

Use a real story question plus one route on selected parts: “Which reveal changed the story most? Continue with Part 5 → …”

Playlist curation

Keep full gameplay oldest-to-newest; keep the Shorts playlist newest-to-oldest. They serve different viewer intent.

7. Future content plan built from footage you already own

A. Preserve the VOD archive; make editorial entry products

Do not delete or re-upload the current full parts. Instead, use their strongest moments to create newly edited, purpose-built products with a distinct viewer promise. A raw concatenation of old VOD segments is not enough; add a real editorial structure: short intro context, selected scenes, clean timeline/chapters, and a story/guide purpose.

B. Content pillars for the next 6–12 Shorts

PillarShare of queueWhat it looks likeWhy
Character / story twist40%Identity contradiction, betrayal, “what is this?” moment, conversation reversal.The Emily twist is the current best internal signal.
Scare / immediate danger30%Threat appears, containment fails, escape moment, monster/room turn.Works without lore context when the visual is clear.
Discovery / puzzle / object20%Antique Coin, component, location discovery, verified solution beat.Can pull search intent and route to a full episode.
Atmosphere / lore10%One concise lore line with visual proof.Use sparingly; exposition-only clips need context and can become repetitive.

C. Release cadence for an archive, not a content factory

7A. Additions from the official-product and game-opportunity research

Official product facts versus strategy inference: YouTube’s feature limits, metadata rules, A/B-test behavior, captions, and notification behavior below are documented platform facts. The recommended route/design choices are deliberate inferences for this specific RE9 library—not claims that YouTube guarantees a result.

Back-catalog packaging: test long-form, not Shorts

Channel Home and captions are library multipliers

Game-specific opportunity: package the player fantasy, only when the footage supports it

Current guide coverage frames Grace as scarce-ammo survival horror and Leon as faster combat. It also identifies specific search-interest locations and utility topics: Wrenwood, Rhodes Hill Chronic Care Center, three-quartz objectives, Raccoon City/RPD, water treatment, puzzles, collectibles, bosses, and endings. That creates three distinct entry lanes:

Spoiler policy for the archive: do not put late villains, endings, final boss, irreversible choices, or final locations in early-part titles, thumbnails, chapters, pinned comments, or feed-facing Shorts. If making a late-game/ending asset, label it SPOILERS — Late Game or ENDING SPOILERS in title and opening description line; use a non-revealing thumbnail such as “THE FINAL CHOICE.”

8. Measurement: what to inspect and what decisions it should drive

Views alone cannot tell you why a Short or VOD moves. For every release, record the right metric against a specific packaging hypothesis.

AssetCheck in StudioQuestion it answersAction
ShortShown in feed; Viewed vs swiped away; average view duration; average % viewed; likes/comments; related-video clicks if available.Did the first frame stop the swipe? Did the event hold attention? Did it create a route?If low viewed-vs-swiped, fix first visual/hook. If good swipe-stop but steep drop, shorten/contextualize the middle. If strong retention but low continuation, improve the linked episode/title match.
Long videoImpressions, CTR, average view duration, first-30-second retention, traffic sources, end-screen click rate.Is the packaging being chosen? Does the opening honor its promise? Are viewers continuing?Low impressions: improve discoverable event/thumbnail. Low CTR: test thumbnail/title. Good CTR + immediate drop: fix promise/opening for future edits, not tags.
PlaylistPlaylist starts, watch time, traffic from playlist/end screens.Does the series route keep people moving?If starts are weak, make “Start Here” more visible and link it from every part/Short.

Minimum experiment discipline

  1. Write one hypothesis before publishing: “A visible character contradiction will beat a lore sentence because no Part-1 context is required.”
  2. Release one Short, not four variants together.
  3. At 48 hours, capture metrics and identify the single biggest drop.
  4. Change one variable on the next Short: opening frame or length or event type—not all at once.
  5. Do not delete and re-upload merely because the first hours are quiet. First confirm processing, feed exposure, and enough time/data.

9. Things to avoid

Don’t treat tags as SEO magic

Official guidance says tags are minimal except for misspellings. Fix title, thumbnail, scene promise and route first.

Don’t dump clips

Four Shorts in eight hours hides the reason for every result and can exhaust the same tiny initial audience.

Don’t copy viral claims

External RE9 titles are market signals only. No fabricated character names, lore, “secret,” “full game,” or solution claim.

Don’t use generic sessions as entry packaging

“Full Survival Horror Session” is an archive label. Find the event inside it before trying to market it.

Don’t layer every CTA

No persistent bell animation; no repeated like/subscribe/comment reminder block; no end-card clutter.

Don’t add links without a route

A Short should not link to a random RE9 part. Link the exact source episode. A Part should not link only to “more videos”; it needs the next story step.

10. 30-day execution sequence

  1. Days 1–3: repair routes, not titles. Confirm chronological order of the 13-part RE9 playlist. Add a real playlist URL to every long description. Draft the same Next Part + playlist route. In Studio, add end screens to Parts 1–13 and inspect cards. Confirm each of the four Shorts has the exact Related video; current automation cannot verify Studio-only settings.
  2. Days 4–7: metadata source review. Review P0 generic Parts 5, 8, 11, 13 against source footage. Prepare factual event-led title/thumbnail proposals. Validate the Alpus/Elpis spelling against the source once. Add chapters to the highest-intent parts.
  3. Week 2: rebuild the Short queue. Mine 8–10 source-verified events across more than one part. Score them. Prepare 3 strongest cuts. Publish one, wait, measure, then select the next based on the result—not because a calendar says so.
  4. Week 3: create one editorial entry product. Choose either a Care Center highlight, an actual puzzle/utility cut, or a spoiler-aware story recap. It must add a new viewer promise and structure; do not simply concatenate old VODs.
  5. Week 4: learn and iterate. Compare story-twist vs scare vs discovery Shorts. Improve the first-two-seconds pattern from the best performer. Test two title/thumbnail hypotheses on selected long parts only after impressions accumulate.
Decision standard: maximize the number of well-matched viewer journeys, not the number of uploads. A viewer who clicks a concise RE9 reveal, lands in the exact Part, then continues in the playlist is more valuable than a disconnected spike on a random clip.

Sources, evidence, and limitations

Prepared for Regia Plays · Research snapshot: 2026-07-28 UTC · Generated by Hermes Pages · Public page auto-expires after 24 hours unless persisted.