Yeah that might be it (the Web broswer)Textractor can too, google up sugoi translator.
I think it's something like using web acces instead of API or smth. (I'm not that knowledgeable)
I see. I could see so many people using your Tool to translate games since it just works and is comfortable.Some reasons:
It's too expensive. ( I actually can't afford to launch any new translation engine with the current volume of users. Unless I raise the user price or reduce the user translation limit.)
DeepL does not support credit cards from my country.( Although the card can be spent in US dollars )
And I think the access without Key is Not enough stable. ( Use in a production environment. )
You might consider: that DeepL (or any other engine) costs $25 per million words translated.
Any game can exceed that size. 1 million words is about 1m-3m in size.
So when I added the new engine:
Users translate a lot of games that have not been translated by this engine.
Game Over.
I don't have a lot of money in reserve for adding new engines.
I think Bing are better.Yeah that might be it (the Web broswer)
I see. I could see so many people using your Tool to translate games since it just works and is comfortable.
I always wondered, since you offer more Translator if you are A Patreon, is there any better than google? (Japanese --> English)
I really don't know how your software works so forgive me if I'm completely wrong in my assumptions and unhelpful.reduce the user translation limit.)
Not bandwidth, is the translate.I really don't know how your software works so forgive me if I'm completely wrong in my assumptions and unhelpful.
What it looks like is that every time someone starts a game they need to have the software operate and exchange information with the server. Often RPGs take multiple sessions to finish. Which means that bandwidth is consumed multiple times for the same person playing the same game.
If the software saved the translation information it received from your server when it was finished locally, then afterwards would use that information instead of contacting the server to re-translate for every session then you could reduce bandwidth use.
Charging users directly for translations under this model would be very expensive.Ahh I understand. The problem that you're running into is that the service you provide is dependent on a service someone else provides. Because you're operating through patreon you can't charge a user for each translation they request.
In order to expand you'd need to either restructure your business to operate independent of patreon, maybe partnering with the companies that do the translations? Or remove your dependency on the translation companies by handling the translation yourself, which is not ideal. Unless you do either of those things you're just going to have to charge more money.
Whoa, snowball much? I didn't think that far.