Possibly...although the idea is to provide variety and to discourage a player from merely picking all research without a true strategy. The concept is to give more of a divergent research approach.
With this version of the game having an additional 1200 items to research, the consideration was that this would be too overwhelming if the player assumed a need to research everything.
So far it has provided some interesting results.
Regardless, currently this project is on hold until the background complexity issue can be addressed. The game functions perfectly...until it simply no longer does. There is no real sense of why it suddenly decides to cause all Motherships to self-destruct, but it seems to occur when the memory usage is around 700 MB and there is heavy space traffic.
Current options are to remove the space traffic, or seek to somehow further reduce the memory load.
Likely it will be the former, but I have not yet decided.
ALC - Sat Sep 22, 2018 11:26 pm
Self destructing Mother Ships is a significant bug.
Could something be causing their health to suddenly be set to zero for some reason. In the absence of a MS, does the same issue affect the most importsnt build ship of a given fleet, I wonder.
Jelrak - Sun Sep 23, 2018 1:30 am
They simply spin off of the map with full health and then explode. Other ships are able to keep building, presumably even to reconstruct a new mothership, so it does not appear to affect anything else. It seems to happen typically if there is more than a single computer opponent and the number of different automated ships exceeds an undetermined number. It typically results soon after some ships become invisible. It has been very curious to observe.
Jelrak - Mon Sep 24, 2018 5:15 am
The number of automated ships is not relevant to this problem...nor is this caused by any obvious memory draw. I will have to investigate if this is caused by a function, and, if so, which one is responsible