resourcepack.ai
DOCS

Get started

Quickstart

One full loop: make a pack, generate something into it, look at it in Minecraft.

You'll need

A ResourcePack AI account, and Minecraft: Java or Bedrock. Nothing to install for either.

Make something#

  1. 1

    Create a pack

    Open studio.resourcepack.ai and create a pack. A pack is the container for everything else you make (models, blocks, items, GUIs, icons and sounds), and it's the unit you export and test. The Studio starts you with a name and banner; use the dice to randomize both, or upload your own image.

  2. 2

    Press Add asset

    Two choices, in this order. First how you want to start:

    OptionWhat it is
    GenerateDescribe it and the AI makes it
    DrawA blank grid, or a stone cube, and you do the work
    UploadArt you already have

    Then what you're making: Block, Model, Item, GUI, Icon or Sound. A few combinations don't exist (you can't draw a sound), and the fields underneath change with the type. See Generating with AI for the detail.

  3. 3

    Describe what you want

    Pick Generate, then say what you want in a sentence. Be specific about material and wear, not about pixels:

    weathered copper roof tiles, blue-green patina, strong diagonal grain

    A block, item, icon or sound comes back in seconds. A model takes minutes instead: the builder plans it and constructs it cube by cube, painting its materials as it goes, and you can leave the tab while it works.

    See Generating with AI for what makes a prompt land.

  4. 4

    Edit it

    Nothing generated is final, and that's the point: generation is a faster starting position than an empty grid, not a finished product.

    Blocks, items and icons open in the pixel editor; models open in the model editor, which has separate modes for shaping geometry, painting it, positioning it in hand, and animating it.

See it in Minecraft#

The fastest route is our test server: no plugin, no setup.

  1. 1

    Join play.resourcepack.ai

    Java or Bedrock, same address. Take the portal for a private sandbox of your own, which is kept between visits, or use the shared sandbox up front for a quick look.

  2. 2

    Link your account, once ever

    On your account page, under Minecraft account, press Get link code, then run it in game:

    /permlink 48213097

    That's the last code you'll type. From here on, the Studio knows who you are on the server.

  3. 3

    Push

    Hit Sync on the pack and it goes straight to your client. Nothing is downloaded, zipped or uploaded by you. On Java the pack swaps in where you're standing; on Bedrock you're bounced out and back in for a few seconds, because Bedrock only takes a pack while joining.

  4. 4

    Iterate

    Change something in the Studio, push again, look again. Most of the work is in how many times you go round this loop, not in getting it right first time.

Export it (optional)#

You never have to do this to test; the loop above never touches a file. But a finished pack is an ordinary Minecraft Resource Pack, and you can take it with you: export Java .zip or Bedrock .mcpack. The .zip goes in your resourcepacks folder:

# Windows
%APPDATA%\.minecraft\resourcepacks
 
# macOS
~/Library/Application Support/minecraft/resourcepacks
 
# Linux
~/.minecraft/resourcepacks

There's no runtime dependency on us in the exported file. It keeps working if you never open the Studio again. The exception is animated models, which need our plugin to play back; see Animations.