---
title: "Installing - VoxelSprout Policy wiki"
description: "Which file goes where, on Fabric and on Bukkit, Spigot, Paper or Purpur, and moving from BuildPrint Policy."
url: https://voxelsprout.com/voxelsprout-policy/wiki/installing
---

[VoxelSprout Policy wiki](https://voxelsprout.com/voxelsprout-policy/wiki)Installing

# Installing

Which file goes where, on Fabric and on Bukkit, Spigot, Paper or Purpur, and moving from BuildPrint Policy.

VoxelSprout Policy goes on your server. It lets you turn features of [BuildPrint](https://voxelsprout.com/buildprint) and [Sorted](https://voxelsprout.com/sorted) off for the players on it, tells them what is off and why, and does BuildPrint's paste on the server side.

It does nothing on a client. Players don't install it: they install BuildPrint or Sorted as usual. Players without those mods are not affected.

## Which file

| Server                                                  | File                                                       | Goes in  |
| ------------------------------------------------------- | ---------------------------------------------------------- | -------- |
| Fabric, Minecraft 26.1 to 26.3                          | voxelsprout-policy-fabric-<version>.jar. Needs Fabric API. | mods/    |
| Bukkit, Spigot, Paper or Purpur, Minecraft 26.1 to 26.3 | voxelsprout-policy-bukkit-<version>.jar                    | plugins/ |

There is no NeoForge or Forge server version.

## Install

1. Download the file for your server from [Modrinth](https://modrinth.com/project/voxelsprout-policy).
2. Put it in `mods/` (Fabric, next to Fabric API) or `plugins/` (Bukkit), and start the server.
3. Everything is allowed until you change it, and players see nothing until then.
4. Join and run `/vspolicy` to open the [chest menu](https://voxelsprout.com/voxelsprout-policy/wiki/chest-menu), or use the [Commands](https://voxelsprout.com/voxelsprout-policy/wiki/commands) from the console.

## Moving from BuildPrint Policy

VoxelSprout Policy used to be BuildPrint Policy. Remove the BuildPrint Policy jar and put this one in its place. Your settings move over on the first start:

* **Fabric**: `config/buildprint-policy.json` becomes BuildPrint's part of `config/voxelsprout-policy.json`, and the old file is renamed to `buildprint-policy.json.moved`.
* **Bukkit**: `plugins/BuildprintPolicy/config.yml` becomes BuildPrint's part of `plugins/VoxelSproutPolicy/config.yml`, and the old file is renamed to `config.yml.moved`.
* `/bppolicy` is now `/vspolicy`. `printer-speed`, `printer-range` and `paste-max` are now `/vspolicy limit buildprint.printer_speed`, `buildprint.printer_range` and `buildprint.paste_max`.
* The old `buildprintpolicy.admin` and `buildprintpolicy.allow.<feature>` permissions keep working for BuildPrint's rules. The new ones are on [Permissions](https://voxelsprout.com/voxelsprout-policy/wiki/permissions).

Released BuildPrint versions keep working with it: they get the same rules as before. Sorted follows the rules from its next version on; the versions out now ignore them.

[Next The chest menu](https://voxelsprout.com/voxelsprout-policy/wiki/chest-menu)

Something missing or wrong on this page? Say so on [Discord](https://discord.gg/CvdkGbEW4y).