Honeyback Hive

So the Honeyback Hive doesn’t count toward 100 Exalted Reps, however it should. If you wanted it not to count, you should have just made a friendship rep instead of an actual Exalted Faction.

Even if it is Alliance only, Horde can still do it for it to count, either by making a Alliance race or something else.

Also, the mount doesn’t count toward mount count on Alliance.

Just a few more glitches in the glitch ointment that are the activities and rewards surrounding the honeyback hive.

  1. mount not usable on horde
  2. harvester events randomly not spawning fresh jelly deposits at the end
  3. fresh jelly deposits randomly not interactable even when they do spawn

It’s like noone from QA took one look at this content before it was pushed to live. And it still hasn’t been fixed three weeks later.

That is not a glitch

Yes it is.

The mount is intended to be an alliance only mount

That does not make it a glitch. Sorry but your feelings are not bugs

Neither does your trolling and failure to understand why faction locking one side’s mounts while allowing them to ride the other side’s mounts is a bug.

Except it isn’t.

Just because it bugs you, doesn’t make it a programming bug.

I wonder why you keep making these threads about something that bugs you but it is not a programming bug. This forum is for programming bugs, not features in the game that get you triggered.

The bee mount is locked to the alliance. It was like that since the PTR and it carried over to live.

Link me the blue post where they clarify the status of the faction lock as intentional and not a bug. I’ll spare you the time - there isn’t one. They’ve been evasive and equivocal about this in every post they’ve talked about this mount. That you are under the delusion a mount that doesn’t have any strong faction identity or faction insignia on it is somehow intentionally faction locked is laughable.

Again, this is not a programming bug. Horde players have known this since the PTR. Blizzard did not change it during the PTR and they haven’t changed it now.

Sorry, but just because something triggers you, doesn’t make it a programming bug.

Typical backsplainin’

We all know no bugs or glitches or typos or data entry SNAFUs that are reported on the PTR ever make it to live, right? Because blorz is so good at fixing and catching everything players report.

Do you have any evidence that supports this being a bug other than your own feelings?

Because if it was a bug, blizzard would’ve changed it by now.

Your feelings are not programming bugs.

No they wouldn’t have. There’s bugs that have festered on live for years without being fixed.

Neither are your feelings intentional design choices. Unlike you, however, I have apples-to-apples precedent to support my position. All you have is “this is how things are and this doesn’t effect me so it’s not a bug because blorz is perfect.”

Can you provide some examples that are not your feelings?

You have yet to provide any evidence that shows that this is a bug other than “me do not like it, me angry, me call it bug because it bugs me”