Terms & Privacy

Guizhan Resources Content Rules

Effective date: August 19, 2026

The Guizhan Resources Content Rules (these Rules) form part of the Guizhan Resources Additional Terms of Service (the Terms), and apply to all user-contributed content, game content, and use of interactive services (Content, Projects).

We may hide or remove any Content that violates these Rules without prior notice, including actions not explicitly listed as permitted or prohibited in these Rules.

If you encounter any Content that violates these Rules while using the Service, please report it to us at support@guizhanss.com.

Projects

Project Names

  • A project name should consist solely of the name of the project itself, and must not contain version numbers, slogans, taglines, or unnecessary filler words.
  • A project name should be distinctive, and must not be identical or confusingly similar to another project.
  • Unless explicitly authorized, project names and page information must not impersonate or imply an official affiliation with, or endorsement by, Mojang, Guizhan Technology, or any other organization.
  • Without the rights holder's permission, you may not use others' brands, servers, or project names in your project name or page information for promotional purposes.

Project Descriptions

Project descriptions should be clear and honest. Before downloading your project, users should be able to learn from the project page:

  • What the project is and what it does
  • Why it is worth downloading
  • What they need to know before downloading and using it (such as required dependencies, configuration requirements, and known limitations)

All information on the project page (including the description, icon, screenshots, and videos) should match the actual content of the project, and must not contain false, exaggerated, or misleading content. Screenshots and videos should demonstrate the project's actual in-use behavior.

Project Metadata

  • The project's category, tags, license, and supported platforms and game versions should be filled in accurately and updated promptly when they change.
  • External links on the project page (such as source code, documentation, and feedback channels) should be relevant to the project and point to publicly accessible resources.
  • The project's icon and cover images must not contain inappropriate content or infringe others' intellectual property rights.

Prohibited Content

The following types of content are strictly prohibited:

  • Illegal content: any content that violates applicable laws and regulations
  • Malicious content: content containing viruses, trojans, malware, or other harmful code (see also Malicious Behavior)
  • Harassment and hate: content that harasses, threatens, or bullies others, or incites hatred or discrimination
  • Violence and gore: excessively violent, gory, or disturbing content
  • Adult content: pornographic, sexually suggestive, or otherwise age-inappropriate content
  • Personal information: publishing others' personally identifiable information without authorization
  • Spam: junk messages, irrelevant advertising, or promotional content
  • Fraudulent content: deceptive, misleading, or false content
  • Infringing content: content that infringes others' copyrights, trademarks, or other intellectual property rights
  • Destructive content: content intended to disrupt the normal operation of other servers, services, or devices

Malicious Behavior

Malicious Code

  • Content must not contain functionality that harms users, servers, or devices, such as deleting or tampering with data, crashing clients or servers, or modifying system configurations without authorization.
  • Content must not contain backdoors, including but not limited to granting or revoking privileges for specific users or user groups at the author's personal discretion (such as special permissions or commands reserved for the author).
  • Content must not evade, interfere with, or counteract security software or review processes in any way.

Data Collection

Content must not upload user data to remote servers without clear disclosure. If data collection or upload is required for functionality, the data collected and its purpose must be clearly stated in the project description.

Cheats and Hacks

Distributing cheat-type content that gives users an unfair advantage in multiplayer environments without a way for server operators to opt in or out is prohibited, including but not limited to client modifications with X-ray, aim assistance, flight or abnormal movement, automated combat, or item duplication features.

You must own the legal rights to the content you upload, or have obtained authorization from the rights holder.

Reuploads and Translations

  • You may not directly reupload others' projects without the original author's explicit permission, including versions with only minor changes.
  • Reuploaded or translated projects with permission must credit the original project's name, original author, and authorization status in a prominent position on the project page, and must not bundle functionality, advertising, or other content unrelated to the original work.

Forks

  • A fork should differ substantially from the original work, or serve to continue a project that the original author has stopped maintaining.
  • A fork must credit the original work and its original author.

Licenses

  • You must accurately select and declare a license for your project, and comply with the license requirements of others' works that you use.
  • If the license declared on the project page conflicts with the license included in the files, the license declared on the project page shall prevail.

Obfuscation and Code Visibility

We encourage you to make your project's source code publicly available.

  • Basic obfuscation is allowed, but the decompiled code must remain readable and reviewable by us.
  • Obfuscation must not hide the project's package root or main class name.
  • Using class encryption, string encryption, or other means to hide code logic is prohibited.
  • For review purposes, we may ask you to provide an unobfuscated version; if you cannot provide one, the relevant content may be removed.
  • For projects submitted through our automated build service, the build artifacts must originate from the source code repository you declared.

Monetization and Advertising

  • Projects and their features must not be locked behind paywalls, license keys, or any form of digital rights management (DRM); projects should run directly from the downloaded files.
  • Using monetized links (such as ad-redirect short links) is prohibited.
  • Project pages may contain links relevant to the project (such as source code, documentation, and feedback channels) as well as donation links, but promotional content must not become the main body of the project page. Projects that exist solely to promote other products or services will be removed.

Versions and Updates

Version Releases

  • Version updates should contain actual changes. You may not publish updates without substantive content (such as re-uploading identical files) to boost the project's visibility.
  • You must not manipulate download counts, favorites, or other project statistics, including using multiple accounts or automated tools to repeatedly download.

Dependency Declarations

Each version should accurately declare its dependencies (required and optional), as well as its supported platforms and game versions.

External Download Links

We recommend distributing your project's files directly through the Service. When using external download links, the links must point directly to the file of the corresponding version, and must not point to pages that require registration, login, or payment to download, nor redirect through monetized links.

Generative Artificial Intelligence

  • Content produced wholly or primarily by generative artificial intelligence (AI) must be clearly disclosed in the project description.
  • Bulk-uploading low-quality AI-generated content is prohibited.
  • AI-generated content is equally subject to all provisions of these Rules, including copyright and quality requirements.

Minecraft End User License Agreement

Projects should comply with the Minecraft EULA and related usage guidelines. Projects whose explicit purpose is to bypass Mojang account authentication will be removed.

Enforcement

Review

All projects you submit must pass our review before they are made public. Content passing review or being available on the Service does not constitute our endorsement, approval, or guarantee of that content.

Penalties

Violating these Rules may result in:

  • Content being hidden or removed
  • Account warnings, suspension, or permanent bans
  • Loss of content upload privileges
  • Reports to relevant law enforcement authorities for serious violations of the law

The severity of penalties depends on the nature and severity of the violation. Penalties escalate progressively for repeated violations.

We reserve the right to take any action we deem necessary or appropriate at our sole discretion, including but not limited to the measures listed above.

Reports

If you discover content or behavior that violates these Rules, please report it to us at support@guizhanss.com. We will review all reports and take appropriate action.

Please do not abuse the reporting channel. Malicious or false reports may result in penalties to your account.

Intellectual property rights holders may also submit infringement complaints via this email address.

Appeals

If you disagree with our decision, you may appeal via support@guizhanss.com, and we will conduct a review. We have the final say in the interpretation and enforcement of these Rules.