Build jobs on MCME are run with TheGaffer, the plugin that protects the map. By default, players cannot change the map at all. A job opens one square area for building, for the people on the job, for as long as it runs. This page is for the staff who start and run jobs (job leaders) and who manage projects: the commands you type, what you will see, and the permission each command needs. For the builder's side, see Building on jobs. The plugin's code is on GitHub at MCME/TheGaffer, and developers can read TheGaffer for developers.

Permissions

thegaffer.create is not limited to your own jobs. Anyone with it can stop, pause or manage any job on that server, so check the job's name before you act.

TheGaffer decides where building is allowed for every plugin that asks it, including Architect's building tools. See Architect building tools.

Starting a job

1. Stand where the centre of the job should be. The centre (the job's warp) is where you stand when you press Create job.
2. Type /createjob. /job create and /job start do the same. You cannot start a job while you are on one: you see You are already in the job <job> - leave or stop it before creating a new one.
3. A form called Create a build job opens. Fill it in:

Some fields only appear when the feature is on: the description and Discord fields depend on server settings, the project list only shows when an active project exists, and the glow switch only shows when glow is enabled.

4. Press Create job. Press Cancel or Escape to stop; you then see Job creation cancelled. No job was created.

You see Created the <job> job! If the name was taken, the job gets a number instead: Name Gate was taken — created Gate-2 instead. A name counts as taken if a job with that name is running or has ever run on that server. Job names are case-sensitive, so builders must type them exactly. An empty name gives A job name is required — nothing was created.

When the job starts:

• Players on your server get the start announcement with a Click to join button. Players on every other server get an announcement whose button moves them to your server and joins them.
• If you left Announce on Discord on, the job is posted on Discord with you as leader, the world, the start time and the /job join command.
• You see the job's edge as a wall of white particles.
• The job is saved, so it carries on after a server restart.

After the start you can still move the job's centre, change its radius, attach it to a project and hand it to another leader. You cannot change its name, description, private setting, Discord setting or glow. To change those, stop the job and start a new one.

Roles

Most other staff commands on this page come from the thegaffer.create permission, not from the role. A helper without that permission can only use /job teleport and /job teleportall.

Build rights come from the worker list. A worker promoted to helper keeps building. The owner, and a helper added with addhelper, are not workers: they can build in the area only if they have thegaffer.ignoreprotection.

When the owner logs off

If the owner leaves the job's server, the job waits a few minutes. Then:

• If a helper is online (and not banned from the job), one of them becomes the owner at random. The old owner stays on the job as a helper.
• If no helper is online, the job pauses itself. Everyone on it sees The job has been paused because no owner or helper is online. It will resume automatically when one returns. When the owner or a helper logs back in, it resumes with <name> is back — the job has resumed.

A job you paused yourself never resumes on its own.

Running a job

The Kick, Ban, Promote and Demote buttons in /job manage act the moment you click. There is no confirm step.

/job prep keeps your stored inventory in the server's memory only. Get it back before you log off; a server restart always loses it.

Managing people and the area

All the actions below need thegaffer.create, and work on any running job on the server. There are two ways to run them.

Guided: type /jobadmin (or /job admin) on its own. The plugin asks in chat:

1. What job would you like to modify? and lists the running jobs. Type the job's name.
2. What action would you like to perform? and lists the actions. Type one.
3. A follow-up question, such as the player's name.

Type !cancel at any point to stop. The questions also stop after a minute without an answer. While the questions run, what you type goes to them, not to chat.

One line: type the job, the action and its argument in one go:

/job admin <job> <action> [player]
/jobadmin <job> <action> [player]

For example, /job admin Gate-2 inviteworker Alice. Most actions answer Success: … in green or Failure: … in red; setwarp, teleportall and clearworkerinven answer Job Edited!.

inviteworker, uninviteworker, kickworker, banworker and unbanworker accept several names separated by commas, without spaces: Alice,Bob.

clearworkerinven wipes every online worker's inventory at once and cannot be undone.

Private jobs and invites

Only invited players can join a private job. Others see <job> is private, and you are not invited. Invite players with inviteworker before or after they ask. An invited player gets <leader> has invited you to <job>. Accept; clicking Accept joins them.

Kicks and bans

• A kick takes away every role the player holds, so a helper stops being a helper too. They can join again if the job is open to them. Use a ban to keep someone out.
• A ban takes away every role and stops the player joining that job. Bans are stored against the player's account, not their name, so a name change does not lift them. A banned player cannot be made a helper until you unban them.
• The owner can be neither kicked nor banned. Hand the job over with /job transfer first.

Moving or resizing the area

setwarp and setradius change the area for everyone at once. Builders' particle walls follow straight away. Blocks already counted stay with the job.

Glow

If you switch on Glow outline for builders when you start the job, workers and helpers get a coloured outline in two different colours (by default purple for workers and aqua for helpers and the owner). It helps you see who is on your job. Glow is chosen at the start and cannot be changed later. It ends with the job.

Discord announcements

With Announce on Discord on, TheGaffer posts:

• at the start: New job: <job>, with the leader, the world, the start time, the description and the /job join command. Operators choose which Discord role, if any, the post pings.
• at the end: Job ended: <job>, with how long it ran, blocks placed and broken, and the number of builders.

Projects

A project groups the jobs of one build, such as every job on Minas Tirith, and adds up their statistics. /pj is short for /project.

Who can do what:

• Anyone can use /project list and /project info.
• Creating a project needs thegaffer.project.create (or thegaffer.project.admin). The creator becomes the project's lead.
• The lead and the project's managers can edit it. The lead alone can change the lead or delete the project.
• thegaffer.project.admin can do everything on every project.

Good to know:

• Project names may contain letters, digits, spaces, underscores, hyphens and apostrophes. They are not case-sensitive, and nothing is not allowed. Names with spaces work in every command: /project attach Minas Tirith Gate-2.
• Only active projects appear in the job creation form. Attach a job afterwards with /project attach.
• When the last running job of an active project ends, the lead (if online) gets All jobs for project <name> have finished. with a Complete button.
• Tab completion of job names in /project attach only works for project names without spaces. Typing the full command still works.

Exports

The files are written on the server, and the chat message gives the file name. Ask a server operator for a copy.