Questions about VoxelSprout Policy

On the server only. It does nothing in a player's own mods folder. Players install BuildPrint or Sorted as usual and nothing else. Players without those mods are not affected at all. See Installing.

Yes. There are two files: a Bukkit plugin for Bukkit, Spigot, Paper and Purpur, and a Fabric server mod for Fabric (it needs Fabric API). Both are for Minecraft 26.1 to 26.3. There is no NeoForge or Forge server version.

Yes. Remove the BuildPrint Policy jar and put VoxelSprout Policy in its place. On the first start your settings become BuildPrint's part of the new config file, and the old file is renamed to end in .moved. Your old buildprintpolicy.* permissions keep working for BuildPrint's rules.

/bppolicy is now /vspolicy. See Moving from BuildPrint Policy.

No. After a fresh install everything is allowed, and players see nothing until you change a rule. BuildPrint's paste goes through the server from the start. Run /vspolicy in game to open the chest menu when you want to turn something off.

On Bukkit, yes: give that rank vspolicy.allow.buildprint.printer. vspolicy.allow.buildprint.* keeps every BuildPrint feature for them. Your caps, like the printer's speed, still apply to them. They get the change when they rejoin, or after your next /vspolicy change or reload. See Permissions.

The Fabric version has no per-player permissions yet. Its rules are the same for everyone.

Usually it is the mod version. The rules are something the mod follows, so a version that doesn't know a rule ignores it. Sorted follows these rules from its next version on; the Sorted versions out now ignore them. Older BuildPrint versions ignore the rules that came after them, like the free camera.

Also check that the player's rank has no vspolicy.allow permission for it, and that they have rejoined since you changed permissions. And a modified client can ignore the rules on purpose: this is not anti-cheat. See Not anti-cheat.

No. It only sets rules for BuildPrint and Sorted, and only versions of them that follow server rules. Turning off creating schematics stops players copying builds off your server with BuildPrint. It does nothing about Litematica, world downloaders or any other mod. Your anti-cheat and your server rules are still what covers those.

A rule id without a mod name means that feature in every mod that has it. /vspolicy disable printer turns off the printer in each mod that has one. To name one mod, write buildprint.printer. Every id is on Rules per mod.

/vspolicy message clear. Or empty message in the config file and run /vspolicy reload. The note can be up to 256 characters, and every mod shows it next to its rules.

No. With VoxelSprout Policy on the server, BuildPrint sends the blocks and the server writes them itself, so no commands and no operator status are needed. Players do need to be in creative mode; the server checks that itself.

Cap how big one paste may be with /vspolicy limit buildprint.paste_max <blocks>, or turn paste off with /vspolicy disable buildprint.paste. See Paste on the server.

Install it on the backend servers, not on the proxy. Each backend sends its own rules, so a creative server and a survival server behind one proxy can have different ones. The mods forget the last server's rules when the proxy moves a player. It hasn't been tested with every proxy setup, so if something is off, say so on Discord. See Proxies.

The first page of the chest menu says how many of the players online run each mod. It doesn't list them by name.