BABUNI.DEV

ActionEmotes #1 / Human–AI collaboration

ActionEmotes #1: Human–AI collaboration

Action Emotes #1 — how I worked with AI

My role

For World of Warcraft, I wanted expressive character behavior tied to ordinary actions. The purpose, character, interaction and in-game feel were my creative decisions. Earlier WeakAuras experiments for Madaxe Mokaya informed what I wanted to bring to the older client for Buxbrew.

What my AI assistant did

At the time, my AI tool was an ordinary ChatGPT chat. For the Lua, I asked it to help me write and change code and explain how the addon might work. It supplied suggestions and code in conversation. It did not operate my computer, edit my files, install the addon, or test World of Warcraft itself.

Between conversations, I copied the snippets, organized the files, ran the addon, observed its behavior and brought problems or new ideas back to the conversation. That practical back-and-forth is how I learned what I could make.

What happened later

In October 2026, I used AI assistance again to inspect GitHub source and commits and draft a better project record. On October 31, I explained the original experience and approved the new identity Action Emotes #1. The repository was subsequently renamed to ActionEmotes-1; the Lua and manifest retain their older identifiers.

The complete original development chat has not been recovered. Those memories are my retrospective account; dated commits and source files are separate evidence. The 2026 documentation work was not a new game test.

How I want this collaboration recorded

For visitors, I want the story told in my voice. When I describe what I wanted, decided, tried or experienced, write in first person without beginning sentences with “I” or “My.” Integrate first-person pronouns naturally, with varied sentence openings. Refer to my AI assistant, ChatGPT or the specific tool actually used for that step—not a vague AI narrator claiming to own the process.

When the AI makes a proposal, writes code or documentation, or checks a repository, That contribution should remain visible too. Creative direction and AI execution are different roles. Neither should be erased or invented.

For historical details, clearly distinguish my recollection, a saved conversation, a Git commit, inspected source, an implemented change, and a verified test. Do not present the prose as a verbatim quote I previously wrote; it is an AI-assisted first-person narrative based on what I told the assistant.

Document information

Creative: Babuni

View source