• v1.19.0 863a90e510

    v1.19.0 — mentions resolve to fantasy teams
    All checks were successful
    CI / build-and-test (push) Successful in 2m13s
    CI / docker-build (push) Successful in 46s
    Stable

    joeyr released this 2026-09-10 22:25:44 -05:00 | 54 commits to main since this release

    Fixed

    • /aufhocker espnff mcp can resolve a Discord mention to a team. Asking
      "how is @Someone's team doing?" got back "I can't resolve a Discord mention
      to an ESPN team on my own" — true, and useless, because the bot had the
      mapping and wasn't passing it on.

      The prompt carried only the asker's own team id. It now carries every mapped
      manager as <@id> (Name) manages team_id N, joining the two halves that are
      configured separately and meet nowhere else: ESPNFF_TEAM_MAP supplies the
      team id, user-mappings.json supplies the name. A manager with no name entry
      is still listed — unnamed and resolvable beats named and absent.

      Worth knowing why it could not work before: a mention arrives in the query as
      raw markup (<@790374074235879454>), not a display name; the fantasy server
      knows only ESPN display names; and user-mappings.json feeds channel
      history, which this command deliberately never sends. Nothing in that chain
      connected a snowflake to a team.

      An unmapped id still cannot be placed, and the model is told to ask which
      team is meant rather than pick one — a plausible wrong team is the failure
      that reads exactly like an answer.

    Downloads