(I think there are technical and marketing reasons to be weary of as well, but the degree to which that matters is application specific. The above is universal and will probably continue to be the case through at least a few more major revisions if I had to guess).
> Operate official, unofficial, private or any otherwise competing BitCraft servers
Doesn't this contradict the Apache license? Isn't this "source-available"?
I'd imagine that by making a "BitCraft" server, it actually wouldn't violate the source code license terms at all, but they are putting you on notice that it would violate trademark and copyright on non-code things, so it wouldn't be legal irregardless of the code license.
Contents of the repo are fair game, anything bitcraft related outside the repo is not, and you have to share attribution under Apache - seems fair. I don't see any bitcraft assets or trademark things in the codebase, but I wonder how much of the game logic and play has to change before it's sufficiently different from the things being protected?
It's much more permissive than source available: you can use the source code for nearly any of your own projects, just not one specific application.
The developer open sourcing all of this is awesome.
Here's an blog post from them last year covering their open source plans: https://bitcraftonline.com/news/open-sourcing-bitcraft-onlin...
[1]: https://bitcraftonline.com/news/bitcraft-open-sourcing-updat...
But I don't know if it really fits the "Massive" aspect of MMO