94 releases 94 tags

RSS feed

• v5.3.5 1c9c16ec5b

  Compare

  v5.3.5 Stable

  joeyr released this 2026-10-10 08:58:37 -05:00 | 3 commits to main since this release

  Nine rarer bugs, each needing bad timing or an unusual answer to show up. A
  cut-off answer now says so, Make Public and the fantasy Confirm buttons hold
  up under slow or failed clicks, a LoL game is posted once and keeps its
  result, a long watchlist lists, a stalled Data Dragon no longer holds up
  startup, and a new DClone board shows the latest grid.

  Fixed

  • An answer cut off at its length limit was shown as if complete.
    Thinking counts toward Claude's token limit, so an answer can stop half
    written, or before it starts. A half answer was shown and saved for
    follow-ups, a "let me look that up" before a cut-off tool call passed for
    the answer, and thinking alone failed as an API error. What was written is
    now shown with a note that it was cut off (or a message saying none of it
    was), and it isn't saved for follow-ups.
  • Make Public could post an answer twice. A long post can outlast
    Discord's 3 seconds to answer a click, which shows "This interaction
    failed" beside a button that still works, and a second click posted the
    answer again. A second click while posting now says so. A retry after a
    post failed partway also posted its start a second time; it now picks up
    at the part that failed.
  • A fantasy Confirm message could pass 2,000 characters and stop
    updating. Each line was clipped, but the message wasn't: five long
    changes with five long failures under them went over, and Discord refused
    the edit after the change had run, so its outcome never showed. Lines are
    now clipped shorter until the message fits.
  • A Confirm press that Discord didn't take left the change stuck. If
    answering the press failed, the change stayed "running" though nothing had
    been sent, and every later press said it had already been handled. It now
    goes back to waiting, so pressing again runs it.
  • Two watched players in one LoL game could get it posted twice. Their
    detections, a moment apart, both found no row for the game, and the step
    meant to reserve it succeeded for both. The game is now claimed with an
    insert that only one detection can win.
  • A game that ended while its ranked data was loading lost its result.
    Ranks and recent form can take minutes behind the Riot rate limit, and a
    game that ended meanwhile (a remake ends at the next poll) had its result
    replaced by the in-progress embed. The late edits now check that the game
    is still live first.
  • /aufhocker lol monitor-list failed past about 30 summoners. The whole
    list went in one message, and Discord refuses one over 2,000 characters.
    It now continues in follow-up messages.
  • A stalled Data Dragon could hold up startup for minutes. Its two
    requests had no timeout, and every plugin after the LoL one, and the health
    endpoint, waited on them. Each now has 10 seconds, and champion names fall
    back to IDs, as they already did when Data Dragon was down.
  • A new DClone status message could show an old grid for hours. A poll
    that landed while /aufadmin d2 dclone-board was posting couldn't see the
    new message to update it, and later polls with the same data skipped it.
    It is now brought up to date as soon as it is recorded.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads