Diamond autobuyer stops functioning if diamond goes above 1e1No

[PythonTryHard]

Version tested on: GitHub (v2.7.0 - Seal of the Merchant [Last Update: 23:38 UTC 6-Sep-2021])

Enviroment: Windows 10 2004 (build 19041.1165), Firefox 92.0 stable release branch.

Steps to reproduce:

1. Start a clean run since we're pushing resources.
2. (Optional) Disable diamond autobuyer. Recommended for most visible result.
3. Push challenge/research/runes/talisman to push diamond past 1e1No (one e one nonillion).
4. If step 2 is performed, re-enable autobuyer. Otherwise just compare the Diamond producers' cost to current resource.

Note:

• Tested also on local Chrome 93.0.4577.63 stable release branch. Reproducible.
• Independently verified on 01 (one) friend's machine as reproducible to ensure the bug not being somehow machine-specific.

Expected behaviour:
Diamond autobuyer functions as normal.

Actual behavior:
Assuming reproduction step 2 is performed, all autobuyer does not autobuy even when re-enabled:

This can be partly confirmed as not being visual bug by Transcending/Reincarnating thanks to a different coin production multiplier: