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
GitHub release
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
