This repository was archived by the owner on Oct 31, 2025. It is now read-only.
rebase #25
Open
rebase #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ngrim causing event cancellation (#24335)
Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
Referenced commit(s): 2e919af
Referenced commit(s): 7d8580a
…4350) Co-authored-by: sogladev <sogladev@users.noreply.github.com>
…lation instead of raycasting (#24330)
…ed after revive" (#24352)
Referenced commit(s): 2ff095b
…#24356) Co-authored-by: sudlud <sudlud@users.noreply.github.com> Co-authored-by: Benjamin Jackson <38561765+heyitsbench@users.noreply.github.com>
…ton and phasing for following quests (#24357) Co-authored-by: sudlud <sudlud@users.noreply.github.com>
Referenced commit(s): cb69e65
…y was on dead side for the whole fight (#24344)
Co-authored-by: sogladev <sogladev@gmail.com>
…s during Mounting Up (#24374)
Referenced commit(s): a4c2476
…affected by Ice Nova (#24354)
Co-authored-by: Degen <61268368+aradep@users.noreply.github.com>
…re hostile to your player's team. (#24100) Co-authored-by: Kitzunu <24550914+Kitzunu@users.noreply.github.com>
Co-authored-by: victor <vngodoyr@unap.cl>
Co-authored-by: Ariel Silva <ariel-@users.noreply.github.com>
Referenced commit(s): db2dafe
…es. (#24638) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Referenced commit(s): 50aa26b
Referenced commit(s): e5a3f5a
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Referenced commit(s): 2b563fc
Referenced commit(s): 7571ada
Referenced commit(s): d71c749
… spawned gameobjects (#24662) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com> Co-authored-by: zergtmn <zergtmn@users.noreply.github.com>
Referenced commit(s): 54d1454
Referenced commit(s): 5b278c7
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Referenced commit(s): 4c1e559
…in (#24582) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
…ication response. (#24569) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Referenced commit(s): 4822314
Co-authored-by: sudlud <sudlud@users.noreply.github.com>
Referenced commit(s): d597e45
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.