Commands
Every command the mod adds, what it prints, and where it works.
Everything the mod adds lives under /vbf, and typing it on its own prints a short list of the common ones. They are client commands, so they never reach a server and work anywhere the mod is loaded.
Getting in and out of an account
/vbf linkAnywhere/vbf link unlinkAnywhere/vbf statusAnywhereWorlds and the people in them
/vbf sharelinkInside a Fragment· Members/vbf membersInside a Fragment· Members/vbf whitelist add <name>Inside a Fragment· Owner/vbf op <name>Inside a Fragment· Owner or op/vbf invite [days]Inside a Fragment· Owner or op/vbf join <code>Inside a FragmentMods
/vbf packAnywhere/vbf updateAnywherePrivacy and your data
/vbf privacyAnywhere/vbf mapInside a Fragment/vbf data exportInside a Fragment/vbf data deleteAnywhereTelling us something is wrong
/vbf bug-report <text>Anywhere/vbf suggest <text>Anywhere/vbf log share [crash]Inside a FragmentWhat some of them print
A world link
/vbf sharelink[VBF] your Fragment link: vbf:frag-brisk-otter-cedar-lantern
[VBF] friends paste this into Multiplayer → Add Server. It never changes.
An invite code
/vbf invite 14[VBF] invite: FROSTY-BADGER-14 — expires in 14d
[VBF] share with friend: /vbf join FROSTY-BADGER-14
A refusal
VBF: whitelist add failed (403) — only the world owner can change the whitelist.
Things that look like commands and are not for you
Anything beginning /vbf-dev is for development and debugging. One of them is named in a message you may genuinely see: if the mod hands your simulation work to a peer because your connection was saturated, it tells you how to take it back. That is covered in when something is wrong.