-
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
[TBC] Battle for Mount Hyjal 💀 #14
Comments
This is the data gathered from the waves that come AFTER the bases are evacuated. Why? Because those cosmetic waves have observably the same pathing as the normal waves. On second glance, it seems that pathing is deterministic, not random. Different charges leading to different patrols. More boring investigation needed. But I lean towards deterministic otherwise waves might've criss-crossed more on the initial charge. Alliance Base
Horde Base
Night Elf BaseFrom Mangos:
|
Peasant RPThe first one has details on the scripting. The rest will just be called "Gathering Point" and "Drop-Off Point"
|
Flying CreaturesIt's difficult gathering points for them because something will cause the Horde Base to despawn if left alone for too long, and there are no RP overrun event for flying creatures GargoylesThese are similar to the ground creatures, they'll choose between 3 paths on spawn. Then after they're done, they'll fly to the ground using 3 random paths. After that I believe they move randomly in a radius as I've not seen one get too far from the ground after that. Troll Camp SideSpawn Paths[0] [2] Points: X: 5789.4087 Y: -2929.6438 Z: 1667.9263 [4] [2] Points: X: 5761.9434 Y: -2873.9258 Z: 1644.555 [11] [2] Points: X: 5761.905 Y: -2817.4917 Z: 1623.4761 Attack Paths[0] Points: X: 5616.811 Y: -2800.8193 Z: 1526.867 [0] Points: X: 5570.3306 Y: -2878.28 Z: 1531.1624 [0] Points: X: 5579.018 Y: -2822.3298 Z: 1540.3124 Fortress SideSpawn Paths[1] [2] Points: X: 5464.7837 Y: -2556.5557 Z: 1579.4302 [2] [2] Points: X: 5484.6777 Y: -2545.9453 Z: 1564.7673 [5] [2] Points: X: 5442.2817 Y: -2569.3784 Z: 1595.6707 Attack Paths[0] Points: X: 5530.9634 Y: -2638.3645 Z: 1504.498 [0] Points: X: 5498.2217 Y: -2643.048 Z: 1506.3585 [0] Points: X: 5466.6343 Y: -2663.3906 Z: 1503.2643 Frost WyrmsThese paths are divided in 2 or 3 Troll CampPath 1[11] [2] Points: X: 5730.1025 Y: -2705.8052 Z: 1642.4415 Path 2[0] Points: X: 5553.9863 Y: -2745.591 Z: 1516.0532 So far I have not gathered Path 3 Fortress SidePath 1[3] [2] Points: X: 5452.1763 Y: -2562.7847 Z: 1586.864 Path 2[0] Points: X: 5488.03 Y: -2706.1182 Z: 1505.735 Path 3 (Patrol)[0] Points: X: 5526.811 Y: -2776.2566 Z: 1520.1216 |
BossesRage Winterchill & AnetheronFollows Charge and Patrol routes like trash. In my case, Charge 3 & Patrol 2 for Rage Winterchill and Charge 3 & Patrol 1 for Anetheron. Kaz'rogal & Azgalor
|
Overrun EventsBuilding NPC is like a serverside creature, doesn't have CreateObject packets Alliance Base Overrun RAW10.2.5.53262_2024-02-21 Battle for Mount Hyjal Attempt to get Waves CO2 + NE Pathing.pkt
Alliance Overrun Reduced
|
It seems simpler than I had imagined.
Some facts:
From what I observed so far, waves follow 1-3 paths towards the camp, once they reach it, they randomly choose between 1-3 patrol paths to walk.
They can only be looted once, so players can't abuse the system to farm whatever.
Spawn points can't be sniffed currently. Since they run on spawn we can't detect the original spawn point with accuracy, so they end up all over the place. One alternative is using the first waypoint as the spawn point, which makes them clump up somewhat, another is using CMangos' method. They use cpp spawns https://github.com/cmangos/mangos-tbc/blob/master/src/game/AI/ScriptDevAI/scripts/kalimdor/caverns_of_time/hyjal/hyjal.cpp#L44
As before and because it's my obsession as well, I believe Blizz uses a system that already has them "spawned". Why? Because I once broke this instance by triggering waves early and making them overlap. Only one group of mobs, however, kept spawning, which were the Infernals, because they are spawned by spells, and the others (abominations, ghouls) couldn't spawn because they already did so before.
CMangos' DB Rework: https://github.com/cmangos/tbc-db/blob/master/Updates/Instances/534_hyjal_summit.sql
Regardless, this will contain pathing, mainly. RP will be here as well.
IMPORTANT!
Most, if not all, wave spawns are CO1. Even if they run on spawn, that makes no sense as instance spawns in Shattered Halls, for example, are CO2, and they run as well. Or The Mechanar's bridge.
The text was updated successfully, but these errors were encountered: