This page covers Architect's commands for staff and managers: item block limits, the no-physics list, resource pack
regions and releases, the build inventory files, the custom head collection, live biome tuning, the web-map layers and
the /architect admin command. For each command it names the permission node it needs. The tools every builder uses
are on Architect building tools. Architect's code and its full technical manual are on
GitHub.

Permissions on MCME are given on the servers, not by Architect itself. Architect suggests four permission groups
(below), but staff may grant nodes one by one. If a command answers that you have no permission, ask whoever manages
permissions.

Permissions

The four groups

Each group includes everything of the group above it in this table. Out of the box, Architect gives the groups and
almost all of its nodes to server operators only; the permissions plugin on the servers gives them to ranks.

architect.* grants the Head Designer group and nothing more.

Nodes in no group

These are never part of a group. Grant them by name.

The Designer group allows /copy, but gives no copy limit. Without an architect.copypaste.limit.<n> node, /copy
answers that the player may copy 0 blocks only. Give every rank that copies a limit node too.

Item block limits (/itemblock)

Item blocks are furniture-like models: a base block plus an invisible armor stand that wears the model. Each chunk
takes only so many. Armor stands, item frames and paintings all count towards the limit, but only item blocks are
refused. The limit is the highest of the limit regions that contain the spot; outside every region it is the world's
base limit (5 unless changed).

<radius> reaches that many blocks sideways, and [height] that many up and down (the radius if you leave it out).
architect.itemBlock.region.ignore lets a player place item blocks in a full chunk.

• A new region has limit 0, so nobody can place item blocks in it until you set a limit.
• /itemblock remove also deletes other named armor stands in range. Look first with /itemblock glow.
• Type /itemblock help, not /itemblock alone, which fails with an internal error.
• The web map can show the regions and how full each chunk is; see Map layers.

The no-physics list (/nophy)

Architect stops block updates ("physics") for chosen blocks, world by world, so that decorations stay as built. Each
world has a list, or uses the default list. Depending on a world setting, the list is a NO physics list (listed blocks
get no updates) or an ALLOW physics list (only listed blocks get updates). The replies say which.

architect.noPhysicsList.edit includes .view. <world> must be a loaded world.

• The first /nophy add <world> ... in a world that uses the default list gives that world a list of its own, holding
  only the new entry. The default entries then stop applying there, so add every entry the world needs.
• Delete exception areas with the command. An area removed from Architect's file by hand comes back.
• Redstone power is frozen on the whole server, on purpose, inside exception areas too.

Keep a copy of the default list before you edit it with -default. In this version, after an /architect reload, an
add or remove on -default that brings the list back to what it was before the reload deletes the whole default
list.

Resource pack regions

A resource pack region is a named area of one world with a pack and a weight. A player with automatic switching on who
walks into it gets its pack. Where regions overlap, the highest weight wins. These commands need
architect.resourcePackAdmin, which includes the player /rp commands, and WorldEdit on the server.

1. Make a WorldEdit selection: a cuboid, polygon, cylinder or ellipsoid. A polygon covers the world from Y 0 up; a
   cuboid only the heights you selected.
2. Run /rp create <name>. Architect saves the region and opens the region editor in chat.
3. Type rp <pack> to set the pack, and weight <n> to set the weight.
4. Type quit.

In the editor, type these words in chat without a /. They do not reach public chat. The editor closes after 2 minutes
without input.

• A new region has weight 0 and no pack, so it does nothing until you set rp. Give overlapping regions different
  weights: with equal weights, which region wins is not defined.
• Region names are case-sensitive, and create, edit and remove must be typed in lower case.
• Every change is saved at once and redrawn on the web map.

Releasing a resource pack

A pack's files are built by a release script on the server, which publishes them as a GitHub release.
/rp release runs that script and reports in chat. Players get nothing until /rp server points the pack at the new
release. All these commands need architect.resourcePackAdmin, and also work from the console.

1. Run /rp release <pack> <tag> <title>, for example /rp release Human v4.1.3 Better leaves.
2. Chat shows the start, such as Releasing Human v4.1.3 ("Better leaves"). Last time this took about 5 minutes. The result comes here.
3. Chat reports each step, such as Human: Sodium zips done, then Human: publishing on GitHub....
4. The closing message gives the result (table below). After a published release, a line such as
   Put it live: [26.2] [26.3] [Open on GitHub] follows. Each version button fills in the /rp server command.
5. Send /rp server <pack> <tag> <version> for each Minecraft version the release is for.

If you leave before the end, you see the closing message when you next join that server, under
While you were away:. A restart loses it.

• Nothing is pushed to players who are online. A player gets the new files the next time Architect sends them the pack,
  such as when they enter another region or join the network. /rp <pack> -force gets them at once.
• Until a player has the new files, Architect no longer recognises their old ones: the F key and /inv may not find
  their pack. /rp <pack> -force fixes it.
• Other servers that share Architect's settings see the change after /architect reload there.

Clearing every player's pack settings

/rp dropdb (permission architect.resourcePackAdmin, or the console) only says what it would do.

/rp dropdb confirm deletes the stored pack settings of every player, for every server that shares them. There is no
undo.

The build inventory

The in-game editor

Players with architect.inventory.edit can add, change and delete blocks of the build inventory in game.

1. Open the build inventory of your current pack. New blocks always go into the pack you are using.
2. Open the tab the block belongs to, or a block's variants to add a variant.
3. Shift+right-click in the item area: on an empty slot to add a block, on a block to edit or delete it. The window
   closes, and the editor asks its questions in chat, marked [Inventory Editor].
4. Answer in chat. Where a list in [...] is shown, type one of its words exactly. Type !skip to keep a value, and
   !cancel to stop. After 300 seconds without an answer the editor stops by itself, and nothing is saved.

When you add a block, the editor asks for a unique id, the placement type, the block states (type one, or hold a
prismarine shard and left-click a block to copy its state), the item, its custom model data and its display name. It
then saves and reloads the inventories: Inventory reload done!

Back up the pack's files, or keep them in git, before you edit in game. Two answers write values that cannot be read
back, and the whole tab then disappears from the build inventory although the editor reports success. When asked
To change the inventory item hold in main hand a new item and type 'ok', answer !skip. When asked whether an
item should be listed directly in the category of its collection, answer no.

• An edit writes the entry anew. Settings the editor does not ask about, such as the next block for sneak+Q and the
  variant layout, are lost. Edit doors, item blocks, signs and most branch blocks in the files instead.
• The editor only works on tabs whose blocks are in a file named after the tab, and never creates files or tabs.

Reloading and syncing

• Upload and download show nothing at the start. Up to 5 minutes later you see
  Custom inventory for RP <pack> pushed to GitHub! or ... updated!, or an error. A failure inside the script can
  still be reported as success, so check Architect's log.
• The description may hold letters, digits, spaces and simple punctuation; no word may start with -.
• Setting up the scripts on a server is an operator task.

Saved inventories of other players

Saved inventories are made by players with architect.inventory.save (see
Architect building tools). architect.inventory.other lets you delete
anyone's with /inv delete [rp:<pack>] <name>. Run /inv reload after a create or delete, so every player sees the
change.

Custom heads: review and the gallery

Players submit heads with /chead submit. Managers review them, sort them into categories and keep the head gallery.
These commands need architect.customHeadManager.manager together with architect.customHeadManager.user.

1. Run /chead reviewList and click a head, or run /chead review <name> to get the submitted head and look at it.
2. Accept it into a category with /chead accept <name> <category/newName>, or throw it away with
   /chead reject <name>.

After a server restart there is no gallery until someone runs /chead reload (or /architect reload). Until then
/chead warp finds no gallery, and accepted heads do not show on the wall. Run /chead reload before
/chead setCollection, or the old wall stays where it was. Building the gallery replaces whatever stands there:
choose an empty spot.

The head inventory (/inv h) shows new categories only after /inv reload or /architect reload.

Other players' files, kits and settings

Automatic block resends

Because Architect cancels many block updates, a client sometimes shows a block differently from the server. Where
automatic resends are on, Architect sends a player the real blocks again just after they place, break or click one.

/chunkupdate auto <world> true turns it on in a world, and /chunkupdate auto <world> (without true) turns it off.
-default in place of a world changes the default. It takes effect at once. It needs architect.chunkupdate and
architect.chunkupdate.auto. /chunkupdate [radius] does nothing in this version.

Biome tuning

Biome tuning changes a custom biome's colours and atmosphere while the server runs, without a restart: sky, fog, water,
grass and leaves, light, climate, music, ambient sounds and particles. You work in an editor window or with chat
commands. An edit is live on the server at once. Players see it after their view is refreshed, and a save writes it
into the datapack so it survives a restart.

You can tune biomes from a datapack in folder form in the main world. Vanilla minecraft: biomes cannot be tuned, but
you can copy their look.

Permissions: none of these nodes is in a group. Grant them by name.

The editor

Open the editor with /biometune for the biome at your feet, /biometune <namespace:id> for another biome, or an
[Editor] button in chat. The home window, Biome editor: <id>, shows the biome's label, ● unsaved or ✓ saved,
colour swatches, a button for each section, and Preview in world, Publish…, Save, Undo, Revert… and
New biome….

In a section, click a colour to open the colour picker. Sliders, switches and choices take effect when you click
Apply, or Apply + preview in world. Only the inputs you changed are written. Choosing (not set) removes a value.

The colour picker has hue, saturation and brightness sliders (and opacity for clouds), and a hex box. Show only
previews in the window; Apply makes it live. Copy from biome… takes a colour from another biome, vanilla ones
included. Clear removes the value.

• If someone else changed a value while your window was open, Apply writes nothing and says what changed. Check, then
  apply again.
• Climate changes the world at once: where it is cold enough, rain falls as snow and ice can form.
• A window closes after 30 minutes.

Live, seen and saved

A refresh makes a client load the biomes again. The player sees a short loading screen and is back after 1 to 3
seconds. Preview refreshes your own view (at most once every 5 seconds). Publish refreshes everyone in your
world, or on the server, a few players a second; each first sees
Biome colours were updated by <name> - refreshing your view.... The next publish can start 30 seconds later.

A restart loses every unsaved edit, so save first. Edits change only the server you are on; other servers keep their
own biomes. If a refresh does not finish, the player is disconnected with Biome refresh did not finish - please rejoin. If a refresh is refused, rejoin to see the live values.

Save keeps the old file as a backup first. It refuses if the file was changed on disk since Architect loaded it;
then run /biometune revert <biome> to load that version (this drops your unsaved edits). Undo steps back one
change (20 steps per biome). Revert goes back to the saved file.

Commands

<biome> is an id such as mcme:custom_001, or here for the biome at your feet. From the console, name the biome.

How to write a value for set: a colour as #rrggbb (clouds #aarrggbb, opacity first), a number as 0.85, on or off
as true/false, a choice from the list (tab completion offers them), and music, sounds and particles as JSON. The
game checks every change; if it refuses, nothing changes and the reply says why.

• /biometune <biome> without edit only works with a full id: /biometune plains answers Invalid subcommand.
• The [Publish] and [Save] buttons show in chat even without those permissions.

New biomes

The game only learns new biomes at a restart, so the server keeps spare biomes: ready-made, neutral biomes with ids
such as mcme:custom_001. A builder claims one, labels it and tunes it, all without a restart.

1. Run /biometune spares to see how many are free.
2. Claim one with /biometune claim <label> [from <biome>], or with New biome… in the editor. With from, the spare
   starts with that biome's look; without it, it looks like plains.
3. Tune it and save it.
4. Paint it into the world with WorldEdit: //setbiome <spare id>.

A claim is for good: there is no command to undo it. Only paint with a spare you have claimed, because a free spare
later gets someone else's look.

Map layers

Architect draws five layers of its own on the web map, so staff can see where its invisible rules apply. Every layer
starts hidden: open the layer list on the map and switch one on. See Using the map for
the map itself. The three newer layers sit in the map's Debug group.

The map draws areas flat; the window gives their heights. Changes reach the map within about 10 seconds.

Commands

Permission: architect.maplayers, or the server console.

On MCME no staff rank holds architect.maplayers at the moment, so an operator runs these commands from the server
console.

The Custom biomes layer draws only worlds that are on it. The first read of a world's files is paced so it does not
hog the disk, survives a restart, and fills the map as it goes. After that, the layer keeps up by itself: paint made
with WorldEdit or FastAsyncWorldEdit over a few dozen chunks shows within about 10 seconds, other paint within a few
minutes. Run scan <world> again if paint reached the world without the server seeing it.

• A world whose biome markers would add more than 512 KB to every map visit is not drawn. scan then says
  not drawn, with the size. It is drawn again by itself once it fits.
• A biome with unsaved tuning shows Changed in game, not saved yet in its window.

Other permissions to grant

Game-mode switcher. Builders who are not op can use the game's own F3+F4 switcher (and F3+N for spectator), in
worlds where it is switched on. Each mode needs its own node: architect.gamemodeSwitcher.creative, .survival,
.adventure, .spectator, or architect.gamemodeSwitcher for all four. These nodes are off by default, even for ops.
A refused switch says You can't switch to <mode> mode here.

Never grant the spectator node alone: without another mode, a player cannot switch out of spectator mode. The
switcher also shows the creative inventory's Operator Items tab; its barrier, light and structure void blocks still
need architect.invisibleBlocks, and its command blocks stay op-only.

Invisible blocks (architect.invisibleBlocks): placing barrier, light and structure void blocks from the creative
inventory. Light blocks from the build inventory need no permission.

Lecterns (architect.lecternEditor): taking the book itself (not a copy) and putting books on lecterns, without
build permission.

Chest protection (architect.inventory.ignoreProtection): where chest protection is on, players without build
permission may look into containers but not take or put items. This node lifts that.

The /architect command

/architect placeAllBlockStates (permission architect.reload) places every state of every block in a large grid
next to you, with no undo. It is a developer tool: never use it in a build world.

Reloading. /architect reload reads Architect's settings, world settings, inventories, kits, regions, heads and map
layers again. Resource pack and item block regions come back after about 10 seconds. A few settings, such as biome
tuning's settings, need a server restart. Reload Architect with /architect reload or a restart, never with /reload
or a plugin manager: that leaves live biome edits in the game while Architect forgets them. Other reload commands:
/inv reload (inventories only), /chead reload (heads and the gallery) and /biometune revert <biome> (one biome).