[IDEA] Module Patch

[manstfu]

Module-Specific Patch System for AzerothCore

This feature allows each module to contain its own patches that apply directly to the core during compilation. This setup ensures that module-specific patches integrate seamlessly while maintaining modularity and ease of maintenance.

Key Features:

· Patch Generation: Patches can be generated using git diff or by directly overwriting original files with customized versions.
· SQL Management: SQL files remain unchanged and must be applied manually if any database modifications are needed.
· Custom Hooks: Extend beyond core-defined hooks by creating your own custom hooks. This allows you to inject or override functionality without modifying the core directly, enabling more flexible and dynamic module development.

Module Structure Example:

modules/
├── YourModule/
│   ├── CMakeLists.txt
│   ├── src/
│   │   └── YourModule.cpp
│   └── patches/
│       ├── src/
│       │   ├── server/
│       │   │   ├── game/
│       │   │   │   └── Entities/
│       │   │   │       └── Player.cpp   // Replaces Player.cpp function

Benefits of This Approach:

· Modularity: Each module independently manages its own patches, reducing complexity and potential conflicts.
· Maintainability: There is no need to modify core files directly, ensuring easier updates and cleaner code.
· Flexibility: Patches can be added or removed simply by updating the module's patch folder, providing adaptability without affecting the core.

This system provides a robust way to customize AzerothCore while keeping modifications organized and aligned with best practices.