• v5.3.4 dcfaf6a52b

    v5.3.4
    All checks were successful
    CI / build-and-test (push) Successful in 2m38s
    CI / docker-build (push) Successful in 32s
    Stable

    joeyr released this 2026-10-10 00:34:15 -05:00 | 4 commits to main since this release

    Long answers get time to finish, a deploy no longer fails a Confirm click
    partway through, a stale DISCORD_GUILD_ID no longer keeps the bot down, and
    a DClone spawn reported as 6/6 stays up for 12 hours.

    Fixed

    • A long answer from Claude could be cut off, and the question failed.
      Each API call had 60 seconds, set before the models thought and before
      chat ran on Sonnet 5.5. An answer arrives whole once the model has
      finished, thinking included, so a hard question at high effort could run
      out of time, and the identical request was then sent three more times,
      about four minutes, before the question failed. Each call now has 3
      minutes, a request that runs out of time is sent once more rather than
      three times, and no call runs past 13 minutes from the question, so the
      reply or the error still reaches Discord inside its 15-minute window. The
      start-up key check keeps its 60 seconds.
    • A Confirm click during a deploy could report a failure after the change
      had gone through.
      Shutdown closed the fantasy server's MCP sessions
      before waiting for interactions in progress, so a Confirm click mid-call
      failed, and an espnff mcp question mid-loop lost its tools. The sessions
      now close after that wait. The LoL and D2 pollers still stop before it.
    • A stale or mistyped DISCORD_GUILD_ID kept the bot from starting.
      After registering its commands globally, the bot clears that guild's
      commands, and a refusal there (a 403 from a guild the bot has left) failed
      startup, so the container restarted into the same failure. It now logs a
      warning and starts. .env.example now says what the variable is for: a
      guild to clear leftover commands from, not one to register to.
    • A DClone spawn that the tracker reports as 6/6 was deleted at the
      reset.
      The bot counted a spawn only when a game dropped from a step
      straight back to idle. A game reported at 6/6 ("Diablo has invaded
      Sanctuary") pinged spawn subscribers under "DClone progress", and the drop
      to idle a poll later deleted that post instead of keeping it up for 12
      hours. The first arrival at 6/6 now counts as the spawn either way.
    Downloads