The current implementation of LEGACY_METEORITE creates a clone of the meteorite every time the RelicManager is reset. This causes a new clone to be created whenever a new run is started.
It should be possible to detect if a relic already exists for LEGACY_METEORITE and skip making a new clone.
This is a small optimization that is worth doing, but shouldn't cause any direct issues (to my knowledge). I'll leave this issue open and fix it when I have some more time, thanks for reporting! 👍
The current implementation of
LEGACY_METEORITE
creates a clone of the meteorite every time theRelicManager
is reset. This causes a new clone to be created whenever a new run is started.It should be possible to detect if a relic already exists for
LEGACY_METEORITE
and skip making a new clone.