mirror of
https://github.com/araxiaonline/TrinityCore.git
synced 2026-06-13 03:32:28 -04:00
James Huston
28dbbf095b
- ServerTools.cpp: Use ChatHandler::ParseCommands() as fallback for any unhandled GM command - ServerTools.cpp: Add leading dot to commands for ChatHandler compatibility - ServerTools.cpp: Add detailed header comments about GM command implementation pattern - AGENTS.md: Add code commenting guidelines section
1.8 KiB
1.8 KiB
Araxia Online Trinity Core Fork
Agent
This project is a fork of Trinity Core, a World of Warcraft server emulator.
Components
Status
We are currently in the process of getting the Eluna addon working with the master branch.
Documentation with status can be found in ELUNA_INTEGRATION_COMPLETE.md, GLOBAL_ELUNA_PLAN.md, and VALIDATION_SUMMARY.md. Please consult them before tacking any new tasks. All tasks should be tracked in these files.
Code Commenting Guidelines
ALWAYS add comments when modifying C++ code in this project.
Why?
- Context is lost between sessions
- Future AI assistants (and humans) need to understand design decisions
- Prevents reimplementing the same solutions repeatedly
- Code comments stay close to the implementation
What to Comment:
- File headers - Document the purpose and any important patterns used
- Non-obvious design decisions - Why did you choose this approach?
- Integration patterns - How does this code interact with TrinityCore systems?
- Gotchas and warnings - What mistakes should be avoided?
Example Pattern (MCP GM Commands):
// PREFER ChatHandler::ParseCommands() over reimplementing GM command logic
// This allows ANY existing command to work without custom code
ChatHandler handler(player->GetSession());
handler.ParseCommands(command);
Key Files with Important Comments:
src/araxiaonline/mcp/ServerTools.cpp- GM command implementation patternsrc/araxiaonline/mcp/AraxiaMCPServer.cpp- MCP server architecture