GuildChatBridge began with a roleplaying idea: what if my World of Warcraft character could have a voice of their own? While I controlled movement, combat and other actions, a local AI could notice what happened around the character, interpret guild conversation and occasionally speak in character. The aim was not a gameplay bot. It was an experiment in giving a player-controlled character a second, partly independent social life.
The first ambition was an AI that could read guild chat and respond there without my composing every line. Later possibilities included reactions to crafting, fighting, loot and nearby events, with party or raid conversations as possible extensions. The character should speak when something mattered to them, not fill every silence.
Why the project is paused
The original attempt stalled because I could not complete the automatic conversation loop with the tools and access available to me. At the time, I understood sending chat to require direct player input, and did not want to rely on unsupported or intrusive workarounds.
That explanation needs one technical qualification: SendChatMessage exists, and this prototype itself calls it for guild chat. Available API references and examples of 1.12-era addons show that automatic chat transmission is not categorically impossible. What remains unsolved here is a reliable, permitted, live connection between game events, an external AI and in-game speech, including the rules of the particular server. No autonomous response loop is implemented or verified. See architecture…