How to publish a release on MobCrafter Hub

Last updated: June 30, 2026

Before you upload

• You need a MobCrafter Hub account (Cloudflare Access login) to publish releases.
• Make sure all files you plan to upload are fully tested and working in-game before submitting.
• Read the Community Guidelines before your first submission. In particular, review the third-party IP and metadata rules — these are the most common reasons releases are rejected by moderation.
• If AI assisted any part of your creation, note that before starting. You will need to set the creation method and provide a disclosure note.

Step 1 — Screenshots

Screenshots are how users decide whether to download your release. The first screenshot you add becomes the thumbnail shown on Hub cards and in search results.

• Accepted formats: PNG, JPG, WebP.
• Show the release as it actually looks in-game. Do not use placeholder images, images from another creator's release, or screenshots that do not match the release content.
• Good screenshots show the unit or build from multiple angles and include an in-game environment for context.
• If no screenshots are uploaded, Hub will attempt to auto-generate a 3D preview from the unit JSON (for JSON releases only). The auto-preview is lower quality than a real screenshot.

Step 2 — Upload files

Quick Upload has separate slots for each file type. Use the right slot for each file — putting a JSON in the schematic slot or vice versa will cause the release to behave incorrectly.

• Unit JSON slot: For the .json unit file from config/mob_crafter/units/. Unlocks the in-browser 3D preview and the direct download button.
• Schematic slot: For .schem (WorldEdit) or .litematic (Litematica) files. Separate from the JSON slot — a release can have both.
• ZIP / Pack slot: For archive bundles containing multiple files or creator assets. Maximum file size: 50 MB. If your bundle exceeds this limit, host it externally and use the External URL field instead.
• External URL: If the primary download is on your own site, CurseForge, Patreon, GitHub, or another platform, paste the URL here. You can use an external URL alone or alongside uploaded files.

Step 3 — Basic info

• Title — The name of your release. Maximum 80 characters. Use the actual name of the creation, not keyword phrases. A clear title like "Iron Golem Siege Unit" is better than "Minecraft iron golem mob crafter unit download free".
• Tags — Choose tags that accurately describe the content: mob type, theme, size, style, Minecraft version, etc. Do not add tags for characters or brands that are not actually in the release.
• Description — This is the most important metadata field. A good description should include: what the unit or build is, what makes it interesting or unique, what Minecraft version it was made for, what dependency mods are required, any known limitations, and basic usage notes for users who are new to the release type.

Step 4 — Release settings

• Content type — What the primary content is: Unit JSON, Schematic + Unit Set, Schematic only, ZIP Pack, or External. Set this to match your files, not what you wish you had uploaded.
• File availability — What file types are actually included in this release (JSON, schematic, ZIP, or external). Users see this on the release page before they click download.
• Access type — How users access the download:
  • Free: Anyone can download from Hub directly.
  • Creator-supported: Free but the creator has a support link (e.g., Patreon, Ko-fi) shown on the page.
  • Supporter only: The primary file is gated behind the creator's external platform. Only supporters get access.
  • External only: No Hub-hosted file. All downloads go through the external URL.
• Creation method — How the release was made: Hand-crafted, AI-assisted, AI-generated, or Commissioned. Be honest — undisclosed AI content is a guidelines violation.
• Visibility — Draft saves the release privately; Published submits it to the moderation queue for review.

After submitting

When you set visibility to Published and submit, the release enters a moderation queue. Moderation checks that the metadata is accurate, the files work, and the content meets the community guidelines. Once approved, the release becomes publicly visible on the Hub catalog.

You can edit a release at any time from your creator dashboard without re-submitting to moderation — unless you make a change that requires a full re-review (such as replacing the primary file or making a significant metadata change).

Common mistakes to avoid

• Wrong file in the wrong slot — A JSON placed in the schematic slot will not generate a 3D preview. A schematic placed in the JSON slot will fail to parse. Use each slot for its intended file type.
• Missing dependency disclosure — If your unit uses blocks from other mods, list those mods and versions in the description. Releases that cause "missing blocks" errors due to undisclosed dependencies are one of the most common user complaints.
• Thumbnail that does not match the release — Using a placeholder, a generic image, or a screenshot from a different build as the thumbnail misleads users and is a moderation flag.
• Vague or one-line description — "A cool unit" tells users nothing. Describe what the build is, why it is interesting, and what users need to use it.
• Wrong access type — Setting a release to "Free" but placing all files behind an external paywall confuses users. If the files require external access, set the access type accordingly.
• Missing Minecraft version — Always note which Minecraft version the release was built and tested on. A unit made for 1.20.1 may not work correctly in 1.21.