What this site is
Helping Your Boyfriend is a psychological horror visual novel by Zieelane (project manager, lead writer, programmer, UI and visual design) and Mousefishdog (characters and CG art), built in Unity and Naninovel for the Spooktober 8th Annual Visual Novel Jam in 2026. It runs about half an hour, has four endings and five minigames, and ships in English and Thai with more than 8,000 words in the English script. It is played on Windows, macOS, Android and the web browser.
This site is an independent fan page. It is not affiliated with, endorsed by, sponsored by, or monitored by Zieelane, Mousefishdog, or any of the other credited contributors, and it does not host the game files. The game remains their work. What this page does is two things: it embeds their published browser build so you can play without downloading anything, and it documents the game in long-form guides for people who want to understand it before or after a run.
Everything you see here is written for players. There is no account to make, nothing to install, and nothing to pay. If the game is worth thirty minutes of your night, this page is here to make it easier to get to the ending you are looking for.
Who runs it
One person runs this site. They are a fan of the game, they pay for the hosting out of pocket, and they write and maintain the guides themselves. There is no team, no agency and no publisher behind this page, and no advertising is placed on the guide pages.
What that means in practice is simple: when something on this site is wrong, it is wrong because one person read the game wrong, not because a business decided to publish something inaccurate. Corrections get applied and the underlying data gets fixed too, so the same mistake does not come back on the next rebuild.
Where the guide facts come from
This is the part that matters most if you are checking anything here. The guides are not written from memory, from forum posts, or from what seemed plausible while playing. The published build of the game ships its own script data — data/scripts.json, a Naninovel command stream containing every line, every branch label, every condition expression and every variable the game reads.
That file is the single source of truth for every factual claim in the guide column. The ending titles, the flag names, the meter names, the numeric thresholds and the scene labels printed in the guides are the game's own identifiers, copied out of that stream rather than paraphrased. If a guide says toldAddress opens the escape door, that is the literal variable name in the shipped script.
How that gets checked
Every game-specific name that appears in the guide prose — flag names, meter names, scene labels, ending titles — is verified against the game's real vocabulary by a script that runs on every build. If the prose mentions an identifier the game does not contain, the build fails instead of shipping. That is what stops a plausible-sounding but wrong trigger condition from reaching a player who is trying to solve a route.
The guide column currently covers roughly 27,000 words across six articles and 58 images, and every one of those pages carries a matching structured-data block so that the questions and answers on the page are also machine-readable.
About the images
No image on this site is AI-generated. The screenshots, backgrounds and character art are pulled directly from the shipped build's own media files (data/assets.json and data/assets-all.json) and re-encoded to WebP so the pages load quickly. All artwork and screenshots remain the property of their respective creators and are used here to introduce and explain the game.
The two walkthrough videos embedded on the home page are by Hello Yinny and Your Game, and they stay the property of their creators — they are linked and embedded, never re-uploaded.
Editorial policy
- Facts come from the game. Trigger conditions, flag names, thresholds and ending titles are extracted from the shipped script data, never from a guess or a secondhand summary.
- Spoilers are labelled. Every guide states plainly what it spoils before you read it, so you can finish your own run first if you would rather.
- No invented content. There is no invented difficulty selector, no invented mechanic, and no "pro tip" that the game does not support.
- Corrections are permanent. A reported mistake is fixed in the copy and in the underlying data, so it cannot silently come back.
- Content warnings are respected. The game contains jumpscares, loud sounds, flashing images, blood, cartoon gore, violence, drug use, obsessive behaviour, toxic relationships and crude language. The warning is on the home page and repeated at the top of the spoiler-heavy guides.
Frequently asked questions
Is helpingyourboyfriend.online affiliated with the creators of Helping Your Boyfriend?
No. This is an independent fan page. It is not affiliated with, endorsed by, or sponsored by Zieelane, Mousefishdog or the other credited contributors, and it does not host the game files. The game itself is the work of its creators; this page only plays their published build and documents it.
Who made this website?
It is run and maintained by one person, an independent fan of the game, who pays for the hosting and writes every guide published here. There is no team, no agency and no publisher behind it, and no advertising on the pages that carry the guides.
Where does the guide information come from?
From the game's own shipped files. The ending titles, branch labels, flag names, meter thresholds and route conditions are extracted from the Naninovel command stream inside the published build (data/scripts.json), so they are the game's real identifiers rather than guesses. A verification script re-checks every game-specific name used in the guides against that vocabulary on every build, and the build fails if any name is not found.
Are the screenshots and images AI-generated?
No. Every image on this site is pulled from the shipped build's own media files (data/assets.json and data/assets-all.json) and re-encoded to WebP for the web. Nothing here is generated, and all artwork and screenshots remain the property of their creators.
Can I report a mistake in a guide?
Yes, and corrections are the point. Use the contact form on this page to send the page URL, what the guide says, and what the game actually does. Corrections are applied to the guide and to the verification data, so they stay fixed on the next rebuild.
Does this site collect any personal data?
The site sets no advertising cookies and builds no profile of you. A privacy-friendly, cookie-free analytics counter records page views and referral sources in aggregate. The contact form is the only place where you type anything, and whatever you send is used only to reply to you. The full text is on the privacy page.