Resource packs

Collaborators

A pack starts as yours alone. Collaborators are other accounts you let work on it — a builder doing your models, a friend drawing block textures, a client watching without touching anything.

Collaborators belong to one pack, not to your account. Adding somebody to your castle pack doesn't put them anywhere near your other packs, and there is nothing to set up before you start: open a pack, hit the people icon next to Edit, and the Collaborators page is the whole feature.

A pack can be shared with five people besides you. An invitation that hasn't been answered yet holds one of those places — otherwise you could invite thirty and have five win a race none of them knew about. Withdrawing an invitation, or removing somebody, frees the place immediately.

Adding somebody#

1
Open the pack's Collaborators page
The people icon in the pack header, beside Edit and Export. Only the pack's owner sees it.
2
Add them by Minecraft name or by email
Minecraft name finds an account that has verified that name by running /permlink on — see Our test server. It's the quickest route, and it's the name and skin the list shows them under afterwards.
Email works for everybody else, including people who don't have a resourcepack.ai account yet — they can create one from the invitation.
3
Choose what they can reach
Editor is the whole pack. Viewer can open it and change nothing. Custom is the two lists below.
4
Send it
They get an email, plus a Discord DM and a line of in-game chat if they've turned those on. Invitations last fourteen days and can be withdrawn from the same page at any time.

Inviting by email always says "invitation sent", whether or not that address already has an account here. That's deliberate — otherwise the box would tell anybody who typed an address whether its owner has a resourcepack.ai account. Nobody's email address is ever shown to another collaborator either; collaborators appear as a Minecraft name and a head.

What a collaborator can do#

Two independent choices.

Which parts of the pack, the same six as the tabs on the pack page: Models, Blocks, Items, GUIs, Icons and Sounds. A collaborator granted Models alone sees a pack with one tab in it; the others aren't greyed out, they aren't there.

What they can do in them:

Edit

Create, edit, rename and delete assets by hand.

Generate with AI

Run generation and AI edits. Spends credits — see below.

Sync & test in game

Push the pack to a Minecraft client and run give commands.

Export

Download the pack as a .zip, or export single models.

The two are independent on purpose. "Can add AI models but can't delete my work" is a real arrangement, and so is the reverse.

What stays yours#

Nothing a collaborator is given touches the pack itself. Renaming it, deleting it, duplicating it, changing its banner, moving assets to another pack, choosing whose credits it spends, and managing collaborators are all the owner's, and there's no way to grant them.

Whose credits get spent#

A pack has one setting for this, in Edit pack:

Use my credits

The default. Anything a collaborator generates comes out of your balance — you're funding their work.

Everyone uses their own

Collaborators spend their own AI Credits and run out on their own. Yours stay untouched.

Either way, your own generations are charged to you, and your billing history records who ran anything a collaborator spent your credits on.

Collaborators need their own access to resourcepack.ai while it's in early access. Being invited gets you into somebody's pack; it isn't a way into the product.

Testing as a collaborator#

Sync works exactly as it does for the owner, and it sends the pack to the person who pressed it: link your own Minecraft account with /permlink once, and Sync lands on you, not on whoever owns the pack. See Our test server.

Removing somebody ends their access to the pack, and their Sync with it.

Hearing about what they do#

The Notifications button on the Collaborators page decides what you're told about, and where. It reuses the three channels from generation notifications — email, a Discord DM, a line of chat in game — and you can set it per pack or override it for one person.

Things worth hearing about: somebody adding, editing or deleting an asset, running AI generation, syncing, linking a server, exporting the pack, or accepting an invitation. Deletes, AI generation and people joining are on by default; the rest aren't, because a ping for every sync is a feature you'd switch off within a day.

You hear about something as it starts, and then it goes quiet for ten minutes — anything that happens in between is counted and mentioned in the next message. Somebody saving a model forty times is one notification, not forty. Collaborators are never told about each other, and never about themselves.

Removing somebody#

The gear beside their name, then Remove from pack. They lose access immediately, their pairing code for the pack stops working, and anything they already made stays in the pack — it was always your pack.

To change what somebody can reach rather than remove them, the same gear opens the same two lists you picked from when you invited them.