4.1

VerityAI 4.1

Reminder ID collisions: /verity task reminder IDs were generated from a counter that reset to 1 on every server restart, so a restart could produce duplicate IDs and make /verity task remove <id> remove the wrong reminder. IDs are now derived from a UUID and never collide across restarts.
AI requests failing on "Empty choices in response": some free OpenRouter models occasionally return HTTP 200 with no choices under load. This is now treated as a transient error and retried with backoff instead of immediately failing the request.
Blank/placeholder API keys: an empty or leftover placeholder entry in ai.api-keys could get sent as an empty Authorization header, causing a 401 Missing Authentication header error. Blank/placeholder keys are now filtered out at load time.

Owner identity is now tied to the player's UUID, not just their name. Previously, /verity owner <player> stored only a name, and every check for "is this the server owner" compared names — which is spoofable on an offline-mode server, since anyone can log in with any username. Running /verity owner <player> now requires the target to be online (so their real UUID can be recorded) and all internal checks use that UUID.
⚠️ If your server runs in offline-mode, note that this only closes part of the gap — offline-mode UUIDs are themselves derived from the player name, so the strongest fix is enabling online-mode: true (real Mojang/Microsoft authentication) if you're granting the owner elevated console-level command access through Verity.

Automatic quests: Verity can now send everyone online a fresh quest suggestion on a timer, on top of the existing on-demand /verity quest. Configurable with /verity quest interval <minutes> (0 disables it), defaults to every 30 minutes.
Full command access mode: commands.whitelist-mode: "all" in config.yml lets Verity run any command the asking player already has permission for, instead of requiring an explicit per-command whitelist. Commands still always run as the asking player (never more power than they already have), and a small set of server-critical commands (op, deop, stop, restart, ban, whitelist, ...) are always blocked regardless of this setting.

No breaking config changes — existing config.yml files keep working as-is. New settings (economy, quests, commands.whitelist-mode, server-info.owner-uuid) are additive; add them manually to an existing live config.yml if you want the new behavior (see the updated config.yml in this release for reference).
If you're hitting HTTP 404 "This model is unavailable for free" or HTTP 429 rate limit errors, that's an OpenRouter-side change (the specific free model was discontinued, or you've hit the free daily cap), not a plugin bug — see the model recommendations in the README.