-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
fix(Scripts/StormPeaks): Rewrite Time-Lost Proto Drake #24497
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
base: master
Are you sure you want to change the base?
Conversation
|
Should we make the timers and chances worldserver conf values? We have manabonk in the config. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR rewrites the Time-Lost Proto Drake / Vyragosa behavior and associated world data to better match sniffed paths and spawn behavior in the Storm Peaks.
Changes:
- Refactors
npc_time_lost_proto_drakefromnpc_escortAI+script_waypointto aScriptedAIusing DB-driven waypoint paths and modern scheduling helpers. - Adjusts
creature_templateandcreature_model_infofor Vyragosa and Time-Lost, and replaces old script waypoints with four sniff-based waypoint paths inwaypoint_data. - Rebuilds creature spawns, pools, and addons for Time-Lost/Vyragosa to support four separate path spawns at a reduced Time-Lost chance.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/server/scripts/Northrend/zone_storm_peaks.cpp | Updates Time-Lost Proto Drake AI to use ScriptedAI, randomizes entry between Time-Lost and Vyragosa, sets flying behavior, and adds new spell timer scheduling. |
| data/sql/updates/pending_db_world/rev_1769117901544014100.sql | Tweaks templates and model info, defines four new waypoint paths, recreates creature spawns and pool configuration, and wires up creature_addon path bindings. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
With this changes does they still choose a random waypoint to spawn? |
No. Before it was a single path with 250 points. Now it has 4 different paths, chosen by the pooling system with equal chance to each path. |
|
I don't know the blizz way, but I assume they tried to make it less predicable as possible? Any of sniffs does any of the dragons spawn in the same place or was always different places? asking because how bad does it sound to have it after picking up 1 of 4 possible routes, to pick a random waypoint within that route + the invisible peridioc (this in theorry should make the dragons fully impredicable |
|
I doubt I caught every consecutive spawn, but in some cases, I'd get the same path in two consecutive days. If predictability is important then it's no worry as the range to turn visible is huge and they do continue pathing while invisible. |
Videos With Blizz Like Spawn InformationBelow are videos that look like there is proof for where these rare spawns are. Video 1loud warning Video 2beautiful music warning Video 3Better Explanation With Some Fluff Important Times in the videohttps://www.youtube.com/watch?v=ZtIJ-Z7MK_0&t=32s |
Changes Proposed:
This PR proposes changes to:
Adds 4 different spawns and paths from sniffed data
Decreased chances of spawning as Time-Lost from 25% to 10% (provided in linked issue, from our data we've seen it 1 in 12 times)
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.
Initial cleanup of the creature script, but it doesn't know up-to-date code standards so I rewrote it anyways.
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.