Yeah i would too, but i’m kinda on the fence about it. On one side, if it’s going to take years to get to the point of looking at adding support you could let a third party extend your product adding c# and the cross platform benefits that comes with mono. Then when you’re ready and .net core matures/covers the platforms required you could add your own first class support for the language. On the other side doing it all properly as a first class language would potentially give a better experience and wouldn’t make a third party’s plugin redundant if you add your own support. but it does mean not being able to tap into that market for a number of years, giving other competing products a chance to gain a foothold. (but who’s to say they couldn’t still sell Xamarin Studio -> UE integration and debugging support for C# if this happened, jsut with .net core instead of mono)
It also makes me wonder If Mono is basically the same .net interfaces, how hard would it be to swap mono for .net core? From the actual game code side it shouldn’t be that hard in theory (the part that would probably change is the interface wrapping UE API’s).