If the download dies right at the very end, it's almost never the file. Some security tool is scanning it and cutting the connection at the finish line. Nine times out of ten it's NordVPN's Threat Protection (its "URL cleaner"): switch it off, download, switch it back on. Same fix if you run Malwarebytes Browser Guard, Avast/AVG Web Shield, Kaspersky, or a work proxy that inspects traffic. Still won't go? Try another network, or email me and I'll get you the jar directly.

Only if you rename the parts that need their real names, and wuuvy already knows most of those. The default fortify preset never renames classes, which is the thing reflection and service loaders care about most, and names passed to Class.forName and friends are spotted and left alone. The mod presets go further for loaders. Everything else gets obfuscated. When in doubt, run it and check the mapping file; it tells you exactly what changed.

wuuvy runs on JDK 8 or newer and protects jars targeting Java 8 upward. Passes that use newer JVM features, such as tricks built on invokedynamic from JDK 9 up, detect the class file version and fall back gracefully on older targets, so one config works across your whole toolchain.

Yes. That is exactly what the mod and mod-strict presets are for. They are tuned for Forge, Fabric, and NeoForge loaders and are aware of Sponge Mixin transformers, so entry points, mixins, and classes loaded through reflection keep working while the rest of your mod is protected.

Yes. Every build emits a mapping file in the standard ProGuard format alongside the jar. When a crash report comes in, retrace it against the mapping to recover the original class, method, and line information.

That is the intended home for it. It runs headless, pin a seed and the same input and config produce the exact same output every time, and the CLI returns clear exit codes, so it slots into any pipeline. Gradle and Maven plugins are included if you would rather wire it into the build itself.

That's up to you. light and methods barely register at runtime; paranoid trades speed for the most protection. Every one of the 150+ passes is a separate switch, so you set the balance, not us.

Yes. Commercial usage rights are part of every Developer License. Ship obfuscated jars in paid products, subscriptions, client deliverables, or anything else you charge money for. There are no royalties, no revenue share, and no separate commercial tier to unlock.

No. The protected jar is completely self contained. Your users never install anything extra, never see a license prompt, and never connect to our servers. To them it is simply your application.

Never. wuuvy does its work at build time and then gets out of the way. There is no runtime agent, no callback to wuuvy servers, and no expiry baked into the output. A jar you protect today will run exactly the same in ten years.

Yes. Hand wuuvy a keep-list of the classes that make up your public API and let it tear apart everything behind them. Your customers code against clean, documented interfaces while your internals, helpers, and protocol details stay out of reach.

That is one of its main jobs. String encryption hides your endpoints and keys, flow obfuscation buries the validation logic, and the junk passes drown the real check in hundreds of decoys. The code crackers go hunting for first becomes the code that is hardest to find.

They can try. A decompiler will produce output, but it will be a wall of renamed classes, encrypted strings, and scrambled control flow instead of your source code. No tool on earth makes reverse engineering impossible. wuuvy makes it cost far more effort than the secrets inside are worth.

Yes. The license is per developer, not per company or per project. If you build jars for clients, every one of them can ship protected, and your clients do not need to buy their own license to receive or run what you deliver.

No. A Developer License is a single $140 payment. It includes lifetime version updates, every transformation pass, commercial usage rights, and unlimited protected builds. There is nothing else to pay, ever.

As many as you like. Licensing is per developer, not per project or per build. One license covers every jar you personally ship, commercial or otherwise, forever.

Every purchase comes with a 15 day money back guarantee. If wuuvy is not the right fit for any reason, email support@wuuvy.com within 15 days of purchase and we will refund you. A refund deactivates your license key. After the 15 day window, sales are final, so give wuuvy a proper run in your real build early. Questions before or after purchase are welcome on Discord or by email.