Case Study: How Doomwen Stopped Plugin Redistribution on BuiltByBit

Doomwen didn't start out with a business plan, just a cheap laptop and a love of Minecraft. Today Doomwen's plugins have sold more than 3,000 copies on BuiltByBit, and every download comes with a license key the buyer never has to think about.

This is Doomwen's story, mostly in their own words.

Starting on a $100 laptop

"I grew up in a broke country, playing Minecraft on a $100 laptop. I started making plugins for my SMPs, then took commissions to save up for a new PC."

Commissions should have been the steady part. They weren't:

"After multiple clients scammed, I began selling premade plugins to the public on my Discord server."

Selling premade plugins put Doomwen in control of their own work. It also brought a new problem.

The problem: one purchase, many copies

"The problem was redistribution, people would just send these plugins to their friends or resell them."

This is the problem nearly every paid plugin runs into. A plugin is just a jar file. Without anything tying it to the buyer, one purchase can quietly become ten servers, or end up on someone else's store under a different name. At $10 to $20 a plugin, every shared copy is a sale that never happens.

So Doomwen did what a lot of developers do, and built a homemade license system:

"It was weak and unreliable, but it worked."

Moving to BuiltByBit broke the homemade system

Selling through their own Discord meant Doomwen could hand out keys by hand. After the move to BuiltByBit to reach more buyers, that stopped working:

"When I moved to BuiltByBit, my manual system didn't work. That's when I found MCLicense, which automatically injects licenses into jars."

This is what made the difference. With MC License connected to BuiltByBit, a key is written straight into the jar when a buyer downloads it, using BuiltByBit's external license key placeholder. There's no email to wait for, no order ID to send and nothing for the buyer to paste.

Each of those keys becomes a managed license on Doomwen's dashboard:

• It's tied to the buyer. The license shows their BuiltByBit username, so a leaked copy points straight back to who downloaded it.
• It has a server limit. A key passed round to friends stops working once it's on more servers than the license allows. That's what ends casual key sharing.
• It can be switched off. If a copy turns up somewhere it shouldn't, that license can be disabled from the dashboard.

Every response from the license check is cryptographically signed, so a resold copy can't simply be pointed at a fake server that always says "valid".

One month in: Lifetime

"After one month I loved it so much that I bought permanent access for $100, which was one of the best decisions I've ever made."

Doomwen moved to MC License's Lifetime plan: a single payment, with unlimited plugins and licenses, and no subscription. With more than 3,000 purchases across Doomwen's plugins, that one payment now covers every license issued.

A team that listens

Doomwen didn't just use MC License, but helped shape it:

"Over time I came up with ideas to improve it, and the team added everything I asked for. That kind of responsiveness is rare."

We're a small team, and we build MC License for developers like Doomwen. If something would make selling your plugins easier, tell us in Discord. There's a good chance it ends up on the roadmap.

Advice for other developers

Doomwen's recommendation comes with an honest caveat, and it's one we agree with:

"I'd recommend MCLicense to any plugin developer. Just keep in mind that it solves the redistribution problem, not full protection. You still need strong obfuscation to stop plugin crackers."

That's exactly right. A license system stops your plugin being passed around and resold. It does that job for every buyer, automatically. A determined cracker who decompiles your jar and removes the check is a different problem, and the answer is obfuscation on top. We've written a practical guide to obfuscating a plugin with ProGuard that works alongside MC License.

Sell on BuiltByBit too?

If your plugins are being shared or resold, you can set up the same thing Doomwen uses in a few minutes:

1. Create a free MC License account and add your plugin with its BuiltByBit resource URL.
2. Add the %%__BBB_LICENSE__%% placeholder in BuiltByBit (setup guide).
3. Add one line to your plugin's onEnable() (step-by-step tutorial).

From then on, every download carries its own license key. It works the same way on Voxel Shop, and on Tebex, where keys are emailed to buyers.

Start free →