Bedrock Commands Community Public License (BCC-PL) v1.0

Plain-language summary (non-binding):

• Code is under the MIT License — you can freely use, share, or commercialize it.
• Creative Assets (builds, textures, models, sounds, music, art, etc.) are under this License (BCC-PL).
  • You may remix and share Derivative Works, as long as you preserve attribution and include this License.
  • You may not redistribute the unmodified Project — only the Project Licensing Representative (PLR) can do that through Official Channels.
  • You may not commercialize Creative Assets without Explicit Permission from the PLR.
• Content creation (e.g., YouTube, streams) is allowed and may be monetized, as long as you credit “Bedrock Commands Community”.
• This summary is provided for convenience only. The full License governs all use of the Project.

1. Purpose

This License distinguishes clearly between two categories of content:

• Code-Based Elements (scripts, functions, and logic) are licensed solely under the MIT License and may be freely used, modified, redistributed, or commercialized in accordance with that license.
• Creative Assets (all non-code assets such as builds, textures, models, sounds, and structures) are licensed under this License (BCC-PL). These may be used and remixed, but are subject to restrictions on redistribution and commercialization set out below.

This License ensures that Creative Assets released through the Bedrock Commands Community Discord’s Annual Map Making Program remain open for public use and modification, while commercial uses of Creative Assets are managed solely by the Project Licensing Representative. This section explains the intent of the License and is not itself a condition of the License.

2. Definitions

• 2.1 “Project”
  • (a) Refers to any designated GitHub repository under the @BedrockCommands organization that has been explicitly included in the Bedrock Commands Community’s Annual Map Making Program, as indicated in the repository README or description by the Project Licensing Representative or Authorized Staff.
  • (b) The Project includes both:
    • (i) Code-Based Elements (as defined under 2.2); and
    • (ii) Creative Assets (as defined under 2.3).
  • (c) The Project covers all such content whether distributed in source form or packaged into alternate formats such as .zip, .mcworld, or any other format shared via Discord, Minecraft Marketplace, or successor platforms.
  • (d) For avoidance of doubt, the Project includes both individual Contributions and the collective assembly of Contributions, including any related versions, derivative works, or distributions.
  • Informal explanation (non-binding) For everyday players, “the Project” simply means the map (including its code and creative assets), in whatever form it is downloaded or obtained.
• 2.2 “Code-Based Elements”
  • (a) Means solely the set of scripts, functions, logic modules, and other programmable or executable content.
  • (b) License: All Code-Based Elements shall include an MIT License header and are licensed to downstream users under the MIT License.
• 2.3 “Creative Assets”
  • (a) Means all non-code assets—such as audio files, visual files, model geometry files, world files, and structure files—that are intended for artistic, design, or sensory purposes. This category includes:
    • All files within the models/, textures/, sounds/, structures/, or music/ directories.
    • Any other creative, design, or art-oriented files integrated into the Project that fall outside of Code-Based Elements.
  • (b) License: Creative Assets are licensed to downstream users under this License (BCC-PL), with the BCC-PL header included where technically feasible.
• 2.4 “Bedrock Commands Community Discord” or “BCC”
  • Refers to the informal online community hosted on Discord, at the server with ID 924894457894174740, which collaboratively organizes and contributes to the Project via the GitHub organization @BedrockCommands. The term is used solely for purposes of attribution and community identity. It does not represent a legal entity and holds no ownership, enforcement rights, or responsibilities under this License.
• 2.5 “Project Licensing Representative” or “PLR”
  • (a) Refers to the individual currently authorized to manage all rights and legal matters for the Project, initially designated as the Discord user @.zruby (711962234431078490). All legal authority for licensing, enforcement, and intellectual property management under this License is exercised by the Project Licensing Representative on behalf of all Contributors, pursuant to mutual agreement as formalized in the BCC Contributor License Agreement (BCC-CLA).
  • (b) In the event the Project Licensing Representative can no longer act, they may designate a successor in writing. Such successor shall assume all rights and obligations under this License.
• 2.6 “Contributor”
  • Refers exclusively to any individual recognized as a Contributor under the BCC Contributor License Agreement (BCC-CLA), which includes those who have digitally signed the CLA and whose Contributions (whether Code-Based Elements, Creative Assets, or other material) have been formally submitted via pull request and merged by the Project Licensing Representative or Authorized Staff.
• 2.7 “Contribution”
  • (a) Any original work of authorship submitted by a Contributor to the Project, as recognized under the BCC Contributor License Agreement (BCC-CLA).
  • (b) This includes, but is not limited to, Creative Assets and Code-Based Elements.
  • (c) Contributions must be formally submitted (e.g., via pull request) and accepted by the Project Licensing Representative or Authorized Staff to qualify.
• 2.8 “Derivative Work”
  • Refers to any work based upon, incorporating, or adapting elements of the Project that includes sufficient creative expression to constitute a new work of authorship under the copyright laws of England and Wales. Purely trivial or de minimis modifications (e.g., renaming files, reordering data, or replacing blocks without substantial transformation) shall not qualify as a Derivative Work under this License.
• 2.9 “Explicit Permission”
  • Written authorization—either signed or otherwise electronically confirmed—by the Project Licensing Representative that specifically permits a particular use otherwise prohibited under this License (BCC-PL), the BCC Contributor License Agreement (BCC-CLA), or both. Requests for Explicit Permission must be sent to [email protected] or the current contacts provided on the Project’s official channels. The Project Licensing Representative or Authorized Staff may respond within thirty (30) calendar days; failure to respond does not imply permission.
• 2.10 “Authorized Staff”
  • Any BCC project director, coordinator, department lead, or moderator appointed by the Project Licensing Representative to act on their behalf under this License, as expressly designated through verifiable Discord role assignments in the Bedrock Commands Community Discord (Server ID: 924894457894174740).

3. Public Rights, Restrictions, and Commercial Licensing

• 3.1 Scope of Use
  • This section applies only to Creative Assets.
  • Code-Based Elements are excluded and governed solely by the MIT License.
  • Derivative Works that combine both remain subject to both licenses: MIT for code, BCC-PL for Creative Assets.
• 3.2 Redistribution
  • Redistribution is permitted only for Derivative Works.
  • The original Project—or any version that is not a Derivative Work—may not be redistributed by third parties.
  • Only the Project Licensing Representative or Authorized Staff may distribute the original Project through Official Channels (§12).
  • However, creating and maintaining GitHub forks of the original repository are permitted for collaboration and version control, but any Creative Assets in such forks remain subject to this License (BCC-PL).
• 3.3 Commercial Restrictions
  • Any Derivative Work that incorporates Creative Assets from the Project, even alongside third-party code or assets, may not be commercialized in any form without Explicit Permission from the Project Licensing Representative.
  • The Project Licensing Representative retains exclusive rights to authorize or monetize Creative Assets, including distribution on commercial platforms such as the Minecraft Marketplace.
• 3.4 Content Creation
  • Individuals may create and monetize content (e.g., videos, livestreams) featuring the Project.
  • Attribution to Bedrock Commands Community is required, with a link to an official Project download page. Acceptable forms include:
    • Verbal credit in the introduction.
    • On-screen credit at the beginning or end.
    • A notice in the video description.
    • A pinned comment containing the credit and link.
  • If platform limitations prevent attribution, creators must provide credit to the best of their ability.
  • If attribution is impossible, the content may not be shared under this License.
• 3.5 Attribution and License
  • Any redistribution of a Derivative Work containing Creative Assets must:
    • include an unaltered copy of this License; and
    • provide attribution to Bedrock Commands Community and all original Contributors whose Creative Assets are included in a visible and appropriate manner in the README File and/or in-game.
  • No party may misrepresent the origin of the Project or claim it as entirely their own.

4. Governing Law, Enforcement, and Dispute Resolution

• 4.1 Governing Law
  • This License is governed by and construed in accordance with the laws of England and Wales, without regard to conflict of law principles.
• 4.2 Dispute Resolution
  • Any dispute, controversy, or claim arising out of or in connection with this License shall first be referred to good-faith online mediation between the parties, using reasonable electronic means such as email or messaging platforms.
  • If the dispute is not resolved within thirty (30) calendar days of the commencement of such mediation, either party may submit the dispute to online arbitration administered by a commercially recognized and independent arbitration provider, or to any alternative dispute resolution method agreed in writing by the parties.
  • The arbitration or alternative dispute resolution shall be conducted entirely online or remotely, and the laws of England and Wales shall apply.
  • Notwithstanding the foregoing, claims within the monetary jurisdiction of a UK small claims court may be brought directly to such court without prior mediation or arbitration.
• 4.3 Enforcement Procedures
  • Violations will be notified in writing by the Project Licensing Representative.
  • If the violation is not remedied within thirty (30) calendar days of notification, enforcement may commence.
  • Rights granted under this License are revoked for the violating party only.
  • The Project Licensing Representative may seek injunctive or equitable relief in any court of competent jurisdiction to prevent ongoing or imminent infringement of Creative Assets.
  • Upon termination, all rights previously granted under this License immediately cease for the violating party.
• 4.4 Costs and Fees
  • The prevailing party in any enforcement, arbitration, or court proceeding is entitled to recover costs reasonably incurred in connection with the proceedings, including administrative or filing fees.
  • Legal representation costs are recoverable only if voluntarily incurred by the prevailing party.
• 4.5 Interpretation and Severability
  • Ambiguities shall be resolved to give effect to the purpose and spirit of this License.
  • If any provision is found to be invalid, illegal, or unenforceable, the remaining provisions remain in full force and effect.

5. Contributor Rights

• Contributors retain ownership of their individual Contributions and may independently use, modify, redistribute, or commercialize their own Contributions in isolation, provided such actions do not conflict with this License or the terms of the Contributor License Agreement.
• Contributors may not claim ownership of, or commercially exploit, the entire Project, any parts of the Project beyond their own Contributions, or any Derivative Works or collective compilations that incorporate Contributions from multiple parties.
• Contributors must promptly notify the Project Licensing Representative or Authorized Staff of any independent commercialization, relicensing, or redistribution of their Contributions.

6. Open Code Licensing

• All Code-Based Elements are licensed solely under the MIT License.
• The BCC-PL applies exclusively to Creative Assets.
• In Derivative Works containing both:
  • MIT License governs Code-Based Elements;
  • BCC-PL governs Creative Assets;
  • Commercial use requires Explicit Permission unless all Creative Assets are removed.
• The MIT License does not override Creative Asset restrictions.

7. Circumvention Prohibited

• Licensees may not disguise, restructure, or repackage files to evade application of this License (BCC-PL) to Creative Assets.
• Any such attempt constitutes a material breach and terminates rights granted herein.

8. No Warranty

• The Project is provided “as-is,” without warranties of any kind.
• Contributors, the Project Licensing Representative, and Authorized Staff disclaim all liability for damages resulting from its use.

9. License Versioning

• The Project Licensing Representative or Authorized Staff may update this License.
• The latest published version of this License governs all new distributions of the Project.
• Works previously distributed remain governed by the version of the License under which they were originally released.

10. Trademark and Attribution Notice

• The term “Bedrock Commands Community” is used solely for attribution and community identity purposes. It is not a registered trademark, nor does it represent a legal entity. Its appearance in connection with redistributed versions of the Project does not imply legal ownership, formal endorsement, or representation unless explicitly stated by the Project Licensing Representative.
• Misrepresentation of the Project’s origin, authorship, or affiliation using this identifier is prohibited.
• The Discord server officially representing the Bedrock Commands Community for the purposes of this License is identified by server ID 924894457894174740. The official GitHub organization for publishing and managing the Project is @BedrockCommands.
• No other server, GitHub account, group, or entity is authorized to represent or act on behalf of BCC unless explicitly designated by the Project Licensing Representative.

11. Exclusions for Vanilla or Third-Party Assets

• This License applies only to original Creative Assets contributed to the Project.
• It does not apply to:
  • Creative Assets identical to or derived solely from Mojang’s vanilla Minecraft, which remain subject to Mojang’s EULA and policies; or
  • Third-party assets included in a Derivative Work but not part of the Project, for which the creator of the Derivative Work is solely responsible.

12. Official Channels

• The following are the currently designated official publication channels of the Bedrock Commands Community Discord:
  • Website: https://bedrockcommands.org
  • GitHub Organization: https://github.com/BedrockCommands
  • Discord Server ID: 924894457894174740 (official Bedrock Commands Community Discord server)
• These links and identifiers are provided for clarity and verification. The Project Licensing Representative or Authorized Staff may update this list as needed by publishing notice through these official channels.

End of License