Builds and blueprints

A build on Aurelune is a blueprint put down in the world that raises itself, block by block, out of whatever players drop in its chest. Every build has its own page where you can watch it go up: see them all at /builds.

Pick a blueprint, face where you want it, put it down, and feed it.

Blueprints

A blueprint is a build saved block for block. The blueprint library has the ones anyone can use. Some are free. Some cost Coins: buy one once and you can build it as often as you like, and the Coins go to the player who made it.

Make your own. Build it by hand, then:

1. Run /build select to get the Build Selector.
2. Left-click one corner of your build and right-click the opposite corner.
3. Run /build scan and give it a name. Empty air around it is trimmed off.

A scan starts private. On its page you can make it public and give it a price. A schematic you upload on the website (.schem, .litematic or .nbt) stays private: you can build it, but only scans made in game go in the library. Uploads are up to 4 MB.

Only your own. A scan has to be somewhere you can build — your claim, your guild's, or unclaimed ground. Nobody can scan a neighbour's house and sell it.

Bought stays bought. A blueprint you paid for stays yours to build even if its owner later makes it private or changes the price. Staff taking one down is the one thing that stops everybody.

Already built something? Select it the same way and run /build add. It goes on the builds list as a finished build with its own page, and its blueprint is saved too.

How many at once

Everyone can have two builds going at once, and each step up the rank track adds one: Knight 3, Lord 4, Paladin 5, Duke 6, King 7. Creator and staff ranks get the same as King.

Only builds that are still going up count. Finished ones never do, however many you have.

A build holds its ground only while it is being built. Nothing can be placed overlapping one that is going up; once it is finished, the ground is free again, so claim it if you want to keep it.

Putting one down

1. Face the spot you want it.
2. Pick the blueprint: /build → Blueprints, the Place it in the world button on its page, or /build place <id>.
3. It shows up just ahead of you, with its front turned toward you. The front is the side its door is on. Only you can see it.
4. Move it until it sits right. The buttons in chat nudge it left, right, forward, back, up and down, turn it, or bring it back in front of you. You can also open the 3D page from the link in chat and drag it around. It moves in game as you move it there.
5. Click Put it here.

The fit score. While you move it, the chat and the 3D page score the spot out of 100: how uneven the ground is, how much has to be dug out or packed underneath, and whether it sits over water. A build needs 60 or better, so it is never carved deep into a hillside. The whole footprint also has to be ground you may build on, not somebody else's claim, and it cannot overlap another build.

Clearing is a choice. Before you put it down, pick whether the site digs its own ground out or leaves it as it stands. Clearing costs 5 coins per 100 blocks it has to remove (the preview says how many, and the button says the price); ranks get a monthly allowance of free blocks that comes off the top. Left as it stands, its walls still go through whatever is in their way, and the rest is yours to dig whenever you like, or never, so a house can sit into a hillside. Cancel it before it has dug anything, or switch it to by hand, and the coins come back.

Wrong spot? Until anything of it has been built, you can still move it: run /build move, use Move it in the menu or on its page, or just put the same blueprint down over it again.

How it goes up

A build works through four stages:

Its chest. Start a build that has no chest and it puts a double chest down in front of it. To add more, look at a chest and run /build chest. Run it again on a bound chest to unbind it.

What goes in stays in. Anyone who may feed a build can put materials in its chests; only its owner and managers can take anything back out, and nothing can be piped out by hopper. Its chests cannot be broken or blown up by anyone else either. A chest anybody could empty is a chest nobody would fill.

Clearing keeps everything it digs. Whatever it digs out goes into its chests, just as it would drop if you mined it yourself with the right tool: stone comes back as cobblestone, coal ore as coal, iron ore as raw iron, grass as dirt, logs as logs, and leaves as saplings and sticks. The dirt and cobblestone are ready for the foundation, and its owner can take the rest out whenever they like. When its chests are full, it stops and says so. Take some out, or bind another chest, and it carries on. If something still will not squeeze in, it lands on top of its chest instead of vanishing, so grab it before it despawns.

Flowers are never in the way. Grass, flowers, saplings and other small plants standing where a block goes are picked, along with any part of them that would be left floating, and go in its chests before the block goes down, whether or not it clears the ground. Farm crops like wheat, carrots and potatoes are somebody's, so it leaves those alone. Sugar cane, bamboo, cactus and berry bushes count as plants, though, so keep a farm of those out of a build's plot.

Layer by layer. A build asks for one layer at a time. The sign over it, the sign over its chest, and its page all say what the current layer is waiting for and what the whole rest of the build still needs, so one trip can bring a lot. A chest only takes as much of an item as the build still needs, and the rest stays with you.

It builds while someone is near. A build needs its ground loaded, so it only works while somebody is close by, unless someone has paid to keep it going (below).

Building by hand. Switch it to by hand and place the blocks yourself. It counts every block that matches, and /build ghost shows where the next ones go. Tall grass, large ferns and tall seagrass cannot be placed, only grown: put short grass, a fern or seagrass on the spot and use bone meal on it, and it counts.

Helping someone else's build

• While a build is open to help, anyone can put materials in its chests. Everyone who gave shows up under Built by on its page.
• The owner can close it to help, then add players who may still fill it with /build helper add <name>.
• Managers, added by the owner, can start, pause, switch modes and bind chests. Only the owner can cancel.
• Managers and helpers can be added by name from the build's page as well as in game.
• Click either sign, the one over the build or the one over its chest, to open its menu.

Letting people visit

A build worth looking at is worth standing in front of. The owner can press Let people visit on its page, and after that anyone online can open the build's page and press Take me there.

• It works for finished builds too: the button stays on the page for as long as the owner keeps it

open to visitors.

• You land just outside it, on safe ground, facing the build.
• It takes three seconds, and you have to stand still. Moving, taking a hit or landing one calls

it off, and you cannot start one at all within fifteen seconds of a fight.

• PvP is on in the survival worlds, so for your first ten seconds there, other players' hits and

falls can't hurt you. Hit someone yourself and that protection ends.

• One trip every thirty seconds, and trips leave from spawn or the survival worlds.
• Visiting has nothing to do with helping: a build closed to help can still be open to visitors, and

one anyone may feed is not open to visitors until its owner says so.

Keeping it to yourself

The owner decides who sees a build and how much its page gives away. The switches are under Who can see it on the build's page and in the Builds panel in Away.

• Private. Only you, your managers and your helpers can open its page. It comes off the builds

list, the homepage, profiles and contests, and it is left out of Discord and the Chronicle. If it already had a post in the Discord builds forum, the post comes down.

• Hide where it is. The page drops the Open the map link, and Discord never gives its

coordinates. If it stands in a claim, Discord can still name the claim.

• Hide the map. The page shows no live map of it. The map shows the land around the build, so

somebody who knows the area could still find it from that. If you hide the location, the page offers to hide the map too.

The Build Selector only works in the Playworld, the Nether and the End, and a build can only be scanned there.

Open the map, when it is showing, opens the full live map over the build, not the cut-out on its page, so you can see what is around it and find your way there.

Guild projects

A guild's owners and officers can put a build down for the whole guild: /build place <id> guild, or For my guild in the preview. A guild has one project going up at a time.

• It stands on your own land. The whole build has to sit inside one claim of yours, and you're its landowner. It counts as one of your builds going up.
• Every member can feed it. It starts open to the guild only. Its owners and officers can open it to help from everyone or add helpers by name.
• Owners and officers run it. They start and pause it and bind its chests. Only a guild owner can take materials back out or cancel it.
• The landowner decides who can find it. It starts with its location and map hidden and visits off. Only the landowner can show where it is, show the map, let people visit or move it.
• If the landowner leaves the guild, the project pauses. The guild's owners have 7 days to take out what's in its chests or cancel it, and after that it's the landowner's own build.
• If the guild disbands, the project becomes the landowner's own build straight away. Everyone who fed it keeps their name on it.
• It earns your guild XP. Each quarter built adds guild XP, up to 120 a week. The more members who've helped by then, the more it adds. Gifts from outside the guild help build it but add no guild XP, and the same blueprint pays a guild once in 60 days.

The Settler title. When a guild project of at least 200 blocks is finished, everyone who gave it enough while they were in the guild gets the Settler title, as long as at least two members did. Enough is 16 to 64 items, depending on how big the build is, after anything they took back out. Leaving the guild or the guild disbanding before the finish takes nothing away. Wear it with /tags.

Your guild's settlement and its ladder are on the guilds page.

Speeding it up with Coins

Anyone can spend Coins on any build. It is how viewers help a streamer's build along.

The clock only runs while the build is using it. A speed-up counts down while it is placing blocks — not while it is paused, waiting for materials, or asleep with nobody near. Keep-it-going counts while it is going. Time you paid for is never spent on a build that is stopped.

If a build finishes or is cancelled before the time you bought runs out, the unused part comes back to you as powerup credit. Your next speed-up or keep-it-going spends credit before Coins, on any build.

Cancelling

Only the owner can cancel. Whatever was already placed stays where it is. A build that never got started is simply removed.

Taking a finished build off the list. Pulled it down, or listed the wrong thing with /build add? Its owner can take it off the builds list from its own page. The blocks in the world stay exactly where they are; only the page goes.

Build contests

Every other Friday a new theme goes up at /builds/contest. You get 10 days to build to it, then everyone votes for the one they like best, and the winner takes 500 Coins.

Contest builds are built by hand. Blueprints don't count. Here is how to enter:

1. Build something new to the theme, by hand, after the contest opened. It has to stand on your own claim or one you're trusted in, like your guild's.
2. Select just the build with the Build Selector (/build select: left-click one corner, right-click the other). Leave out the ground and trees around it: everything inside the selection counts.
3. Run /build add <name> to put it on the builds list.
4. Open /builds/contest and enter it. One build each, and you can swap it until building closes.

How the server looks at it. When you add a build, the server reads its block log for that spot since the contest opened and counts the blocks that you, players trusted in the claim, or your guildmates placed by hand and that are still standing. Blocks placed and broken again don't count, and nor do blocks that were already there.

• If most of the build was placed by hand during the contest, it goes straight in.
• If only part of it was, or the server couldn't read the block log, it waits for a quick look from staff before it goes on the ballot.
• If most of it wasn't placed by hand during the contest, it can't go in.

What can't go in: a build put down from a blueprint, even one you finished by hand in manual mode; anything standing where a blueprint was put down, even if that build was cancelled or taken off the list; and a private build. The contest page lists your builds and says why any of them can't go in.

Staff can take out a build that breaks these rules. You'll get a notification saying why, and you can still enter a different build. A build that's in a running contest, or one staff took out, can't be taken off the builds list.

On stream

Every build page has an overlay for OBS. Add its link as a browser source, and viewers watch the progress bar move as they feed the build.

Commands