Random part errorring after restart
rubensworks opened this issue ยท 1 comments
Parts can become errorred after a server restart.
Can also happen when re-validating networks (such as placing a cable)
(Randomly try to re-enable inactive parts to improperly catch such bugs for now)
Variables don't reference other variables.
activeAspect
in PartStateWriteBase
can become null for some reason.
Can ONLY happen in in PartTypeWriteBase#updateActivation
, so when a network element is deactivated (activeAspect
set to null), but later again not activated again.
The cause of this might be clashing network elements because of a wrong compareTo implementation.
SMP-only?