Routine major and minor fixes can now be seen.

AI-Focused Announcement (Concise)

Why this change

I rarely wrote changelogs. The tool updates frequently, but users couldn’t see what changed. Meanwhile, years of ad-hoc maintenance pushed the volume of issues close to my personal limit.

What’s new: one intake, public progress

You can now submit issues via the “!” in the top-right of the tool.
After submission, a thread is automatically created in the forum’s [Bug Reports] section so both you and I can track status in one place.

• Entry point: top-right “!” inside the tool

• Where to view: forum [Bug Reports] (bbs.mtool.app)

• What I’ll do: triage, schedule, label status, and update the same thread when fixed

Note: Issues sent via Steam, Discord, or platform DMs are not auto-synced. For the fastest handling, please use the “!” entry in the tool.

How this replaces a traditional changelog

The [Bug Reports] forum effectively acts as a fix log: you can see what was just resolved and what’s in progress—making updates more transparent.

Why some new translations require a forced update

While there are other factors, the main reason is that a few games didn’t work on older versions. After fixes, certain scenarios need re-translation to function correctly. Requiring an update reduces wasted resources and repeated errors. Thanks for understanding.

-------- Full Post (Translated & Lightly Polished) --------

I’ve been thinking about this for a long time:

“I don’t want to write changelogs” vs. “Do we actually need changelogs?”

I’ve always known that skipping changelogs makes changes invisible to users—
but honestly, I just didn’t want to write them.

For me, that reluctance comes from years of accumulating aversion to things like “daily/weekly/monthly reports” and “documentation” back when I was an employee.

But over the years, reality set in:

Many people feel that “MTool is fine, it updates all the time, but we can’t tell what changed.”

At the same time, after years of unstructured maintenance, the number of issues almost reached the limit of what I can manage solo.

I needed a way for users to report problems clearly/quickly/simply, and for me to queue and resolve them in one unified place.

So there’s now a “!” button at the top-right of the tool.

It actually appeared months ago, but I hadn’t decided how to use it.
After a few iterations, it’s now a somewhat “retro” approach:

an internal list + a public forum thread.

This gives me an internal list to track status, while keeping everything public and easy for users to check.

Which also helps with the “changelog” problem.

From now on, any issue submitted via the top-right “!”
will automatically create a post in the forum’s [Bug Reports] section.

(Reports sent via Steam, Discord, or platform DMs won’t show up there for now.)

Forum: bbs.mtool.app

Think of it as a kind of bug-fix log.

You can directly see what’s been fixed recently and what’s still in progress.
I hope this makes updates more transparent and reduces uncertainty.

This also partly explains why new translations sometimes require a forced update: some games really didn’t work on older versions, and after fixes, certain cases need re-translation to function properly—reducing wasted resources and repeated errors.