Oculus: I Was Cheated Out of the Cache

#0 - June 29, 2010, 12:34 p.m.

Our LFD group was doing very well in Oculus until we got to Eregos. I had taken damage from the whelps so I dismounted as usual to mount up again with a 100% health drake. The problem was that my group pulled Eregos while I was trying to mount, and so I was unable to. I died quickly, and decided to run back to try and help heal. Somehow, my group managed to down Eregos with 4 Ruby drakes before I got back from the graveyard, and so while I got the emblems of frost for completing a heroic(which I could care less about) I did not get a chance to roll on loot or to grab the whole reason I am doing heroics every day: the Cache of the Ley Guardian. I REALLY want a Blue Drake, so missing a day of random Oculus farming is unacceptable to me. I was present when the group pulled the boss, and tried to get back to help, it's not like I was AFK badge farming. PLEASE give me the Cache! (Also, we had 4 Rubies and one Emerald, so I should have gotten Amber Void too, but really all I want is the damn cache).

Orlyia

#3 - June 29, 2010, 12:50 p.m.

Q u o t e:

If I get cheated out of my cache because I wanted to come back and help save the party from a potential wipe then screw this. That is totally lame.

Generally, it's unwise to release in most fights to try to run back. In some cases you are locked totally out and can't even zone back in.

You can ask via petition about this, but we'll simply have to look to see if you can be considered eligible for it.

On the plus side, that drake really isn't that rare. Run Occulus a few times and you should get him :)

Orlyia

#5 - June 29, 2010, 12:53 p.m.

Also, just an FYI on that particular dungeon/cache.

Make sure to loot it before everyone disbands, that can cause issues on it's own even if you are standing right there.

Orlyia

#13 - June 29, 2010, 1:38 p.m.

Q u o t e:

BALONEY!!! I have according to my statistics done this 34 times, and i'm good with saying 25+ is after the cache came out. Still no mount. 25 is not few. I hear it's a huge drop rate, but not for me.

You might want to consider totally resetting your UI and trying to run addon free.

While rare - it's been known to happen that certain addons/addon corruption can keep one from seeing quest items, rares, etc.

It may also just be the luck of the draw.

The insidious thing about misbehaving addons/UI issues is they usually manifest in what you CAN'T see.

To do a full reset UI, you will want to save your addons in another spot if you wish to preserve them.

Then rename/delete or move your WTF, Cache and Interface folders while WoW is shutdown. Reboot your system.

Note, if you are running Vista make sure your permissions are set so it does not undo your changes.

More detailed instructions for different operating systems, including Macs are here.

http://us.blizzard.com/support/article.xml?articleId=18761&searchQuery=reset%20UI&pageNumber=1

Orlyia

#15 - June 29, 2010, 1:44 p.m.

Q u o t e:

What kind of addons are causing this?

Addons of all kinds work with those three folders. It's not necessarily a specific one, or even kind - they can ALL misbehave from time to time, especially after patches where changes have been made to the game.

Getting new versions is wonderful, but if changes have already been made in any of those three files that conflict, that when odd stuff can happen - and why we recommend deleting those files, or renaming them.

Orlyia

#18 - June 29, 2010, 2:40 p.m.

That's one possibility.

I've seen it in the past.

It NEVER hurts to refresh things with updated addons and wipe out old folders - especially after a patch when the chances of a conflict or corruption are the greatest.

Orlyia

#20 - June 29, 2010, 2:43 p.m.

UI's are odd beasts.

Your UI is basically your interface with the world itself.

Some things get handled client side, some things get handled server side.

I'd not saying THIS particular issue is true in THIS particular case - but I've seen odder things happen, and resetting really can't hurt anything. If something is invisible to your UI, chances are, it's going to be treated like it doesn't exist.