Yandere Simulator Custom Mode Explained: Create Your Own School Story

Custom Mode is the sandbox lane for players who already understand a school week in Yandere Simulator and want to rewrite the cast, the schedule, and the confession arc without waiting on a new official rival drop. You still play inside Akademi’s rules—classes, clubs, reputation pressure—but the story beats belong to you.

Content note: Custom stories can include mature themes depending on what you write. This guide covers editor access, file layout, and sharing etiquette—strategy and setup, not graphic walkthroughs.

If you have not installed a recent build yet, grab the launcher or zip from the Download page and skim the FAQ for mode basics before you touch JSON.

What Custom Mode is for

Story Mode ships fixed rivals and scripted weeks. Custom Mode flips that contract: you define the protagonist profile, Senpai, each rival’s identity, where they stand on the map, and how their day flows. The confession week still arrives, but how rivals leave the picture depends on the elimination methods you enable and how reputation plays out across your custom cast.

Most community stories today sit on the 1980s Mode foundation. That means Ryoba-era tone, phone-free intel habits, and pacing closer to retro Akademi than full 202X phone economy. Treat Custom Mode as “author a mini-campaign,” not a total engine rewrite—you are arranging characters and markers inside systems the build already understands.

Players use it for alternate timelines, challenge runs with weird schedules, fan-fiction schools that still obey bell times, and shared scenarios posted on forums. The payoff is replay value after you finish Osana/Amai routes in Story Mode.

How to open it

Custom Mode does not hide inside the main 202X Story save flow. On current builds you reach it through the 1980s Mode new-save UI:

1. From the title menu, start a flow that creates or opens a 1980s save (exact menu labels shift slightly between builds—if a button moved, check the latest DevBlog note before you reinstall).
2. On the new-save screen, look for Shift or Custom Mode. Community threads describe the same entry point: 1980s save creation first, then the Custom button beside Shift.
3. Confirm you want a custom slot rather than the default 1980s campaign. The editor opens on top of that mode stack.

If the button never appears, you are usually in the wrong mode branch (202X Story) or on an older build from before Custom Mode landed with the big January update wave. Updating through the official launcher, then repeating the 1980s new-save path, fixes most “where is Custom Mode?” reports.

Cross-read the 1980s Mode guide if Ryoba’s week rhythm is unfamiliar—Custom Mode inherits that DNA even when your cast names are original.

What you can edit

The in-game editor is the friendly face; the real contract lives in data files. From the editor you typically touch:

• Protagonist and Senpai — names, portraits where supported, baseline relationship framing.
• Rivals — headcount, identities, elimination hooks the game recognizes, confession timing relative to your method mix.
• Routines and map markers — where a rival eats lunch, which corridor they patrol, which club door matters for your plot.
• Topic and misc text — dialogue-adjacent strings that show up in school life scenes (keep AdSense-safe phrasing if you plan to showcase the story on a public blog).

Think in schedules first, drama second. A rival who never visits the roof will never trigger your rooftop event, no matter how good the portrait folder looks. Place markers where students already path during class breaks; the engine does not invent new navmesh highways for custom stories.

Confession week end states tie back to elimination methods you allow and reputation swings across the school. A custom story that enables every loud option without giving the player social cover will feel “broken” when the whole school turns hostile by Wednesday—even though the JSON is valid.

Cutscenes and events folders

Cutscenes and one-off beats ride in `StreamingAssets/CustomMode` (plus companion JSON the wiki documents). Treat that directory as your film strip:

• Drop event scripts or scene hooks the build expects for Custom Mode sequences.
• Keep filenames and topic IDs aligned with what `CustomTopics.json` references, or the game silently skips your beat and players assume the story is unfinished.
• Test one event on a fresh save before you bundle a ten-rival epic—failed references are easier to catch when only one flag fires.

If you mod visuals, `PortraitsCustom` (per wiki layout) holds custom portrait assets. Mismatch between portrait IDs in JSON and files on disk shows up as blank silhouettes or default stock faces—always verify in-game after a copy/paste from someone else’s pack.

Backup your whole CustomMode tree before you paste a stranger’s download. Merge conflicts between `Custom.json`, `CustomTopics.json`, and `Misc.json` are the usual reason “it worked on their PC” stories fail on yours.

Sharing a custom story

Sharing is a folder + JSON handoff, not a Steam Workshop button:

Piece	Role
`Custom.json`	Core cast, rivals, method flags, schedule skeleton
`CustomTopics.json`	Topic lines tied to events and school life
`Misc.json`	Extra toggles and misc data the wiki lists per build
`PortraitsCustom/`	Optional art pack
`StreamingAssets/CustomMode/`	Cutscenes and custom events

Zip the set, label the build month you tested on, and tell players which mode entry path you used (1980s → Custom). Ask them to merge into their game directory rather than overwriting unrelated Story saves.

When you publish a story on the hub or a forum, link back to the FAQ for install hygiene and warn players that mature custom plots are author responsibility—fan hub guides stay strategy-focused.

Limits on recent builds

Custom Mode is powerful and still young. Expect rough edges:

• 1980s foundation — 202X-only systems (full phone schemes, some club gadgets) may be absent or simplified. Do not assume Info-Chan schemes from Story Mode port one-to-one.
• Confession week — outcomes depend on which elimination routes you enabled and whether reputation collapsed mid-week. Test confession with both a peaceful run and a messy run before you advertise “multiple endings.”
• Build drift — January-era Custom Mode updates landed with Mission Mode and 1980s work; mid-2026 bug-fix passes can rename menu strings or fix event triggers. Re-test after every game update you install.
• No official cloud sync — broken paths or half-merged JSON are player-side fixes; keep version notes in your readme.

If a custom rival refuses to progress, check reputation first, then marker placement, then JSON typos—in that order. Most “stuck rival” tickets are schedule gaps, not engine curses.

Related modes

1980s Story Mode is the canonical campaign Custom Mode clones. Learn Ryoba’s tools there before you author.

Mission Mode (main menu contracts) scratches a different itch: fixed constraints and awareness scoring instead of a authored confession arc. Useful for sharpening stealth without editing JSON.

202X Story Mode remains the flagship ten-rival route with phone intel and expanding scheme menus—great for playing official content, separate from authoring.

When your custom week feels stable, try exporting a clean peaceful run video or write-up that highlights systems (schedules, reputation gates) rather than shock content—that keeps your page aligned with AdSense-safe hub standards and helps other authors learn from your layout choices.