La priorite de cible sur le dirigeant utilisait searchRange * 2, donc la portee d engagement courante. Abaisser siege_engage_range pour reduire l attrition retrecissait du meme coup le rayon a partir duquel le dirigeant devient la cible prioritaire, exactement quand on cherchait a le rendre atteignable. Les deux valeurs sont desormais independantes, nouvelle cle siege_boss_engage_range (40 yards par defaut, borne a 10 - 60). Portee d engagement abaissee a 10 yards dans le fichier de configuration distribue : mesures a 50 bots sur la route relevee en jeu, avec siege_boss_engage_range a 40. engage 18 waypoint 29/30, bot le plus proche a 94 yards engage 10, boss couple waypoint 29/30, bot le plus proche a 47 yards engage 10, boss a 40 waypoint 30/30, bot le plus proche a 3 yards La horde franchit donc desormais la totalite de la route et atteint le dirigeant au contact. Reste ouvert : Anduin ne perd toujours pas un point de vie, y compris avec un bot mort a 3 yards de lui. L hypothese d une protection par la faction est ecartee par deux essais avec sa faction forcee a 12, dont un ou la horde a franchi les 30 waypoints. Rien dans creature_template ne l explique non plus : ni masque d immunite, ni aura, ni script, et son unit_flags 0x8000 ne figure pas parmi les drapeaux bloquants de Unit::_IsValidAttackTarget. Le diagnostic suivant demande d instrumenter la selection de cible cote bot. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DestinyCore
🚀 Build Status
| Windows | GCC | Clang |
|---|---|---|
📖 Introduction
DestinyCore is a modern, modular MMORPG server framework written in C++ that supports multiple platforms (Windows, Linux, macOS) and builds cleanly with GCC, Clang, and MSVC.
It is designed to be lightweight, scalable, and extensible, providing developers and server administrators with a stable foundation for World of Warcraft® (Legion 7.3.5) and beyond.
Key goals of DestinyCore:
- ⚡ Modern C++ design (C++20+)
- 🔌 Modular architecture (authserver, worldserver, shared libs)
- 🤖 Integrated PlayerBots system
- 🌍 Multi-database support (auth, characters, world)
- 🛠️ Easy build system (CMake + GitHub Actions CI)
- 🎮 MMO-ready networking with scalability in mind
🛠️ Requirements
DestinyCore depends on modern development tools and libraries:
- CMake 3.31+
- Boost 1.84.0
- MySQL 8.0
- OpenSSL 3.x
- GCC / Clang / MSVC (Visual Studio 2022 recommended)
📦 Installation
-
Clone the repository:
git clone https://github.com/slash-design/DestinyCore.git cd DestinyCore -
Create a build directory:
cmake -S . -B build -DTOOLS=ON cmake --build build -
Configure your databases (
auth,characters,world) and import the SQL structures provided in/sql/base. -
Start the servers:
./bin/worldserver ./bin/bnetserver
🤝 Contributing
We welcome all contributions!
Whether you’re fixing a bug, improving documentation, or adding new features — PRs are always appreciated.
- Fork the repo
- Create a feature branch
- Submit a pull request
🐛 Reporting Issues
Issues can be reported directly via the GitHub Issue Tracker.
Before creating a new one, please check for existing reports to avoid duplicates.
📜 License
This project is licensed under GPL v2.0.
See the LICENSE file for details.
🌐 Links
⭐ If you like DestinyCore, consider giving the project a star on GitHub!