im lazy of commit naming smh

Because of such a high conversion rate, this actually needs careful consideration and excessive testing. As most calculations are done in 64 bit types these eye-candy conversion rates eat up bits from useful values and this one just uses 2 more bits than everything else. And I remember there already being some issues with overflowing money, not sure if they were all fixed. It's also quite bad for the UI to have all those pointless numbers at the end. So I think it would be much better from both UI and implementation pov to add such currencies in thousands, so this one would be a "thousand rupiahs" currency with the conversion rate of 19.

Because of such a high conversion rate, this actually needs careful consideration and excessive testing. As most calculations are done in 64 bit types these eye-candy conversion rates eat up bits from useful values and this one just uses 2 more bits than everything else. And I remember there already being some issues with overflowing money, not sure if they were all fixed. It's also quite bad for the UI to have all those pointless numbers at the end. So I think it would be much better from both UI and implementation pov to add such currencies in thousands, so this one would be a "thousand rupiahs" currency with the conversion rate of 19.

ok imma fix it

Because of such a high conversion rate, this actually needs careful consideration and excessive testing.

FYI: Everyone can already test this by using the manual currency and setting the max value. I think I'm going to play with such a fantasy currency from now on. I'll report back (in other issues) if I find any bugs.

About the "thausand rupees" thing: Shouldn't the suffix change then, or is this intended?