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

Pyrewood Ambush spawning in extra set of mobs #21583

Open
Apathyxia opened this issue Feb 22, 2025 · 2 comments
Open

Pyrewood Ambush spawning in extra set of mobs #21583

Apathyxia opened this issue Feb 22, 2025 · 2 comments

Comments

@Apathyxia
Copy link

Triager notes (By me and @Xolo-fath):

.go c id 2058 for easy travel to the NPC.

Wave 1: 1 Councilman Smithers
Wave 2: 1 Councilman Tatcher,1 Councilman Hendricks
Wave 3: 1 Councilman Cooper , 1 Councilman Hartin, 1 Councilman Wilhelm
Wave 4: 1 Councilman Brunswick, 1 Councilman Morrison, 2 Councilman Higarth

On the Wave 4, there is an extra Councilman Higarth. There should only be 1.

Some of the councilmen occasionally turn into Moonrage Sentries. Xolo found out that the mobs may also evade, turn into Moonrage Sentries and despawn. This is best observed by standing still at the back of the room after starting the event.

The steps to reproduce stated on the report are indeed correct, but not applicable to CC PTR or Local AC. It only works on CC live. CC PTR and Local AC both behave differently.

On CC live: If there has been duplicate waves, the next person picking up the quest will get it instantly completed. Duplication only happens here.

On CC PTR: No duplicate waves happened. Only the extra councilman on wave 4 and the councilmen turning into moonrage sentries (and despawning).

On Local AC: I was not able to make the event even spawn.

Original CC issue: chromiecraft/chromiecraft#7875

Current Behaviour

So this quest is spawning in extra waves of mobs that is not supposed to happen. Just died to this bug on my HC shaman. What is happening is that after a certain amount of time, the "next" wave of mobs are supposed to spawn, but it spawns in the same wave. As well as, the waves seem to be on a timer, cause when the "next" wave is supposed to spawn, the mobs change into regular sentries. As well as, as soon as you kill the wave of mobs, it will spawn in the same wave of mobs. Essentially, you have to beat 8 waves of mobs. Totaling in 18 mobs that you have to almost solo, instead of the usual 9 that is supposed to spawn. Quite annoying to die to a bugged quest.

Image
Image
Image
Image
Image
Image
Image
Image

Expected Blizzlike Behaviour

This quest has 4 waves in total. The first wave being only one mob. The second wave has 2 mobs that spawn. The third wave has 3 mobs that spawn. Then the final wave spawns in 3 mobs. Then the quest is completed

Wowhead Comment with Link;
https://www.wowhead.com/wotlk/quest=452/pyrewood-ambush
Four waves, easily soloable with a 16 lock.

1st wave - 1 guy
2nd wave - 2 guys
3rd wave - 3 guys
4th wave - 3 guys

Source

Youtube video showing how this is supposed to work on a 3.3.5 wrath client.

https://www.youtube.com/watch?v=G9rwAhgNeMA

Steps to reproduce the problem

  1. Accept the quest
  2. Wait for the first wave/mob to spawn
  3. Either kill the mob or wait around 10 seconds for the next wave
  4. "Next" wave will spawn the exact same mob
  5. Next wave will spawn, 2 mobs this time. Repeat step 3
  6. "Next" wave will spawn the exact same 2 mobs
  7. Next wave will spawn, 3 mobs this time. Repeat step 3
  8. "Next" wave will spawn the exact same 3 mobs
  9. Next wave will spawn, 3 mobs this time. Repeat step 3
  10. "Next" wave will spawn the exact same 3 mobs

Extra Notes

No response

AC rev. hash/commit

chromiecraft@ee69a56

Operating system

Ubuntu 22.04

Modules

Customizations

None

Server

ChromieCraft

@Nyeriah
Copy link
Member

Nyeriah commented Feb 22, 2025

Other than the duplicate mob, I can't reproduce any of this, either on CC or local server

@Nyeriah
Copy link
Member

Nyeriah commented Feb 22, 2025

On spawn, mobs choose either the player who had picked up the quest or the quest npc to attack
Next wave comes 6 seconds after the last mob dies, no matter what
What I think could have happened is some player taking the quest and dying, or two players taking the quest at the same time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants