New type in list can clash with genetics
Created by: clusterfack
Description of issue
I have become vaguely aware of a runtime where the list of mutations I believe will break due to interactions with the new genetics list. This occurs due to the fact that somewhere in the code is_type_in_list is being used to read from the list (which I don't believe it has any reason to) and the fact the genetics list is being modified at runtime, which doesn't work with the current is type in list schema.
This could be related to one or two other issues where genetics abilities are not applying the effects they should be.
Specific information for locating
Check runtime logs for examples of this runtime
Length of time in which bug has been known to occur
Since optimized is type in list was implemented