Why update, and why so frequency?

(I've always seen people complaining about "fake updates" and "not letting free users use it", hence this article).

You may not be aware of how this software can allow a game to run smoothly after translation without crashing. 

The answer: I constantly update it.

Why is it able to run on almost every user's system without requiring any special setup? 

Again, because I keep updating it.

Why are most new games supported? 

Because I start updating as soon as they're released. 

While you're sleeping after the game launches, I'm busy updating it! By the time most people start playing, I've already fixed the problems. 

They just get a seemingly pointless update and grumble, "Another fake update, What a shame!".

I've put tens of thousands of games working on this engine. The massive scale makes it impossible for me to test each one individually.

How do I make sure the software runs seamlessly? 

By relying on everyone's feedback. 

I look at every reported problem, fix it, and patch it in subsequent updates. 

These "updates" will free you from all problems. 

(Also, because the situation is too complex with so many games, a small change can affect everything. Sometimes a bunch of updates in short time might indicate that the previous update caused other problems).

Some people are waiting on the next "update" to fix their problems. Maybe you're not willing to update right away, so should they just keep waiting?

You might say, "Don't force updates, let me choose when to update".

This used to be my strategy, but the reality is that when users encounter problems in the games, they don't actively update; instead, they come to me with their problems, which means I have to spend time dealing with this "pointless feedback". 

(Before fully implementing forced updates, I gradually increased the urgency of the update reminders, telling users not to report problems before updating. But clearly I was unsuccessful. Even now, with forced updates, some are still reporting problems that have already been fixed).

Although these updates are free, they're not "free" to me. I invest a lot of time and money (buying games/development tools/testing equipment) to produce these "free" updates.

I only charge for translation services that cost me a lot of money, and this price is much cheaper than if you paid the translation engine directly.

You can get these updates with a few simple mouse clicks.

( I do intend to increase the pay rate here, because I have no selling point other than the translation which is almost completely free, and I don't want to offer a product that is broken if you don't pay, so I have no choice.)

Isn't that enough?

You can choose not to use it, but please don't doubt it.

------------

Let me also explain here why there is no permanent license, no one-time payment for lifetime use. 

I couldn't afford to pay the translation/server fees for everyone indefinitely. 

If it becomes permanent, I would surely have to cut and run.

------------

After some thought, I think most regular people:

Don't want to: Register a translation engine account > do verification > Apply for API

Don't understand: The cost of translation, how much it costs to use machine translation for certain amounts of text, the limitations/inconveniences of free use.

Everyone just wants to play and doesn't want to think too much. This is perfectly fine.

If we didn't care about the user's emotional balance, I could provide the ability to call your own API directly.

But consider this:

If others can get it for free (using the free credit), then surely I should get it for free too. Why should I pay? (Sure, not everyone thinks this way)

This could become a big problem.

People might write tutorials on how to use it for free, and those who can use it for free might mock those who pay. (Similar to "pirated versus legal" disputes)

It's uncomfortable for everyone. The paying customers feel they're being cheated, and the free users aren't happy either.

The ultimate user experience would be: Another sloppy product.

The downward spiral could end in chaos.

There's no such thing as a free lunch, what falls from the sky is usually a trap.

------------

Why didn't I write an changelogs, because I don't like it.

I was resistant to this stuff when I was working.

I would only inform users when it was necessary, unless there was no other option.

------------

Recently there have been several tools that can translate the JSON files exported by my tool. I hope this won't have a big impact. 

After a temporary frenzy, there might just be a mess.