forked from azerothcore/azerothcore-wotlk
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npcbot #30
Merged
AthenaSui
merged 24 commits into
AthenaSui:Az_trickerer_npcbot
from
trickerer:npcbots_3.3.5
Jul 30, 2024
Merged
npcbot #30
AthenaSui
merged 24 commits into
AthenaSui:Az_trickerer_npcbot
from
trickerer:npcbots_3.3.5
Jul 30, 2024
Conversation
This file contains 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
* fix(DB/Creature): Ormus the Penitent * Update rev_1721400804205047100.sql
Referenced commit(s): 139e6d6
* Config - Deprecated for 3 years * ChatCommand - Deprecated for 2 years * getLevel() - Deprecated for 2 years * SendGlobalText - Deprecated for 8 years +
* fix(CI): tools * Update tools_build.yml * I dont think this is neccessary. Let's see if CI agrees with me
* daze * bruh * bruhx2
azerothcore#19455) fix(DB/Spells): Mortal Wound and Sunder Armor stack from different casters
Referenced commit(s): 1e6d0e7
…19044) * add Apprentice Morlann talk * Modify emoticons * fix error * Update rev_1718007800531434000.sql * Update data/sql/updates/pending_db_world/rev_1718007800531434000.sql --------- Co-authored-by: Gultask <[email protected]>
Referenced commit(s): c68f234
Referenced commit(s): dd8bc51
* refactor(Core/Chat): PSendSysMessage to `fmt`
Referenced commit(s): 3fbded8
remove unneeded script
…nde at first (azerothcore#19467) Update boss_archimonde.cpp
…rothcore#19469) * Init. Co-Authored-By: Tereneckla <[email protected]> * Simplify code, add comment. * Adjust scenario in which distance fails at all ranges. * Remove unused variable. * Account for deviation with distance check. Co-Authored-By: Tereneckla <[email protected]> * f Co-authored-by: Kitzunu <[email protected]> * Rewrite with initial teleport. * Whitespace? * Update function type. * Drop Doomfire spawn timer. Verified with le sniff. Teehee. --------- Co-authored-by: Tereneckla <[email protected]> Co-authored-by: Kitzunu <[email protected]>
Referenced commit(s): bc23a7a
AthenaSui
pushed a commit
that referenced
this pull request
Jan 4, 2025
Add a new statement to update character online by guid
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.