Readable code
Plugins are read more than they're written. We keep codebases small, names clear and structure predictable so the next person to touch it — you, us, or a stranger on GitHub — can find their way around without an archaeology degree.
About Vectra Studios
Who we are
A small Minecraft development studio founded in January 2026, currently building PVP practice cores and minigames for Java and Bedrock.
The studio
A small team, one Discord
Vectra Studios is a small team of developers. We founded the studio in January 2026 to build Minecraft PVP content full-time — practice cores, minigames and the plugins that hold them together.
Right now we're working on three projects: CPvPWars, a Paper plugin that combines CPvP and Bedwars into one minigame; VectraCore, an open-source Bedrock PVP practice core for PocketMine-MP; and AerisCore, a Java Edition PVP practice core. All three are in active development.
We work on both the Java and Bedrock sides. We keep the codebases small and readable because we're the ones who have to maintain them.
Most coordination happens in our Discord. If you want to commission work, follow the projects, or just talk about Minecraft PVP development, that's where to find us.
Scope
What we build
PVP practice cores and minigames, mostly. We develop for Paper on the Java side and PocketMine-MP on the Bedrock side, and release reusable work as open source where it makes sense.
- Java plugins for Paper / Spigot
- PocketMine-MP plugins for Bedrock
- PVP practice and minigame systems
- Open-source releases under permissive licenses
vectra-core
Open source
Built on open source
Paper, PocketMine-MP, every library we depend on — the Minecraft server ecosystem runs on open source. We contribute back where we can, and release our own reusable work under permissive licenses.
- MIT-licensed utilities and libraries
- Public plugin frameworks with documented APIs
- Community contributions welcome and reviewed
- Internal tools released when they're stable enough
MIT · public · maintained
Values
How we work
Three things we keep coming back to when a decision isn't obvious.
Long-term support
A server is a long-lived thing. We document what we ship and stick around for the follow-up bugs. When we build something, we keep it maintained rather than dropping it after release.
Community first
Most of our work happens in the open. Public repos, public issue trackers, public roadmap. Commission work stays private when needed, but everything reusable goes upstream so the next server owner doesn't have to write it again.
Want to work with us?
Tell us what your server needs. Commission requests go through our contact form — general questions are welcome in Discord.