Tech • AI • Robotics • Game
🚨🚨 Vibe Coding WoW Forever Mods With Esfand 🚨🚨
3/10TL;DR
A livestreamed coding session exploring World of Warcraft add-on development shifted from basic setup advice to a broader concept for linking in-game chat with Discord through companion tools and mention mapping.
KEY POINTS
From casual coding to add-on design
The session began as an informal plan to build a World of Warcraft add-on with AI assistance, framed as a beginner-friendly project that could become useful enough for public release. The initial goal was modest: create something light and practical rather than a joke tool, then potentially distribute it through CurseForge.
AI tools and editor choices
Discussion centered on which AI coding tools are currently most practical for small projects. Claude, Codex, and Cursor were all mentioned, with Cursor presented as one of the easiest interfaces for non-experts because it reduces reliance on terminal-heavy workflows. The consensus was that, for a simple add-on, the exact model mattered less than having a usable interface and a clean workflow.
Version control seen as essential
A key recommendation was to ensure the add-on files are under Git version control. The project was already being developed inside a local add-on folder so changes could be tested immediately with a game reload, but keeping everything only on one machine was seen as risky. Remote backups through platforms such as GitHub were discussed as the safer long-term option.
Rapid in-game testing workflow
The setup used the add-on folder directly inside the game installation, allowing each change to be tested with a slash reload rather than packaging builds separately. That approach was described as convenient for experimentation and had already been used to make a simple quest-related tool based on existing in-game data.
Strict limits of WoW add-ons
Much of the conversation turned into a technical review of what WoW add-ons cannot do. Standard add-ons do not have general HTTP access, cannot freely read arbitrary files, and cannot open sockets or call web APIs directly. Those limits were recognized as intentional security protections that prevent add-ons from accessing sensitive data on a player’s computer.
Companion apps as the real bridge
Because add-ons are sandboxed, more advanced integrations usually rely on external companion programs. Examples such as Warcraft Logs, Raider.IO, and TradeSkillMaster were cited to show how data can be exported, processed outside the game, and then uploaded or synchronized elsewhere. That architecture was treated as the realistic path for any deeper social or data-driven feature.
A Discord mention system emerged as the main idea
The strongest concept to come out of the session was a guild-oriented system that could connect multiple game characters to one Discord account. The proposed workflow would let players register a character-to-Discord identity, then have a bot parse guild or general chat for name-based mentions and translate them into actual Discord pings using numeric user IDs. That would effectively create a lightweight social layer across the game and Discord.
Text replacement inside chat looked feasible
Testing suggested that add-ons can detect or alter a player’s own typed text before it is sent, opening the door to automatic replacement of shorthand names with properly formatted Discord mention syntax. Once the numeric ID format was verified to work, the project moved from a novelty idea to a potentially functional utility for guild coordination, raid roles, and targeted alerts.
Security concerns remained central
The discussion drew a firm distinction between sandboxed add-ons and outside companion apps. While in-game code is tightly restricted, any standalone tool run on a PC can potentially read local files and expose secrets such as API tokens. That made cautious distribution and code trust a recurring concern, especially for any future app that would watch chat, update files, or communicate with Discord.
Project paused, but scope expanded
By the end, what started as a small AI-assisted coding experiment had grown into a larger systems concept involving Discord bots, add-on text handling, and external synchronization. The immediate build was deferred, but the idea was left on the table as a potentially rich project for future development.
CONCLUSION
The session underscored both the creative potential and hard technical boundaries of World of Warcraft add-ons. The most promising path forward is not a standalone add-on, but a hybrid system combining in-game tools, external software, and Discord automation.
Ask a question