Key Features
Regional pricing is not that difficult of a problem, unless you're targeting particular customer bases and want to introduce discounts. So, I expect you'll always have devs who can't be bothered, and will opt for the defaults.
Those who want to do the additional legwork won't face that many problems with calculations, although admittedly your tool makes it easier for them. But what's the genuine difference between the default and your prices, and how much of a customer base is actually lost in that difference?
In fact, to reframe this more optimistically, I'd suggest you reach out to people at Steam (and other platforms) who are working on this. Since your tool is already free, you can aim for even more impact and tell them why their current system is wrong, why this matters and why yours is better.
If you want to adapt this to something you can monetize, I'd suggest introducing more complex considerations into the mix. What if I wanted regional pricing and info when to apply discounts where? What platforms should I support to get the most players from X country? You could leverage more data and advanced analytics to support complex decisions that users would pay for.
Just my two cents.
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.