Would it be easier if you hop into my repo or me sending a dev build? It happens quite a lot, but I can't tell where it's coming from.

The best way to find the source of the problem will be to reproduce it in your project. What steps should I follow?
I have access to your repo, which branch should I use?

Use tactic-dev. New Game -> Skrimish (Humans). Settle a city. It has happened from clicking end turn, placing buildings, moving units... But I really can't tell what exactly does it. :(

Here is a video that shows the bug happen. I've repeated what I've done in this video but I can't always make it crash. https://files.catbox.moe/thel0c.mp4

I'm getting

NotImplementedException: The method or operation is not implemented.
Zenject.MonoInstallerBase.InstallBindings () (at Assets/Plugins/Zenject/Source/Install/MonoInstallerBase.cs:32)

when clicking Play, probably need to install or configure something to make it work.

You're on tactic-dev with commit c66aa5f5c16c74b7e4e3faa9ed9c90c27fced11a? How odd. Did you try restarting the editor? And can you send me the callstack for that?

Yes I'm on that branch and commit.

I noticed there are some scripts that can't load due to compiler errors (like AppInstaller), and reimporting Project/Source/Core I get this

Assembly 'Library/ScriptAssemblies/Assembly-CSharp.dll' will not be loaded due to errors:

Reference has errors 'Empis.Master'.

Assembly 'Library/ScriptAssemblies/Assembly-CSharp-Editor.dll' will not be loaded due to errors:

Reference has errors 'Assembly-CSharp'.
Assembly 'Assets/Plugins/Empis.Master/netstandard2.0/Empis.Master.dll' will not be loaded due to errors:

Empis.Master references strong named Microsoft.AspNetCore.Http.Features Assembly references: 2.2.0.0 Found in project: 3.1.10.0.

Assembly Version Validation can be disabled in Player Settings "Assembly Version Validation"

I have no idea why this would happen. Could I send you a development build of the game?

If I can reproduce the crash in the player then yes.

UPD: Nevermind, I closed Unity, reverted a few files that were modified by Unity and after restarting it works fine.

Oh, that's great to hear!

The problem I'm seeing is that you are raising property change notifications from different threads and our objects can only be invalidated from Unity main thread.

Notify Empis.Unity.ViewModels.ProductVM.CanBuild

UnityEngine.StackTraceUtility:ExtractStackTrace ()

UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])

UnityEngine.Logger:Log (UnityEngine.LogType,object)

UnityEngine.Debug:Log (object)

Noesis.Extend:NotifyPropertyChanged (object,System.ComponentModel.PropertyChangedEventArgs) (at Assets/NoesisGUI/Plugins/API/Core/Extend.cs:5219)

Empis.BindableObject:NotifyPropertyChanged (string) (at Assets/Project/Source/Game/BindableObject.cs:15)

Empis.BindableObject:Set<bool> (bool&,bool,string) (at Assets/Project/Source/Game/BindableObject.cs:22)

Empis.Unity.ViewModels.ProductVM:set_CanBuild (bool) (at Assets/Project/Source/ViewModels/ProductVM.cs:104)

Empis.Unity.ProducerViewer/<>cDisplayClass46_0:<UpdateProductBindings>b1 (Empis.Unity.ViewModels.ProductVM) (at Assets/Project/Source/Viewers/Components/ProducerViewer.cs:111)

System.Threading.Tasks.Parallel/<>cDisplayClass31_0`2<Empis.Unity.ViewModels.ProductVM, object>:<ForEachWorker>b0 (int)

System.Threading.Tasks.Parallel/<>cDisplayClass17_0`1<object>:<ForWorker>b1 ()

System.Threading.Tasks.Task:InnerInvoke ()

System.Threading.Tasks.Task:InnerInvokeWithArg (System.Threading.Tasks.Task)

System.Threading.Tasks.Task/<>cDisplayClass178_0:<ExecuteSelfReplicating>b0 (object)

System.Threading.Tasks.Task:InnerInvoke ()

System.Threading.Tasks.Task:Execute ()

System.Threading.Tasks.Task:ExecutionContextCallback (object)

System.Threading.ExecutionContext:RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)

System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)

System.Threading.Tasks.Task:ExecuteWithThreadLocal (System.Threading.Tasks.Task&)

System.Threading.Tasks.Task:ExecuteEntry (bool)

System.Threading.Tasks.Task:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem ()

System.Threading.ThreadPoolWorkQueue:Dispatch ()

System.Threading._ThreadPoolWaitCallback:PerformWaitCallback ()

I see, thanks for the info.

We added support in Unity for logging from different threads, so errors produced by using the UI elements from different threads are now properly shown.