You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there's a way to have SimpleEnergyItems be unregistered from the "default" energy type? Currently, I have two energy items that are extended from a class that implements SimpleEnergyItem (and other behaviors that are not relevant to the issue).
All is dandy for the first item, since it is meant to use the default energy type. However, for the second, it's meant to use a custom energy type; I registered it manually to it - however, it's still registered to the default type (as all items that implement SimpleEnergyItem do), essentially allowing unintended 1:1 energy transferral.
Even if unregistering is an option, It'd be nice to have custom energy types support, since I wouldn't consider having what's essentially the same logic registered to other id enough to deem it complex/advanced to warrant having to use EnergyStorage.ITEM directly.
EDIT: Not long after I posted this, I found out I just had to register an empty EnergyStorage for the default type and it'd work 😅 Hopefully the request for built-in support, thus requiring no additional setup, is worth keeping the issue open.
The text was updated successfully, but these errors were encountered:
Hello,
I was wondering if there's a way to haveSimpleEnergyItem
s be unregistered from the "default" energy type? Currently, I have two energy items that are extended from a class that implementsSimpleEnergyItem
(and other behaviors that are not relevant to the issue).All is dandy for the first item, since it is meant to use the default energy type. However, for the second, it's meant to use a custom energy type; I registered it manually to it - however, it's still registered to the default type (as all items that implement
SimpleEnergyItem
do), essentially allowing unintended 1:1 energy transferral.Even if unregistering is an option,It'd be nice to have custom energy types support, since I wouldn't consider having what's essentially the same logic registered to other id enough to deem it complex/advanced to warrant having to useEnergyStorage.ITEM
directly.EDIT: Not long after I posted this, I found out I just had to register an empty EnergyStorage for the default type and it'd work 😅 Hopefully the request for built-in support, thus requiring no additional setup, is worth keeping the issue open.
The text was updated successfully, but these errors were encountered: