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

🦂 [Bug]Diremaul #2679

Open
ShiyoKozuki opened this issue Jun 21, 2024 · 4 comments
Open

🦂 [Bug]Diremaul #2679

ShiyoKozuki opened this issue Jun 21, 2024 · 4 comments
Labels
bug Something isn't working dungeon

Comments

@ShiyoKozuki
Copy link
Contributor

🦂 Bug report - Dungeon

Captain Kromcrush gives quest before you finish tribute run
Knot Thimblejack's Cache did not spawn after freeing him
Guard Slip'kik does not give buff after tribute run

Expected behavior

https://www.wowhead.com/classic/guide/dire-maul-north-dungeon-strategy-wow-classic
https://www.icy-veins.com/wow-classic/dire-maul-north-dungeon-guide
captain kromcrush shouldn't quest before you finish tribute run
Knot Thimblejack's Cache should spawn after freeing him
Guard Slip'kik should give buff after tribute run
image
image
image

Version & Environment

Client Version: 1.12.1

Commit Hash:
https://github.com/ShiyoKozuki/core

Don't know what this means but this is my repo

@ShiyoKozuki ShiyoKozuki added bug Something isn't working dungeon labels Jun 21, 2024
@mserajnik
Copy link
Contributor

mserajnik commented Jun 22, 2024

Don't know what this means but this is my repo

Commit hash means that you would specify the commit that you were at when you built the server, e.g., 7836306.

This is done so that it can be determined if a bug was fixed (or maybe also introduced) with a newer commit than what you are using (also going forward in time, so it’s useful to state the explicit commit instead of just “latest” because it won’t be the latest in half a year anymore).

You’ll generally not get support here though if you are building the server from a different repository than this official one (from what I’ve observed), so you should verify that the bug also exists when building the server from the latest commit in this repository.

@ShiyoKozuki
Copy link
Contributor Author

Don't know what this means but this is my repo

Commit hash means that you would specify the commit that you were at when you built the server, e.g., 7836306.

This is done so that it can be determined if a bug was fixed (or maybe also introduced) with a newer commit than what you are using (also going forward in time, so it’s useful to state the explicit commit instead of just “latest” because it won’t be the latest in half a year anymore).

You’ll generally not get support here though if you are building the server from a different repository than this official one (from what I’ve observed), so you should verify that the bug also exists when building the server from the latest commit in this repository.

So this?
ShiyoKozuki@a44cbd6

I build off the core besides some partybot/battlebot ai ive changed and 2 prs(from the official repo)

@mserajnik
Copy link
Contributor

Yeah, you reference a specific commit like that.

And I think it’s more of a general stance that you won’t get support for code from other repos, no matter how large or small the changes compared to the official repo are. So it would still be best to just test if the issue also occurs here, even if the changes in your repo have nothing to do with the issue you are experiencing. But that’s not up to me, I’m just stating what I observed thus far. 🙂

Also, I think two of your issues stated have already been reported, by the way: #2249

@ratkosrb
Copy link
Contributor

You should not report things before having tested them on clean vmangos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dungeon
Projects
None yet
Development

No branches or pull requests

3 participants