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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 [Bug Report] Missing In Action quest - Corporal Keeshan NPC is missing a waypoint path #3703

Open
soniquete0 opened this issue Apr 20, 2024 · 8 comments
Labels
Info: Needs Replication Issue needs replication before further action.

Comments

@soniquete0
Copy link

Bug Details

Corporal Keeshan in the Missing in Action quest is missing a waypoint path. It has already been implemented to TBC in this commit ( cmangos/tbc-db@df201dd ) but didn't make it's way to vanilla (and likely WotLK as well).

Steps to Reproduce

  1. Start the quest
  2. Watch the NPC not doing anything

Expected behavior

The NPC should move.

Suggested Workaround

No response

Crash Log

No response

Core SHA1 Commit Hash

x

Database SHA1 Commit Hash

x

Operating System

Win 10

Client Version

1.12.1 (Classic)

@soniquete0 soniquete0 added the Info: Needs Replication Issue needs replication before further action. label Apr 20, 2024
@al3xc1985
Copy link

I believe when kw will do his periodic backports, will do this one 2

@soniquete0
Copy link
Author

Is there a list of these?

@al3xc1985
Copy link

well, KW has them noted down

@soniquete0
Copy link
Author

So not publicly available.

@al3xc1985
Copy link

why closed it?

@soniquete0
Copy link
Author

I don't see a reason to have an open issue for something that is in the works. Don't know your process. I can reopen it if you want.

@al3xc1985
Copy link

So let me explain, KW like all the other devs have their part of this project that they work on.
From time to time, when KW decide and have time, he is backporting all stuff from a repo to all others accordingly to their researche.

It can sometimes to forget a certain update to backport.
In this case an issue report is made like you did, and wait patiently until the moment comes.

It is our reposnsability to give a hand and see from time to time what updates are in the repo that we observe, and if a dev forget to close our bug report, close it ourselfs.

Bug reports are welcome, that is why we are a community to help each others and wait. Our devs are like big brothers. Need to help them as much as we can.

So yes, reopen it and wait till it;s backported

and You did a gret job to link the link missing

@soniquete0 soniquete0 reopened this Apr 28, 2024
@soniquete0
Copy link
Author

Alright, makes sense. Thanks for the info. Reopened the issue. I'll report more in case I spot them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Info: Needs Replication Issue needs replication before further action.
Projects
None yet
Development

No branches or pull requests

2 participants