Paste on the server
With VoxelSprout Policy installed, the server writes BuildPrint's pastes itself: quick, and no operator status needed.
Players in creative mode can paste a placed schematic into the world in one go with BuildPrint. With VoxelSprout Policy on the server, BuildPrint sends the blocks and the server writes them itself: a slice of each tick, without block updates, with chest contents and sign text. That is much quicker than the other ways to paste on a server (Axiom, /fill commands for operators, WorldEdit), and it needs no operator status.
- Only players in creative mode can paste. The server checks this itself, not only the mod.
/vspolicy disable buildprint.pasteturns it off. BuildPrint then won't paste on your server in any way: not through Axiom, commands or WorldEdit either./vspolicy limit buildprint.paste_max <blocks>caps how many blocks one paste may change. Players paste fewer layers at a time for a bigger build.- Each player can undo their last 5 pastes, until they leave.
- Filling a build's containers from the schematic goes through the server too: the items go straight into the chests, barrels and hoppers already standing in the world, and it can be undone the same way.
- On Bukkit, chest contents and sign text go in with
data merge blockrun by the console, so those lines show up in the server log.
Players see the paste cap in BuildPrint's Server rules screen. More on paste from the player's side: BuildPrint wiki: Paste.
Something missing or wrong on this page? Say so on Discord.