How to Publish Your Add-on on GodCraft and Get More Downloads

You've built something, tested it, and it works. Publishing it on GodCraft takes a few minutes. Getting people to download it is a different skill, and it's mostly about how the post looks before anyone opens it. Every upload is reviewed by our team, so this guide is also a list of what we see working, and what we see ignored.

Before you publish

• Install it yourself one last time and play with it in a fresh world. Broken uploads collect bad comments fast.
• Make sure every object has a real name. "Item 1" in someone's inventory looks unfinished.
• Set a pack Icon in the add-on details. It appears in Minecraft's pack list.
• Take a few screenshots in game while you test. You'll need them in a minute.

Publishing step by step

1. Sign in. Publishing needs an account, not guest mode.
2. Open the Workbench tab and tap Publish on your add-on. The app builds the .mcaddon file and opens the publish screen with the file already attached.
3. If you've published before, you can choose Publish as a New post or an Update of your post. Use the update option for new versions of the same add-on (more on that below).
4. Fill in the Name, pick 1 to 3 Categories, and choose the Minecraft versions it works on.
5. If the add-on is based on someone else's work, fill in Original author.
6. Write the Summary and Description, then add a few Keywords, separated by commas.
7. Set the Thumbnail and add Screenshots.
8. Choose Free or Paid. Paid add-ons cost gems, up to 999, and you keep every gem.
9. Agree to the Privacy Policy and Terms of Use and tap Publish.

If something is missing, the screen lists exactly what to fix before the button works. Links, emails and contact details aren't allowed in the text fields, so leave those out.

The thumbnail decides most clicks

People scroll past dozens of posts. The thumbnail is the only thing they really look at. You have two options:

• Generate builds a thumbnail from the objects in your add-on and your title. It's clean, readable, and always relevant, which makes it a solid default.
• Import lets you use your own image. A good in-game screenshot of your best mob or build often beats everything else.

What doesn't work: random pictures, memes, or images that have nothing to do with the add-on. They get removed in review. Text crammed into the thumbnail is also a mistake, because it's unreadable at card size.

Titles that get found

Use the name a player would search for. "Ruby Tools and Armor" will be found. "My First Addon v2 FINAL" won't, and it tells people nothing. Put the main thing first, and skip all-caps and clickbait. A name has to be at least 4 characters, but it should really be a short description of what's inside.

A description people actually read

The description supports markdown, so you can use short headings and lists. A structure that works for almost any add-on:

1. One or two sentences on what the add-on adds and why it's fun.
2. A list of the contents: each item, block or mob with a line about what it does.
3. How to get things: recipes, where mobs spawn, or the /give commands.
4. Requirements: the Minecraft version, and any experiment that must be on (if there is one).

The Summary is the short line shown on cards, so make it a clear one-sentence pitch rather than repeating the title.

Screenshots

Show the content in game: the mob in its biome, the tools in a crafting table, the block used in a small build. One screenshot per main feature is plenty. Hide the HUD if you can (F1 on Windows), and avoid dark night shots where nothing is visible.

Keep it updated

Updates are one of the best ways to get noticed again. When you publish a new version as an Update of your post, it's added to the existing post and the post moves to the top of the Updated list. You can also manage versions on the post itself under Versions > Add version.

Give each version a clear number (1.0, 1.1, 2.0) and an optional name, and tick the Minecraft versions it supports. Keeping everything on one post means your downloads, likes and comments stay together, instead of being split across copies.

After publishing

• Answer comments, especially bug reports. A short "fixed in 1.1" reply builds trust.
• Read what people ask for. The best update ideas usually come from the comments.
• Polished, complete add-ons can be verified, and verified content earns you gems.

Our honest summary after looking at a lot of uploads: a clear title, a relevant thumbnail and an honest list of contents beat any amount of hype. Make it easy for someone to understand your add-on in three seconds, and the downloads follow.