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

Quest: Stinky's Escape. Issue: Stinky names your character instead of attacking enemy #21242

Open
horsetuna opened this issue Jan 22, 2025 · 4 comments
Labels
Confirmed Needs sniff The issue/PR needs sniff data to be corrected.

Comments

@horsetuna
Copy link

Current Behaviour

I accepted Stinky's Escape and we got attacked by a Raptor. However when speaking, the character says: Look out! The Raviaries attacks!

(Raviaries is my character's name)

Image

Expected Blizzlike Behaviour

It should say 'The raptor attacks' I'm pretty sure.

Source

No response

Steps to reproduce the problem

Accept quest.
Get attacked by Raptor. (uncertain if it does this with other targets. He didnt say anything after that)

Extra Notes

No response

AC rev. hash/commit

I have completed the quest and moved on. I am uncertain if this is needed

Operating system

Windows 11

Custom changes or Modules

No response

@TheSCREWEDSoftware
Copy link
Contributor

Future reference AC rev. hash/commit referes to the .server debug output in your case you've downloaded manully so it will always be invalid. Next time try to tell us the day and hour (alongside the timezone) so we can figure out what Version of AzerothCore you're running.

I can confirm this issue the Quest NPC is supposed to target and say the creature attacking it name not the player.

(haven't check but he doesnt seem to have SAI). But still needs sniff to make sure the waypoints and quotes are played in the correct order.

@TheSCREWEDSoftware TheSCREWEDSoftware added the Needs sniff The issue/PR needs sniff data to be corrected. label Jan 22, 2025
@horsetuna
Copy link
Author

Apologies. I will try to do so next time! It was around 3 pm january 22nd 2025 in Eastern Standard Time Zone.

(I am uncertain what the future reference is in this context though sorry).

@TheSCREWEDSoftware
Copy link
Contributor

The data below is for anyone else looking at the issue. When i refered to the date and time i was refering when you downloaded the revision (version of the core) not when issue happened

@horsetuna
Copy link
Author

Sorry I will remember to include that next time I promise! thank you! newbie here :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Confirmed Needs sniff The issue/PR needs sniff data to be corrected.
Projects
None yet
Development

No branches or pull requests

2 participants