BungeeCord · Velocity

PROXY PLUGIN GENERATOR

Plugins for the layer in front of your servers. Describe the network behaviour you need - queues, routing, cross-server chat, transfers - and Codexe writes it against the BungeeCord or Velocity API you choose.

Why generate a proxy plugin

The right API for the job

Proxy code is not Bukkit code. The generator uses the proxy's own event model and connection API instead of producing server-side calls that will not resolve.

Network-wide by design

One plugin that sees every player on every backend server - the natural place for queues, global chat, staff alerts and routing rules.

Both halves when you need them

Plenty of network features need a proxy plugin and a small backend companion talking over plugin messaging. Describe the whole flow and Codexe can generate both.

Working on the backend instead?

Gameplay, blocks, items and world events all live on the backend server, which means a Spigot, Paper or Folia plugin - or a Kotlin plugin if you prefer that language. The plugin docs cover where each type of code belongs.

Example prompts

> A Velocity plugin with a join queue for a full server: players wait in a lobby, get a position message every 15 seconds and are connected automatically when a slot frees up.
> A BungeeCord plugin that relays chat between all backend servers with a per-server prefix and a toggle command to mute the global channel.
> A Velocity plugin adding /send <player> <server> and /sendall <server> for staff, with a permission node and a message when the target server is offline.
> A BungeeCord plugin that routes players to the least-populated lobby on join and falls back to a maintenance server if none are reachable.

Proxy plugin generator FAQ

What is the difference between a proxy plugin and a normal plugin?

+

A proxy plugin runs on BungeeCord or Velocity, which sits in front of your backend servers. It has no worlds, blocks or entities - the API is about players, connections and which server someone is routed to. Anything that touches gameplay has to be a Bukkit-family plugin running on the backend server instead.

Are BungeeCord and Velocity the same API?

+

No. They solve the same problem but have completely different APIs, event models and plugin descriptors. Say which one you are targeting in your prompt - code written for one will not compile against the other.

Can a proxy plugin change blocks or give items?

+

Not directly. The proxy has no access to world state. The usual pattern is a proxy plugin plus a small companion plugin on each backend server, talking over plugin messaging - describe that setup and Codexe can generate both halves.

How do I send a player to another server?

+

Through the proxy's connect API, which is exactly the kind of thing this target exists for. Generated code handles the server lookup and the failure case where the destination is offline.

Does it handle plugin messaging channels?

+

Yes, if you ask for it. Describe what the proxy and the backend need to tell each other and the generator wires up the channel registration and the message handlers on both sides.

Which one should I run?

+

Velocity is the modern choice - faster, actively developed and with a cleaner API. BungeeCord is older and still very widely deployed, so pick it if your network already runs on it or you depend on a BungeeCord-only plugin.

Need something that runs on the backend servers instead of the proxy? Codexe also generates:

READY FOR A NEW PROXY PLUGIN?

Free tier refills 50K tokens daily, enough for a working proxy plugin in one pass.

START BUILDING
BungeeCord & Velocity Plugin Generator – AI-built proxy plugins | Codexe