UI Improvements: - Added Raw tab showing formatted JSON of server NPC data - Added GM toggle button with green active state indicator - Added 3D model zoom (scroll wheel) and rotation (click-drag) - Green active tab styling for all tab buttons (left/right panels) - Refresh button now always fetches fresh data from server - Waypoint button properly reflects state when re-targeting NPC Waypoint System Fixes: - Fixed stale visualization state after Clear All or Eluna reload - VisualizePath now validates tracked creatures exist before skipping - DevisualizePath properly cleans up maps even if creatures gone - Added ClearAllVisualizations C++ method for proper state cleanup - Added player:ClearAllWaypointVisualizations() Lua binding - Increased Smallfolk deserialization limit to 100KB for large NPC data C++ Changes (requires rebuild): - WaypointManager: Self-healing visualization state - WaypointManager: ClearAllVisualizations and IsPathVisualized methods - PlayerMethods: ClearAllWaypointVisualizations binding Known Issues: - Paths tab shift+click removal not working (buttons need rework)
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.