How a pack works

Editing in a browser

/rp edit opens a model, texture or vehicle from your server's content folder in ResourcePack AI's web editors, and writes your changes back to the file on your server when you are done. Use it to tweak a model or repaint a texture without downloading the file, opening Blockbench and uploading it again.

/rp edit mypack:chair

You get a link in chat. Click it and that thing opens in the right editor. Move the cubes, paint the texture, press Send to server, and assets/models/chair.bbmodel on your server changes and the content reloads.

No account, no sign-in, nothing to install. The link works once and lasts three hours.

What it opens#

You give it only the ID. The plugin works out which editor to use:

What the ID is	Where it opens
An item with a `model:`	The model editor: geometry, paint, display, animation
An item with no `model:`	The pixel editor, on its sprite
A vehicle	The vehicle editor: seats, handling, effects

Other kinds of content (sounds, screens, recipes) have no editor yet, and the command tells you so. The ID tab-completes, and only things that can be opened are offered.

/rp edit           the links you have open, and how long they have left
/rp edit close     end them

Nothing changes until you press Send to server#

The editor saves your work as you go, but none of that reaches your server. Your files change once, when you press Send to server. If you try something and change your mind, close the tab and nothing has happened.

What crosses, and what does not#

Only the thing you named: one model and its textures, one texture, or one vehicle's settings. Not the rest of your pack, and not your config.

The link is the key. Anybody who has it can edit that one thing until it expires, so do not paste it anywhere public. /rp edit close ends it early.

Models#

A model comes back as the same kind of file it went out as.

A .bbmodel (the Blockbench project, which Models recommends) comes back as a .bbmodel, with its geometry, bones, animations and art still in one file. Anything Blockbench keeps that the plugin does not read, like display settings and texture names, is left as it was.

An exported .json comes back as a .json, with its PNGs written beside it where they already were. A texture you add in the editor goes into your item's texture folder.

A model written inline in the item's YAML, or one named by a resource location (minecraft:item/...), is not a file in your pack's assets/models/, so it cannot be opened.

Your original is never half-replaced

The plugin checks the file it is about to write loads as a model before saving anything, and refuses in chat if it would not. Each write goes to a temporary file first and is then moved into place, so a crash or a full disk cannot leave half a model behind.

Vehicles#

In the vehicle editor you drag a figure onto a seat, and that is where somebody sits.

Only that vehicle's entry in your vehicles/*.yml is rewritten. Other vehicles in the file, blank lines and comments between them are left alone. Comments inside the edited vehicle are lost.

The vehicle's model is shown so the seats have bodywork to sit in, but it is read-only there. Open the item it wears to change its shape.

Textures#

The pixel editor opens square PNGs up to 256×256. An animated strip (a tall image with a .mcmeta file beside it) is refused rather than squashed.

Turning it off#

# config.yml
edit:
  enabled: true

Set enabled: false and /rp edit says it is switched off instead of doing anything.

rpengine.edit is the permission, and it is a serious one: whoever holds it can rewrite files in your content folder from a browser. It defaults to op. See Permissions.

This is not the same as Sync#

/rp sync sends a pack from a Studio account to a player on your server, so you can try it before it ships. It needs an account and a pairing code.

/rp edit goes the other way and needs neither: your content folder is the source, and your changes land back in it.

Content from a Studio pack, synced or distributed, has a studio: id. Studio is its source, and the pack's folder in content/ is replaced each time you publish, so /rp edit studio:<id> doesn't open an editor here. It links to the pack in Studio instead: change it there and publish again.