Currently, matter generation is broken due to the matter field being initialized too early in the MatterType enum.
The fix, which turns out to be simple, is to make use of kotlin's lazy to let the game initialize the field when it's first used, then value gets cached afterwards.
Currently, matter generation is broken due to the
matterfield being initialized too early in theMatterTypeenum.The fix, which turns out to be simple, is to make use of kotlin's lazy to let the game initialize the field when it's first used, then value gets cached afterwards.