The crash file does not seem to be from Thrive at all so it is useless. The thrive crashes are in a folder next to the thrive logs folder.
The log actually has an exception in it, which is probably the crash reason (here it is formatted better):
------------ Begin of Unhandled Exception Log ------------
The following exception prevented the game from running:
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <c84d94161bca414384015e66544862cf>:0
at HexLayout`1[T].get_Item (System.Int32 index) [0x00000] in <ce785dc8d0874aee89478af416bacadf>:0
at Microbe.OnMulticellularColonyCellLost (Microbe cell) [0x0016b] in <ce785dc8d0874aee89478af416bacadf>:0
at Microbe.OnColonyMemberRemoved (Microbe microbe) [0x00066] in <ce785dc8d0874aee89478af416bacadf>:0
at MicrobeColony.RemoveFromColony (Microbe microbe) [0x0006a] in <ce785dc8d0874aee89478af416bacadf>:0
at Microbe.OnDestroyed () [0x0001a] in <ce785dc8d0874aee89478af416bacadf>:0 at Microbe.Kill () [0x0003e] in <ce785dc8d0874aee89478af416bacadf>:0 at Microbe.Damage (System.Single amount, System.String source) [0x001c9] in <ce785dc8d0874aee89478af416bacadf>:0
at Microbe+<>c__DisplayClass253_2.<OnContactBegin>b__2 () [0x00000] in <ce785dc8d0874aee89478af416bacadf>:0
at Invoke._Process (System.Single delta) [0x00088] in <ce785dc8d0874aee89478af416bacadf>:0
Please provide us with this log, thank you.
------------ End of Unhandled Exception Log ------------
So maybe this actually isn’t a random Godot crash, but it is a bit suspicious why the unhandled exception is so far up in the log. I really need to fix how people can copy logs from the launcher as I assume that’s the only way this very line break missing, mangled logs are posted, for the 2.0 version.
As to the actual stacktrace it seems to indicate that a cell that was not in a colony was attempted to be removed from a multicellular organism. I can add mitigation for that but the underlying bug is probably closely related to: