u/Capital_Tangerine948

"This is what I think of your copyright" - translating a previously unreleased game with AI

"This is what I think of your copyright" - translating a previously unreleased game with AI

As an experiment I set my agent on translating an old Sega Saturn (1995) visual novel.

Result: https://imgur.com/a/c2gY51m#gpG94k0. The game is Nightruth Maria. It's unfortunately kinda mid. It only ever came out in Japan.

Total cost? 8 hours of my time and 3 dollars 40 cents on Deepseek API.

The short of it is to translate a rom you need 5 steps:

  1. Unpack the data from the iso
  2. Find where the text is located and how it's encoded into the game, extract it.
  3. Translate the text (and images if you need to - this one didn't)
  4. Prepare a patch that will inject your translated text back into the rom. This usually involves shifting data around so that you have enough bytes free to fit longer text.
  5. Run the patch, package new iso, test game.

AI did all 5 of those for me. All I did was orchestrate it, i.e. provide the vision of what I wanted, and babysit it so it didn't get too off-base.

It managed the first and last steps perfectly well - seriously, Chinese models are pretty good at reverse-engineering. It's a lot of trial and error, because even if you've located the text and it's in there in plain sight, you still need to find a way to extract it that will let you inject it back into the rom later without bricking it. AI also does trial and error, it just does it faster and without losing progress.

The problem was step 3. We got there eventually but it took the longest amount of time. At first deepseek started hallucinating an entire portion of the text. Then it simply forgot to translate some parts or just didn't want to. Finally it had some issues injecting the new text into the game and indicated some non-existing addresses, so some text was originally missing from the patched rom. It was a huge mess.

I had made a vision document to describe how I wanted the translation to sound, and I think on that note it did really well though. In the screenshot, you can see the text is a bit formal, it says "I shifted my gaze to my watch" and not "I looked down at my watch", but this is how the writers originally wrote it in. So we kept that. However, I wanted a localization in all other aspects. Just a personal preference.

For this game we were lucky that the font file contained Latin characters, otherwise we would have had to hack them in somehow. We were also lucky that text was very easy to find (being a VN) and was sequential. Other games are not so easy to reverse-engineer. Menus are already in english in the original, but otherwise I would just need my agent to extract the pictures somehow, and I tested this with Gemini - it can edit the text on them just fine while keeping the style consistent. Yes, you could use Photoshop if you have it, but it's a bit more work to keep the background correct when you edit the content of the picture. AI did a really good job, and you could even pipe them automatically to your model if there's hundreds of them.

I've seen both professional and amateur translation work that left in tons of typos too in my time, and missing strings. In some cases they didn't even encode their text back in properly and it doesn't display correctly.

Now for the first time in its 30 years history, Nightruth Maria has received an English translation. I'm just sitting on it right now though because I'm not sure it's ready to publish and I wouldn't even know where to put it. And like I said I'm not sure the game is super interesting in the first place.

But if you've wanted to FOSS some software, or translate games of your own... sic AI on it. This is what I think of copyright.

Antis are cannibalizing their communities in a bid to remain "pure" and "untainted"

(edited with AI to trim it to half-size from the original draft I wrote. I think of y'all having to read through this lol)

A few months ago, Codeberg decided to stop allowing AI projects. In the new, unclear wording, projects that mostly consist of AI code will be removed. 'Mostly' is their word, not mine. It does a lot of lifting. Policy: https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html. This is the final copy agreed upon by everyone who voted on it.

If you don't know Codeberg, I don't blame you. Barely anyone does, and they've now decided to become even more irrelevant—you'll see.

Codeberg is like GitHub: you use git to upload code, others download it. In its new policy, Codeberg tells "AI coders" to go back to GitHub. But GitHub is huge—projects like ffmpeg, which ships as a .dll with games you play, are hosted there. Also, Microsoft has owned GitHub since 2018. That matters, because Microsoft coined 'embrace, extend, extinguish' and deals in proprietary software. They could delete any critical repo and replace it with a paid service; they should never have been allowed to buy out github.

I support Codeberg's mission—I want alternatives to the corpo-owned internet. I'm just questioning this decision, rushed in 20 days.

Codeberg was never a serious competitor. I use it myself to avoid reinforcing GitHub—it's a personal choice. Codeberg sees itself that way too; it's in their mission statement. But here's the real scale of both: Codeberg's own Forgejo has barely 5k stars. GitHub's top projects have half a million. Openclaw, the viral AI agent, is the #6 most popular project on GitHub.

Now that Codeberg only wants pure, untainted projects, they've locked themselves into irrelevancy. It's not "might be more interesting than GitHub one day" anymore—it's impossible.

One thing people don't think about when it comes to AI code: security. AI finds vulnerabilities humans miss. That's just true. You have to run AI on code now, before some random with Anthropic credits finds the exploit for you... and doesn't disclose it.

But Codeberg cited "bogus AI issues" as a reason for the ban. So we're supposed to push and use buggy, vulnerable code because it's "purer"? Sorry, that won't fly for me. I'd prefer my apps to not have vulnerabilities anyone can exploit.

They also imply you can't act on AI-generated bug reports at all. If someone finds a real problem using AI, you're supposed to ignore it, apparently. Because in their unclear wording, and with the climate reigning over Codeberg right now, accepting it might very well get you and your project in hot waters.

The wording is unclear. I don't argue semantics, but Codeberg admits they can't really find these projects—yet they "know" it's a huge problem? They have proposed no detection tool, no automatic ban, no reporting mechanism. A 'moderator' from codeberg apparently pulls the trigger on their own.

And 'unmaintained' is undefined. If I upload a working repo and wait for user reports—but nobody uses Codeberg, so nobody makes reports—am I unmaintained? Do I need pointless commits to prove I'm alive? They don't say, but it's heavily implied. Remember: the most-starred repo on Codeberg has barely 5k stars. You don't use Codeberg to get users or a community, you use it because it's not Microslop.

The vote optics are bad too. Anyone who donates can become a member and vote. People openly said they'd drop €10 to push this vote through. It was announced before a decision was made and that's really, really bad optics. It should have stayed an internal matter until a decision was reached. I also manage and work on public online communities, it's what I would have done. Instead, they were communicating that they let people buy their way into a vote. That's... not very democratic, for a service that wants to claim it's all about FOSS (free and open source software).

Am I here to character assassinate Codeberg? No. I've managed online spaces too. I'm just saying this reinforces that you want specific developers and no one else, closing yourself off. It's at odds with your mission.

They also invite pushback with lines like:

> Using LLMs to work with your code gives you a kick of adrenaline. You can develop at a rapid pace, build things as if you had a large team. Only that you have none. In fact, you are (often) alone, working with a statistical machine that turns energy into code.

I'm not saying they can't say it—I just don't find it relevant. This is "I really want to make a statement" from them, and kind of tone-deaf, since FOSS projects often have a single core maintainer behind them (who often burns out from the popularity).

One of their reasons for this decisions was resource usage: they provide free hosting and thus want "quality". I get that—they give out free server resources unconditionally. But hand-coded doesn't equal quality. And this is why rate-limits exist: give new accounts 10MB, limit repos to 5MB, expand over time, charge for more. That's more sensible than blocking AI, because Codeberg would at least get something out of it.

They lament AI companies crawling "nonsensical" pages like git history—that's actually how LLMs are trained nowadays, they learn how code evolves over time and why. Instead of banning, they could make deals with companies for access, like Reddit and Stack Overflow did. They're gonna crawl you anyway, least you can do is charge them for it.

It just seems like virtue-signaling. They say LLMs are a danger to FOSS, but their solution is to take themselves out of the equation—out of the discussion, out of growth, out of ever being a relevant alternative to GitHub. All so they can stay pure while AI keeps doing its thing with or without them.

It's certainly a choice, but it's not one that's in the best interest of FOSS.

reddit.com
u/Capital_Tangerine948 — 5 days ago