Skip to content
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

Molten Core: Lucifron Patrol Path is WRONG #15663

Closed
wrathix opened this issue Oct 4, 2015 · 1 comment
Closed

Molten Core: Lucifron Patrol Path is WRONG #15663

wrathix opened this issue Oct 4, 2015 · 1 comment

Comments

@wrathix
Copy link

wrathix commented Oct 4, 2015

While Going through MC today, I notice that Lucifron is patrolling all the way to the start of 'Magmadar Cavern' Which is way too far! He should turn around and go back towards Magmadar about when he reaches the closest corehoundpack.

A video on youtube shows his correct patrol path from live. This is definitely the correct path in the vid.
https://www.youtube.com/watch?v=uhkXEcXb4eQ

Where he currently patrols is where a whole 40 man guild would prepare themselves back in the day at the start of Magmadar cavern. This would be impossible to prepare in this location right now, you'll pull him even if you are hugging the back wall without a doubt!

@TrinityCoreBot
Copy link

This issue is not considered valid because of the following reasons:

  • No proper commit hash (revision)

Please read http://bit.ly/tc-issuetracker-and-you . Thanks.

@TrinityCoreBot TrinityCoreBot added the Invalid-IncompleteData/OrNotTrinityCore Reporter deleted parts or all template or he is using a 3rd party unsupported core. label Oct 4, 2015
@wrathix wrathix closed this as completed Oct 4, 2015
@Aokromes Aokromes removed the Invalid-IncompleteData/OrNotTrinityCore Reporter deleted parts or all template or he is using a 3rd party unsupported core. label Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants