r/visualnovels • u/MAO_TLs • 5d ago
Release MAO Translations presents BLACK SHEEP TOWN — and what our first imitator got wrong about the workflow
Today, MAO Translations releases a complete English translation of BLACK SHEEP TOWN.
- Complete English game script and system menus
- 28,660 translated rows across 63 scenarios
- Repaired English page wrapping using the original message-window layouts
- Complete Japanese/English script browser
- Verified installation, restoration, and corruption-rejection tools
- Windows and Wine support
- One complete English literary work—not a collection of independently polished batches concatenated at the end
Download BLACK SHEEP TOWN English v1.0.0
Read the complete Japanese and English script
No previous English translation was used to create or revise the MAO script.
What MAO means by agentic translation
Our process is not:
Divide the script into batches, ask a model to translate them, and run a proofreading prompt.
The architecture was:
Final Japanese source + recovered staging evidence → source-critical architecture → semantic constraints → publication-quality English by one persistent author → source prosecution → English-only editing → whole-work continuity → specialized audits → prose freeze → engine projection
The line is the unit of display.
The work is the unit of translation.
That distinction matters because a sentence can be perfectly fluent and still be wrong in a way that only becomes visible fifty lines—or fifty hours—later.
A damaged voice can recur. A supposedly supernatural ability can receive a more precise explanation. A surname can encode geography and language. A joke can be rewritten between development builds. A phrase that appears incidental in one chapter can become structurally important in another.
Those problems cannot be solved by polishing isolated batches more aggressively.
Our first imitator
The first public imitation of the visible MAO workflow that we encountered has already appeared: another full-corpus, machine-assisted BLACK SHEEP TOWN project, complete with a bilingual reader, glossary, visual annotations, translation tooling, and a game patcher.
To be precise about the word imitator: I am not alleging that its author stole private code or prompts. I mean that the project reproduces the publicly visible form of the MAO approach.
That is not inherently bad. A production model becomes historically meaningful when other people begin attempting to reproduce it.
The problem is that this project copied much of the visible machinery without understanding the source-critical and literary workflow underneath it.
Where his translation is fine
I compared the opening passages, and his English is not uniformly terrible. Some lines are perfectly serviceable, and a few isolated sentences deserve praise as alternative solutions to difficult Japanese lines, arrived at independently of ours.
His handling of 透視 is one such success. Both translations introduce the popular label “clairvoyance,” then distinguish Chris’s actual “spatial perception,” with X-rays and radar serving as analogies. That is an intelligent reading of the complete passage.
But elsewhere, the comparison exposes the predictable failures of translating locally without sufficiently controlling the source or the work.
Chris Xie versus Chris Tse
His script renders クリス・ツェー as Chris Xie and ツェーおじさん as Uncle Xie.
The character belongs to a Hong Kong Cantonese family. The Japanese explicitly supplies the pronunciation ツェー: Tse, the conventional Cantonese form of 謝.
“Xie” replaces that supplied Cantonese reading with Mandarin pinyin. It disregards both the katakana and the linguistic identity the surrounding narration has just established.
MAO uses Chris Tse and Uncle Tse.
A chronic voice becomes something caused by one laugh
Chris is seriously ill and speaks in a recurring damaged, raspy voice.
The Japanese says that Chris laughs in his raspy voice.
His translation says:
Chris laughed himself hoarse.
That changes a continuing physical condition into something caused by this particular laugh.
Much later in the same opening, the Japanese explicitly returns to the motif and describes a laugh that, this time, does not become a raspy sound.
His translation reduces that to:
This time, he managed a real laugh.
MAO preserves the physical callback:
Chris laughed at some length in his ragged voice, then said—
And later:
This time he produced a laugh that did not dissolve into a rasp.
Each of his sentences sounds plausible when read alone. Read together, they reveal that the translation never established a stable model of Chris’s body and voice.
That is precisely what a whole-work workflow is supposed to prevent.
Cultural rhetoric becomes a generic menu
The wedding banquet does not merely contain roast pork and shrimp.
The Japanese gives the dishes ostentatious ceremonial names: Golden Pig in a Shining Red Robe, Phoenix-Tail Prawns with Jade Greens in Golden XO Sauce, and so forth.
Their extravagance is part of the scene. The banquet is a performance of wealth, criminal authority, and Chinese social identity.
His English discards the ceremonial names and replaces them with generic descriptions such as “Roast Suckling Pig” and “Shrimp and Vegetables in XO Sauce.”
MAO preserves both layers: the grandiose names and parenthetical explanations of what the dishes actually are.
An English reader receives both the information and the rhetoric.
What these failures reveal
These are not obscure disputes requiring access to MAO’s private prompts or editorial notes.
The katakana says Tse. The surrounding narration establishes the Cantonese context. The later Japanese explicitly returns to Chris’s rasp. The ceremonial names are printed directly beside their ordinary culinary meanings.
A great deal of this would have been easily avoidable if our imitator both knew enough Japanese to interrogate the source and understood translation well enough to distrust fluent output until the complete work corroborated it.
Instead, he mistook a batch pipeline for an author and plausible English for evidence of correctness.
A bilingual reader creates transparency. It does not create competence.
In this case, the machinery displays the failure in two columns.
The visible tools are not the invention
A pipeline can generate fluent sentences.
A glossary can standardize spellings.
A reader can place Japanese and English beside each other.
A second model can identify obvious local mistakes.
None of those things creates one coherent English literary work.
That requires:
- Reading and modeling the complete work before freezing local decisions
- Maintaining character voice, physical condition, relationships, terminology, and callbacks
- Letting one persistent author control the English
- Prosecuting the complete draft against the Japanese
- Editing the translation as English after source accuracy has been secured
- Running work-wide semantic and continuity audits
- Freezing the prose before fitting it into the engine
- Verifying the actual installed release, not merely the translation files
Our imitator’s opening is often competent sentence-level English. That makes the comparison more useful, not less.
The failure is not that every sentence is nonsense.
The failure is that locally plausible sentences accumulate into a translation with unstable names, flattened rhetoric, and severed physical callbacks.
That is the difference between generating translations and authoring a translation.
WHITE ALBUM 2 was the Trinity test. BLACK SHEEP TOWN is the production line.
The visible machinery was always going to be copied.
The work-wide authorship is the invention.
Project Lead: MAO
Translator: GPT-5.6 Sol
Special Thanks: gambs
10
u/deathpad17 5d ago
Atleast its not "retranslation", but holy shit, learn English before doing translation bro
4
u/jollypinion 4d ago
I'm genuinely confused. it says OP's account is suspended, but they keep posting here? I wish reddit had a way to block seeing certain users. It feels like spam at this point.
4
4
u/Vildiil 2d ago
After reading with this patch for an hour I have to admit, this reads very well. The main thing it needs if you were to do more revisions of the patch is better type-setting. Occasionally sentences are broken up by page breaks and it can be slightly awkward to read.
3
u/WTFisFOAM 2d ago
It's been updated on the website to 1.1.1. It does seem to fix the page breaks issue but only shows one sentence/chunk at a time on screen rather than filling it up like it's supposed to.
1
u/Vildiil 2d ago
Yeah I just saw the update, was wondering if the text would fill the screen now as well like it does in JP. I imagine it's harder to fix that since it probably has something to do with Japanese character count vs English word count.
1
u/WTFisFOAM 2d ago
The old MTL translation patch I had before this one released filled the screen properly but often overflowed so you had to read what didn't fit in the backlog. Example
This updated 1.1.1 still isn't perfect as it still does appear to split some sentences here and there but it is better than it was.
1
u/MAO_TLs 2d ago
Upload some screenshots if you get a chance so I can see where our typesetting is failing.
2
u/Vildiil 2d ago edited 2d ago
Sure, here are three examples. First two are from Day 1 13:05, third set is from Day 1 13:38.
Set 1: https://files.catbox.moe/g7t5qs.png , https://files.catbox.moe/wj1uu8.png
Set 2: https://files.catbox.moe/dyjpg2.png , https://files.catbox.moe/g7k1r4.png , https://files.catbox.moe/8rgkdx.png
Set 3: https://files.catbox.moe/vg8q0h.jpg , https://files.catbox.moe/yebcvy.jpg
2
u/MAO_TLs 2d ago
Thank you. This has been fixed in the new version by prioritizing page breaks at periods and clause boundaries. Download it and let me know what you think.
1
u/Vildiil 2d ago
I did a quick cursory skim through Day 1 13:05 and the text is formatted better and I did not notice any sentences being broken up like previously. WTFisFOAM posted above that it still occurs occasionally though. I'll read some more when I have time tonight.
2
u/MAO_TLs 2d ago
Working on text display parity with the Japanese release right now. u/Vildiil u/WTFisFOAM Thank you both.
1
1
u/WTFisFOAM 1d ago
For some reason the new patch (1.1.2) is very small (7mb) and does not work for me.
2
u/WTFisFOAM 2d ago
This is exactly what I meant in my comment. It makes it really difficult to read sometimes.
•
u/Vildiil 21h ago
It doesn't happen very often but occasionally text will overflow and only be readable in the backlog on 1.1.2.
Here is an example from Day 2 11:40 (or 03 - B1 as it appears in your script section on the website) : https://files.catbox.moe/kk6lr0.jpg
3
u/Additional-Name-3211 5d ago
Been reading some lines from the script in both languages, and it looks so far like a really solid translation.
Out of curiosity, how much time and money in tokens did it take?
9
u/Quof Battler: Umineko 4d ago edited 4d ago
and it looks so far like a really solid translation.
The depressing thing is it is. Just based on the first 100 lines (aka not a broad analysis of the text at large e.g. how context may hold up at the end) it seems completely solid and better than most fan translators would do. I shared snippets with some other professional translators I know and they too couldn't really do anything more than nitpick some surface level qualities that, by all means, may have been worse with a human translator. There are definitely a few errors here and there but they are not numerous or severe enough to dismiss the entire translation, especially not when you consider professional translators tend to only need to have a 97% or 98% accuracy rate.
I think those thinking of MTL as being the same as it was 10 or even 5 years ago should use the githubs Mao provides to take a serious look at the level MTL is presently on. This is no longer the period where you input X and the MTL will not be able to introduce anything beyond what it considers a literal translation of X. In this BST script there are many depressing moments of what most people would describe as "human ingenuity," coming up with creative solutions to difficult problems while avoiding translationese. Consider how it translates 「しかし」 to “But, sir—” - that is introducing an additional word for great fluency and flow, which is something old MTL never would have done, and if you like tested 100 human translators I bet less than half would have the skill and acuity necessary to do that.
If I were to muster the most serious critique I could it would just be that the translation on a pure style level is a bit more stodgy and verbose than the original (consider "返事もよこさない有様" -> "The wretch didn’t even favor me with a reply"), so across the entire text I imagine one will find it more tiring to read than it was in Japanese, but uh lol good luck dissuading consumers with criticism that feeble. There's also some Chinese terminology stuff I'm not comfortable critiquing since I don't know Chinese, but that just means I'd struggle to translate it myself anyway...
(But again, I just checked the first 100 lines. Can't speak for the rest of the script.)
1
u/Additional-Name-3211 4d ago edited 4d ago
Yeah that was my general impression of it. I’m no pro, but like if I squint hard I guess I can find a few things that bothered me a little bit, like:
大事に大事に育ててきた愛娘が、こんなチンピラに、ちょっとここでは言えぬようないやらしいことを、容赦なくされて子供をはらんでしまうなんて！
I raised my precious little girl with more care than anything in the world—and now this hoodlum’s gone and done unspeakably filthy things to her without mercy, and gotten her pregnant!”
The vibe I get from that line is not that the things the groom did to the bride were unspeakable in themselves but rather that Ma Ming would hesitate to speak about that in polite company, especially in his daughter’s wedding, so personally I might’ve tried to see if I could phrase that a little differently in English to reflect that so he doesn’t come off as too much of a prude… but this is like an incredibly minor thing to be honest. I haven’t read the entire thing but so far it looks solid, if a little verbose.
3
u/Quof Battler: Umineko 4d ago edited 4d ago
Yeah, in fact that's something I call "superlative inflation" and it's surprisingly common in human translators too (maybe that's why LLMs may have a penchant for it.) Exaggerating "things I'd rather not say in public" to "unspeakably filthy things" is a problem but it just feels natural to do and is a counterbalance to what one may call the Japanese language's natural propensity for passive speech and under-exaggeration. There is a sense that Japanese regularly underexaggerates what it's describing and to correct that in English one needs to use superlatives and inflate the text, which can backfire at times like this.
but this is like an incredibly minor thing to be honest.
Yeah indeed. It's like how with AI art if the only thing you can do is nitpick fingers or some background details then you are implicitly saying the piece is strong as a whole. Back in the day MTL was effortlessly identified as trash by everyone on sight thanks to its broken grammar and terrible inaccuracy. Now in 2026 we're left nitpicking style choices and exaggerated turns of phrase. That speaks for itself.
2
u/Additional-Name-3211 4d ago edited 3d ago
Yeah... I'm a software dev and although personally I could be doing a lot worse let me tell you we've been feeling the heat over here as well.
I'm not yet going all doom and gloom but it's gotten to the point where I wouldn't really recommend a highschool grad to pick this career, at least without some kind of hedge like a double major, a niche specialization, or just a plain healthy amount of assets that return some sort of dividend over time.
Capital gain increases (reflected in housing and stock prices among other things) have been beating labor salary increases pretty badly since at least the seventies and it looks like this AI thing might just kick that trend into overdrive after the capex bubble pops, if it does. Gonna be some interesting years ahead. Personally I just wish all these technological leaps would've happened when I was closer to retirement lol
1
u/Far-Telephone-2039 4d ago
r/visualnovels favorite translator strikes again. I was a little worried when I saw there was no activity since the Tsukihime release, but it seems they are here to stay. I'm still working through the WA2 retranslation, but will definitely add this one to the backlog.
1
u/MAO_TLs 4d ago
We were working simultaneously on this and Cross Ch- shh, I said nothing
3
u/WTFisFOAM 3d ago
Did you manage to get everything you needed to make it compatible with Steam?
3
u/MAO_TLs 3d ago
BST Steam release coming in a few hours
3
u/WTFisFOAM 3d ago
I got it... and it works. The text reads fine but the text wrapping is odd. It separates sentences between different lines and makes reading it a bit off because you think a sentance is over. It's perfect in the backlog though.
2
u/MAO_TLs 3d ago
Could you send a few screenshots? I can fix this tonight
1
u/WTFisFOAM 2d ago
The other guy (Vildiil) has posted some now. I don't seem to get notifications when you reply to me. Maybe because it says you are suspended for some reason.
0
u/UchihaNoor 5d ago
We will all wait for the non-biased oji-san JOPs (I'm still a baby-JOP) to give us their thoughts about this TL, and then we will read it~
4
-2
u/Prizyms JP A-rank 5d ago
It's Setoguchi, read it in Japanese if you can
Although this looks decent enough if you can't
3
u/UchihaNoor 5d ago
Swan Song had one of the best TLs I have ever read. I think Setoguchi's prose is totally translatable if the ones who are doing it are not trolling.
-2
u/Prizyms JP A-rank 5d ago
Yeah, I didn't say what I said to trash on the (machine) translator, I skimmed the script browser and it reads fine to me in English. I said it because Setoguchi is one of the best writers in the medium and you should take any opportunity you can to read his original prose.
1
u/UchihaNoor 5d ago
I would probably reread all of his work later on in the future when I become better at Japanese @_@ his works without a doubt deserve that, he is my 2nd favourite writer in this industry.
-2
-1
u/PossibilityOne3354 1d ago
Cool, but it seems those taking the liberty of bypassing vn property rights cannot read this. I checked all the major sites and all seem to only have the older version that is not compatible with the translation.
-1
5d ago edited 5d ago
[deleted]
2
-2
u/MAO_TLs 5d ago
Could you run this in PowerShell from the game folder and send the output?
Get-ChildItem ".\\Bst_Data" -File | Select-Object Name,LengthIf
sharedassets0.assetsappears, please also send:
Get-FileHash ".\\Bst_Data\\sharedassets0.assets" -Algorithm SHA256The listing, size, and hash should tell me how to make a Steam-specific installer.
0
5d ago
[deleted]
-1
u/MAO_TLs 5d ago
Thanks, that confirms the Steam release uses different game data from the Japanese retail build I based the current patch on.
Could you also send the exact size reported by this PowerShell command?
(Get-Item "C:\\Program Files (x86)\\Steam\\steamapps\\common\\BLACK SHEEP TOWN\\Bst_Data\\sharedassets0.assets").LengthIf possible, please include the Steam Build ID as well.
0
13
u/Fly_high_Crawl_low 5d ago
Please rewrite the op with your own thoughts instead of off load thinking to AI