Minecraft Webshop for Paper, Purpur, Spigot and Velocity
Compatibility questions come up before anything else, so here is the direct answer. The bridge plugin targets the Bukkit API, which means Paper, Purpur and Spigot all work, and Folia is supported because the bridge already runs off the main thread.
Proxy networks need one clarification that trips people up: Velocity and BungeeCord do not forward RCON. The bridge belongs on the backend servers that actually hold player data and execute commands, not on the proxy itself.
For a network, the usual arrangement is a bridge on each backend server, with products pointed at whichever server should execute the command.
What you get
- Paper, Purpur and Spigot are supported through the standard Bukkit API.
- Folia is supported: the bridge does not run on the main thread.
- Velocity and BungeeCord networks work by connecting backend servers rather than the proxy.
- Multiple servers can be registered, with each product delivering to the correct one.
- Player presence is polled across connected servers, so the online check works on a network.
- No port forwarding on any server in the network, because every connection is outbound.
Try it with your own players
Free for 7 days, no card required. Set up your store, connect your server, and let real players buy something before you decide.
Frequently asked questions
Can I install the bridge on my Velocity proxy?
No, and it will not work if you try. Proxies do not handle RCON or execute game commands. Install it on the backend Paper or Purpur servers instead.
Does it work on a network with several servers?
Yes. Register each server and assign products to whichever server should run the command, which is how survival and skyblock stores are usually kept separate on one network.
Which Minecraft versions are supported?
The bridge uses standard Bukkit APIs and console command execution, so it is not tied to a specific game version. Modern Paper and Purpur builds are what it is tested against.
Will it affect server performance?
It holds one outbound WebSocket connection and executes commands as they arrive, off the main thread. The overhead is negligible on any server large enough to need a store.