Co-authored-by: nea <romangraef@gmail.com>
Co-authored-by: nea <nea@nea.moe>
Co-authored-by: Roman / Linnea Gräf <roman.graef@gmail.com>
Co-authored-by: nopo <nopotheemail@gmail.com>
Co-authored-by: hannibal2 <24389977+hannibal00212@users.noreply.github.com>

Co-authored-by: Vixid <52578495+Vixid1@users.noreply.github.com>

Co-authored-by: hannibal2 <24389977+hannibal00212@users.noreply.github.com>

Show magical power at accessory bag in skyblock menu.

Co-authored-by: hannibal2 <24389977+hannibal00212@users.noreply.github.com>

Co-authored-by: Lulonaut <lulonaut@tutanota.de>

* Added Sky Mall to Dwarven Overlay.

* Made SkyBlockTime a data object.

* Added color to names and display item per different perk variant.

* Added daySuffix support for days greater 10.

* Data classes have a copy method already.

* Green color does not work.

* Fixed a bug in monthName.

* Add Unit Tests and make use of Instant

* Fixed Sky Mall overlay showing in crystal hollows.

* 11st
12nd
13rd

---------

Co-authored-by: hannibal2 <24389977+hannibal00212@users.noreply.github.com>
Co-authored-by: nea <nea@nea.moe>
Co-authored-by: nopo <nopotheemail@gmail.com>

* Rename .java to .kt

* hotm rework.

* Moved class to kotlin directory.

* Removed debug.

* Support for maxed out levels.

* Fun fact of the day: Developer waste more time on the name of a variable than actual coding.

* default is 0

---------

Co-authored-by: hannibal2 <24389977+hannibal00212@users.noreply.github.com>

`CacheResult` should in theory have either a `file != null` a `future !=
null` or be `disposed`. Apparently this invariant of `CacheResult` is
either being violated somewhere, or the `synchronized` blocks arent as
synchronized as id hoped they were. In fact, `dispose()` does not even
delete the file, so i can really only see this happening because the
first `synchronized` block that writes the file and the second
`synchronized` block that reads from the file hold the same lock.

I have no idea how this would happen, but hopefully this fixes it (since
the dispose didn't have a threading issue reported so far, i feel more
confident leaving the .deleteOnExit in there, but I'm also wrapping any
potential IOExceptions during access, because I am just so confused how
the internal state was broken.