v2.9.46

Disabled automatic full member-list scraping on connect (was causing gateway lag/timeouts and slowing startup); removed the Auto-Vote DM-history sync and the owner/customer badge-profile background lookups - fewer non-essential background API calls, more human-like connection behavior.

v2.9.45

Randomized daily break enabled by default; Discord status now drifts naturally over time instead of staying frozen; every command's send timing now varies by a real +/-15% window by default (was a near-fixed ~1s window); captcha solving now uses only NopeCha + NoCaptcha (NoneCap removed).

v2.9.44

Gem tracking reliability fixes, captcha cookie rate-limit backoff, hCaptcha provider chain timeout fix.

v2.9.43

v2.9.43

• Auto Huntbot and Letter Verify are now free for everyone — no longer paid add-ons; just toggle them on in the Plugins tab.
• Gem use reworked. The bot now reads each hunt reply's gem status (the [x/n] counters) on every message and re-equips a gem the moment it actually runs out — no more re-sending a gem that's already active on a timer. It also spends the lowest-tier gem first in each category (mixed) so cheap gems deplete before the expensive ones (OwO gems have no set bonus, so a matching set gains nothing).
• Support for the alternate HuntBot status panel layout (some accounts show "Time › 14H 35M" instead of "BACK IN 14H 35M"), so an already-running huntbot is correctly detected there.

v2.9.42

v2.9.42

• Auto gem use fixed. Reactive per-hunt gem re-equip was unreachable on the desktop app (it sat behind an early return in the message handler), so spent gems weren't being re-applied automatically. Ported the server's approach so gems are tracked and re-equipped on every hunt, and the special-animal (rare catch) log is restored along with it.
• Captcha detection improved. No more empty/phantom captcha detection: a message is only treated as a captcha when it actually carries a real challenge (the letter-word prompt, "are you a real human? … use the link below", or an owobot verify link) — OwO's own confirmations and chatter no longer trip it. Also catches a captcha that arrives as a reply without an @mention, and prevents a double "resuming" after a solve. A bare behavioural "(N/5)" warning is no longer hammered with tokens (that was a ban risk); it halts and asks for a manual check instead.

v2.9.41

NIGHTOWL v2.9.41

• Auto gem use now matches the web panel: re-equips the moment a gem depletes (even when OwO drops the gem line entirely), reconciling all three categories per hunt.
• Phantom-captcha loop fixed: after a solve, a stray captcha-looking message no longer re-triggers an endless 'Unauthorized' solve loop.
• 'Others' custom commands now stop during captchas and scheduled/post-captcha breaks.
• Remote log + start/stop: the panel relays each account's log and accepts remote start/stop (rendered log text only; no tokens/proxies/passwords).
• Stability fixes.

v2.9.40

NIGHTOWL v2.9.40

• Online log: the panel now relays each account's recent activity log for remote support/monitoring (rendered log text only — no tokens, proxies or passwords are ever sent).
• Captcha provider key rotation updated (server-side).
• Stability fixes.

v2.9.39

Unlimited captcha retry loop (never auto-give-up), scheduled-break log collapsed to one line + remaining time, and rare-catch detection now works without a 'gained' keyword (custom/embed catches). AceData added as a bundled captcha fallback (server-side).

NIGHTOWL v2.9.38

Auto-use gem embed-aware rewrite (OwO now sends hunt/inv/use replies as embeds with empty content — gem tracking, inventory scan, wuse confirmation and 🚫 reject now all read the embed text, matching the owner-server logic), letter-verify now solves in any DM, and a selectable boss channel (Automation → Boss: pin where 'wboss' is sent).

v2.9.37

Special / high-XP catch detection fixed and made more reliable.

• Fixed a bug where the "Special Animal" catch check could silently stop working on gem-empowered hunts (an internal helper was undefined, which aborted the check on any shared-channel catch that wasn't a direct reply).
• A catch now counts as special when it is YOURS and gives 2000+ xp.
• The "gained Nxp" line is now read from embeds too — OwO sometimes sends the hunt result inside an embed with empty message text — and from the follow-up message OwO fires right after the hunt.
• Strict account attribution: another player's big catch in a shared channel can no longer be logged under your account.