ROARRunlimited — human–AI collaboration and attribution
What the available records establish
The original README, ROARRunlimited.lua, TOC, MIT license and dated Git changes establish the implementation and the visible evolution from physical-slot-indexed settings to numbered instances. They do not contain a complete human–AI conversation indicating who individually proposed every API, command or phrase.
The creator's original “action bar into a war drum” metaphor belongs to the project record. Do not attribute this direction to an assistant simply because an assistant is documenting it later.
AI contribution in the 2026-10-26 documentation pass
The assistant:
- Read the live repository source, manifest, README, license and earlier short docs.
- Examined original commits that introduced multi-slot settings, per-instance configuration and v1.1 changes.
- Reconstructed implementation history without fabricating approvals.
- Flagged the actual TOC/Lua case mismatch, persisted session-relative cooldown timestamps, and lazy-load/logout risk.
- Expanded the README and documentation structure in Markdown only.
These are research, technical interpretation and writing/editing contributions. No addon source or license was altered, no gameplay functionality was implemented, and no World of Warcraft client was run.
Future development record
For every substantial implementation, record the human request and rationale, AI options and their limitations, explicit creator decisions, code/document paths and Git references, tests actually run and their observations, and unverified concerns. Mark proposals as proposals; mark retrospective interpretation as inference.
Do not publish sensitive private conversations, credentials or unapproved personal information in portfolio documents.
Document information
Human project creator and decision-maker: Babuni.dev.