Build together

Share a build with a code. Everyone sees it in the same place and sees the progress.

Start a session #

  1. Load the build and put it where it belongs.
  2. In the Loaded tab, select it and click Build this together... in the Build group.
  3. Choose New session, give it a name, and choose whether to share the file with Host the schematic file.
  4. On the right, tick the builds that go in. Every loaded build that is saved to a file and not in a session yet is listed, with this one ticked. A session can hold several builds side by side.
  5. Click Start session. The code and the link come up: copy them and send them to the others.

A build has to be saved to a file before it can be shared, because builds are matched by their file.

Not signed in? You can start it as a guest. Only this game can then end the session or change its settings.

To add builds to a session you run or are an admin of, choose Add to a session instead, and pick the session. Everyone in it sees them straight away. Add builds... in the Sessions screen does the same.

Share the file, or not #

Host the schematic fileWhat happens
OffNothing leaves your computer. The others need the same file already. BuildPrint matches it for them.
OnThe file and a picture go online, so the others can load it and the invite page shows it. It is deleted after 30 days without use.

Join a session #

Press B, click Sessions... at the bottom of the Loaded tab, type the code under Session code and click Join. You do not need an account. People who are not signed in show as Guest.

The Sessions screen #

  • Opens from Sessions... in the Loaded tab, or with /buildprint sessions. While you are in a session the button shows how many.
  • Lists your sessions. For each one: its code (click to copy), Copy link, Open page, and who is in it under People.
  • The owner and admins can Make admin or Remove admin.
  • Leave stops following a session. Click it twice to confirm.
  • When a shared build is not showing, the button reads, for example, Sessions: 2 hidden, and the screen says why: another world, another dimension, a file that could not be downloaded, or a file nobody shared.

On a build that is in a session, the Loaded tab has Share, which shows the session's code and link, and Stop sharing.

While you build #

  • Everyone sees the builds in the same spot.
  • The material list shows the progress of the whole group, also when you are far from the build.
  • Gathering, the others' cards leave a material to whoever is getting it. See below.
  • You can be in several sessions at once, and a session can hold several builds.
  • The session stays while the owner is offline. Someone who joins later sees everything.
  • A build only shows in the world it belongs to.
  • Builds shared from another address of the same server are offered in chat: Show here shows them, Not this server stops asking. /buildprint sessions can change it later.

Gather together #

When several of you use Gather in the material list of a shared build, you do not all go out for the same thing. See Gather.

  • Picking up a material on the list leaves it to you. It goes off the others' cards.
  • Each card says who is getting what, one line per person, for example Alex gets Oak Log, Sand.
  • What you carry stays yours until it is placed. A material goes back to everyone once the build no longer needs it, when you stop gathering, or when you leave the session.

Who can do what #

MemberAdminOwner
See the builds and the progressYesYesYes
Hide a build on your own screenYesYesYes
Move builds and swap blocksNoYesYes
Add builds, or remove one for everyoneNoYesYes
Make someone adminNoYesYes
Take admin away from someoneNoNoYes
End the sessionNoNoYes

The live page #

The link of a session opens a page on this site with the builds in 3D and the material list, updated as people build. The owner and admins who have linked BuildPrint to their account can swap blocks and manage members from there.

Leave or stop #

  • Leave stops following the session. Builds from others are unloaded, your own stay.
  • Stop sharing takes your build out of the session, for everyone. It asks first. It stays loaded for you.
  • Removing a shared build from the Loaded tab asks what you mean: Hide it on your screen only, Leave session, or Remove for everyone....
  • When the last build is taken out, the session ends and its code stops working.

Something missing or wrong on this page? Say so on Discord.