Not really. That's a document explaining the rights you'd like to provide, but is not a legal copyright license - and unless you're a lawyer you shouldn't try to write one. Licenses are written in a specific unambiguous manner that will hold up in court. Your code was being distributed on our servers in various modpacks and running on modified servers (as this came up during an audit). Our lawyers only rarely review custom licenses - when they do we have to pay them hourly to do so. The industry standard practice of selecting an existing software license exists because the cost to have such licenses reviewed is so high. This also doesn't protect your rights as an author, for example what your LICENSE.md does not require attribution; you've allowed others to fork your work and include any amount of your code in their projects, which legally speaking could be 100% of your code only changing the trademarks. So Mr Hypothetical Badguy can fork your code, edit out your name and the mod's name, slap his own license on it, and distribute it claiming to be his own. For your sake as an author and for the sake of a few dozen of our users who've had their accounts temporarily suspended due to their inclusion of your mod, it looks like you're trying to get an effect similar to the MIT license. This is used for quite a few Minecraft mods. https://opensource.org/licenses/MIT The only thing the MIT license doesn't do is restrict redistribution of your modpack by itself, however as the trademark holder you may still enforce your right to determine who can use the trademark "mystical agriculture" and through which channels your official work may be distributed as a stand-alone product.

It wasn't a big deal until hosting providers started getting sued. Now we have to be paranoid and ensure all the legal rights are in place, because the legal fees alone for a lawsuit would be enough to end our company.