James Huston
ec14aa5545
HUGE MILESTONE: AI assistant now has direct real-time access to worldserver! Phase 1 - Database & Server Tools: - db_query, db_execute, db_tables, db_describe - server_info, player_list, gm_command, reload_scripts Phase 2 - Shared Data Bridge: - shared_data_read, shared_data_write, shared_data_keys - ElunaSharedData integration for cross-state communication - Full client MCP bidirectional data flow AMS Bridge Implementation: - Server: mcp_bridge.lua handles MCP_CHAT, MCP_CLIENT_LOG, MCP_GET_MESSAGES - Client: MCPBridge.lua with /mcpbridge commands - Data stored in ElunaSharedData, readable by MCP tools Key Learnings Documented: - nlohmann/json: Don't use value() with nullptr - TrinityCore: Use GetBoolDefault() not GetOption<T>() - AMS: Use AMS.Send (dot) not AMS:Send (colon) on client - Smallfolk: Never serialize functions Windsurf Integration: - Add to ~/.codeium/windsurf/mcp_config.json - AI gets direct access to all MCP tools - No more manual curl commands! This is SOOO FUCKING COOL!!!
TrinityCore (master)
- Build Status
- Introduction
- Requirements
- Install
- Reporting issues
- Submitting fixes
- Copyright
- Authors & Contributors
- Links
Build Status
| master | 3.3.5 | cata_classic |
|---|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
Introduction
TrinityCore is a MMORPG Framework based mostly in C++.
It is derived from MaNGOS, the Massive Network Game Object Server, and is based on the code of that project with extensive changes over time to optimize, improve and cleanup the codebase at the same time as improving the in-game mechanics and functionality.
It is completely open source; community involvement is highly encouraged.
If you wish to contribute ideas or code, please visit our site linked below or make pull requests to our Github repository.
For further information on the TrinityCore project, please visit our project website at TrinityCore.org.
Requirements
Software requirements are available in the wiki for Windows, Linux and macOS.
Install
Detailed installation guides are available in the wiki for Windows, Linux and macOS.
Reporting issues
Issues can be reported via the Github issue tracker.
Please take the time to review existing issues before submitting your own to prevent duplicates.
In addition, thoroughly read through the issue tracker guide to ensure your report contains the required information. Incorrect or poorly formed reports are wasteful and are subject to deletion.
Submitting fixes
C++ fixes are submitted as pull requests via Github. For more information on how to properly submit a pull request, read the how-to: maintain a remote fork. For SQL only fixes, open a ticket; if a bug report exists for the bug, post on an existing ticket.
Copyright
License: GPL 2.0
Read file COPYING.
Authors & Contributors
Read file AUTHORS.