AI Ticket Bot v2.4.14: smarter forms, reliable staff pings

AI Ticket Bot v2.4.14 is a small one. It is mostly about clearing the errors reported since the last release, in the bot and in the AI, plus one real change in how applications and forms are handled. Everything here is live on every plan, including the free tier.

Applications and forms stay with the AI

A ticket that turned into an application or a form, so staff applications, partnership requests, anything built around a set of questions, used to get pushed straight to your team instead of being worked through. Nexus now follows up on those scenarios properly, asks the next question, and only escalates when it genuinely needs a human. If your server runs applications through tickets, this is the change you will notice first.

Staff pings land, even with hundreds of roles

Some servers saw the bot fail to ping the configured staff role, and it showed up most on servers with a very large role list. That is fixed, so the staff ping is stable again regardless of how many roles you have. While you are there, it is worth confirming in your dashboard that the staff role set for your panels is still the one you want.

Nexus searches its memory with fewer tokens

Nexus got a token usage improvement on memory search. The answers you get are the same, it simply does the same job more efficiently under the hood.

A batch of fixes

Alongside the above we cleared a batch of errors reported since the last update, both in the bot and in Nexus itself, so opening, handling and closing tickets is steadier day to day.

Update now

This rolls out automatically, with nothing to reinstall and nothing to reconfigure. If you missed it, the previous update added /ticket close-request, /mytickets, /vote and the redesigned embeds.