Veyl FAQ

No. Builds upload the JAR to the Veyl worker. Obfuscation runs on the server; the protected JAR is written back to your build/libs (or Maven output). There is no local obfuscator runtime in the CLI / Gradle / Maven plugins.

Your source never leaves the machine. The built JAR is sent over HTTPS with your login session. Job history keeps metadata; older JAR payloads are purged while stats remain.

Usually the plugin version is not on the Gradle Plugin Portal yet.

1. Run veyl add again.
2. Or pin a published version: veyl add --version 1.0.10
3. Ask in Discord if you need the latest build.

Source / Portal: gradle-veyl · plugins.gradle.org

pluginManagement { … } must be the first statement. If rootProject.name is above it, Gradle errors. See Gradle.

veyl login
veyl whoami

Wrong password, disabled accounts, and unreachable API print explicit errors.

The Paper/Bukkit main class was renamed. Keep it:

veyl recommend path\to\YourPlugin.jar --out veyl.rules

Put veyl.rules in the project root (or keep 'me.example.MyPlugin' in Gradle). Details: Keep rules.

Default is mostly rename on. Turn on more passes in the veyl { } block / Maven config: aesStrings, hiddenNumbers, hiddenCalls, controlFlow. Compare a class in the dashboard before/after preview when available.

Same worker and passes. The web dashboard is interactive (presets, preview). Gradle/Maven/CLI are for everyday builds with the same account.