Thanks for the info @Ciastex
I’ve been working on this problem when anytime I get a spare moment and hopefully it’ll be smoothed out when we release version 3.8
Unfortunately, it’s a bit of a multifaceted problem and everytime I think I’ve come close to a good solution I run into something else that makes it a little bit more complicated. The behavior of MonoGame and NuGet are both contributing to the problem (and the behavior has changed over the years) which makes this considerably more difficult.
Worst case, we might have to fall back to having a README file that explains the issue and how to work around it. I think I can get the README to display when the NuGet package is installed, so at least it’ll be in your face rather than scattered across the internet.