fix(Scripts/TempestKeep): Add Teleport Position to Astromancer Solarian and Threat Reset#24622
Merged
Gultask merged 3 commits intoazerothcore:masterfrom Feb 6, 2026
Merged
fix(Scripts/TempestKeep): Add Teleport Position to Astromancer Solarian and Threat Reset#24622Gultask merged 3 commits intoazerothcore:masterfrom
Gultask merged 3 commits intoazerothcore:masterfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes the Astromancer Solarian encounter in The Eye (Tempest Keep) by implementing a teleport to the boss's start position during the spotlight phase and adding a threat reset after the teleport sequence completes. The fix addresses issue #6958 from chromiecraft and is based on sniff data from build 50791.
Changes:
- Implements boss teleport to start position during spotlight phase using spell 33244
- Adds threat reset when boss returns to combat after spotlight phase
- Adds database entry for teleport spell target position
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/server/scripts/Outland/TempestKeep/Eye/boss_astromancer.cpp | Adds "Serverside" comment to spell, implements teleport cast at phase start, and adds threat clear before returning to aggressive state |
| data/sql/updates/pending_db_world/rev_1770249033416011200.sql | Defines spell target position for teleport spell (Map 550, coordinates matching START_POSITION constants) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
sudlud
approved these changes
Feb 6, 2026
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
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:
AI-assisted Pull Requests
Important
While the use of AI tools when preparing pull requests is not prohibited, contributors must clearly disclose when such tools have been used and specify the model involved.
Contributors are also expected to fully understand the changes they are submitting and must be able to explain and justify those changes when requested by maintainers.
Issues Addressed:
SOURCE:
The changes have been validated through:
Build 50791
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.