Minecraft Server Sponsorship, Cleared Against the Guidelines

Half of what an agency proposes for Minecraft is not permitted, and the fastest money I save a client is the two weeks they would have spent designing something Mojang's usage guidelines forbid. So the first deliverable is a memo mapping your brief line by line to the specific clause that allows or blocks it: naming, monetisation, asset use, and what may be said publicly about the relationship. Only then does a server partner get contacted. Where the audience is: Java networks and Bedrock are two different businesses with two different rulebooks. The Marketplace is a closed shop reached through an approved partner studio, with featuring that Microsoft controls and nobody outside it can promise. Java networks and the large modpack communities on CurseForge and Modrinth are negotiated directly, run on Paper or Spigot behind a Velocity proxy, and reach players who are older and considerably more technical than most brand teams assume. Which side of that line your brief belongs on is the first real decision, and it is made against numbers rather than preference. Diligence on the partner: I read a server's own store before I read its traffic. A network selling gameplay advantage is already in breach and one enforcement message away from going dark with your campaign on it. I check monetisation model, moderation staffing, chat filtering, incident history, and whether the operator has ever been contacted about compliance. Two of the last partners I recommended were the third and fourth choices on the shortlist for exactly this reason, and both engagements finished their seasons. What compliant sponsorship looks like: A branded server-side experience with its own plugin work, a season with a start and an end date, cosmetic-only rewards, and copy describing the relationship in language the guidelines permit. I write the build specification and manage the plugin developer. I do not write the plugin. Reward structure, event cadence and the announcement calendar go into the contract rather than into an email thread after signature. The money: Operators price on a mixture of concurrents and goodwill, and the first number is rarely the last one. I negotiate on delivered player-days and season length, with payment tranched against events actually delivered, and I work from the operator's own back-end figures rather than a screenshot of a player counter. Measurement: Counting is server-side: unique joins to the branded world, join-to-return rate across the season, minutes inside the branded content against minutes elsewhere on the network, and referral traffic to whatever you want people to do next, whether that is a graduate application, a documentation site or a careers form. Discord referrals and redemption codes close the loop where recruitment is the objective. The operator's public player counter is not a metric and does not appear in reporting. What I refuse: Anything requiring pay-to-win mechanics or a reward carrying gameplay advantage. Any claim of endorsement by Mojang or Microsoft. Any promise of Marketplace featuring, from me or from anybody else. And a brief where legal will not accept the residual risk present in every third-party server relationship: you do not control the community, and a moderation failure can happen with your name on the door. Not included: Plugin engineering, world-building labour and hosting costs. Community management during the season, which belongs with the operator or an agency that staffs it. Localisation beyond English and Polish. Not for you if: You want reach measured against Minecraft's total player base. That number is real and irrelevant. The reachable audience for any single sponsorship is smaller by three orders of magnitude, and the plan says so on page one rather than in a footnote.