Page 1 of 1

*seriously ticked*

Posted: Sun Feb 06, 2011 7:28 pm
by Shade
Went and got Ashtail on my little level 16 horde hunter. Then ran into the badlands to the closest stable master to drop her off, so I could run back into Loch Modan and get myself Gosh.

I stabled Ashtail, corpse ran back out of the Badlands-dying about 10 times on my way out.

I get out start trying to tame and guess what? I HAVE A BLOODY ACTIVE PET ALREADY.

I try dismiss pet, revive pet, mend pet, and am told I don't have a pet. Target a random mob and try to tame and.. You have an active pet already.

I've seen this bug on my other hunters too, if I stable my active pet and then step away from the stable master, I get a message saying I do not have any pets to summon...

Anyone seen this and know how to fix it aside from running all the way back to the bloody stable master again?

*cries*

I'm so sick of this dang glitch. Submitted a ticked, but that is going to take even longer. :x

Re: *seriously ticked*

Posted: Sun Feb 06, 2011 7:33 pm
by Miraga
Re-logging usually fixes it for me!

Re: *seriously ticked*

Posted: Sun Feb 06, 2011 7:34 pm
by Shade
I relogged, but still had the same problem. But I'll try it again once more.

This is seriously getting old though, is Bliz addressing this at all?

Re: *seriously ticked*

Posted: Sun Feb 06, 2011 7:36 pm
by Shade
Alright that fixed it thank you. I guess I had to stay logged out for a bit. I also logged into another toon and then out before getting back on Kit.

Grrr. This is irritating.

Re: *seriously ticked*

Posted: Sun Feb 06, 2011 7:55 pm
by Snowwalker
I've found also that playing around in the stable if you notice before you leave can fix it. Switch out a pet or move them around. I 'think' it may be triggered by skipped spots in your lineup, at least it seems to be when it happens to me.

Re: *seriously ticked*

Posted: Sun Feb 06, 2011 8:19 pm
by Arisia
Another thing I have found is that I have to make sure that my active pet is NOT the one I am stabling. Otherwise, I get that bug for the longest time. What I do is switch to another pet, dismiss it, and then stable the pet I wanted to put away. Weird, but it's worked for me; hope it helps!

Re: *seriously ticked*

Posted: Mon Feb 07, 2011 6:48 pm
by Foru21dr
I have just gotten use to dismissing the pet I have and swapping to another before I even open up the stable to change. It's become almost a ritual when I go to a stable master.

Re: *seriously ticked*

Posted: Mon Feb 07, 2011 6:50 pm
by Vephriel
Foru21dr wrote:I have just gotten use to dismissing the pet I have and swapping to another before I even open up the stable to change. It's become almost a ritual when I go to a stable master.
*nod* Same here. I've found that just always dismissing your active pet first prevents a lot of issues. Also if you're going to swap a pet out, swap them directly with the pet you're putting back in. If you stable your first slot pet without putting a new one in its spot it can glitch up. The stables are still rather finicky, but I suppose I've just adapted to their quirks. Hopefully Blizzard can fix them up a bit in the future.

Re: *seriously ticked*

Posted: Mon Feb 07, 2011 11:39 pm
by Cialbi
Vephriel wrote:
Foru21dr wrote:I have just gotten use to dismissing the pet I have and swapping to another before I even open up the stable to change. It's become almost a ritual when I go to a stable master.
*nod* Same here. I've found that just always dismissing your active pet first prevents a lot of issues. Also if you're going to swap a pet out, swap them directly with the pet you're putting back in. If you stable your first slot pet without putting a new one in its spot it can glitch up. The stables are still rather finicky, but I suppose I've just adapted to their quirks. Hopefully Blizzard can fix them up a bit in the future.
Ah, that explains why I rarely encounter this problem. Cialbi's stables are always filled to capacity or nearly so, which means I'm always swapping pets in the manner that Vephriel recommends.

Ah idea to counter this problem would be to fill all the empty spots in your stables with moths, all the same color, and each named Mothball. When you want to tame a new pet, you just release one of the moths. In fact, I think I'll take Shorelfon on a short vacation over in Azuremyst Isle sometime this week, and tame 10+ moths :P

Re: *seriously ticked*

Posted: Mon Feb 07, 2011 11:40 pm
by Mastodon
I've had this bug happen several times. It is rather annoying. i'm sure people have summited bug reports about it. Hopefully it gets fixed.

Re: *seriously ticked*

Posted: Tue Feb 08, 2011 1:23 am
by Pwncess
I've learned that you have to move a pet to the slot the stabled pet originally was in, and that seems to fix it. Hopefully this is in the hotfixes with the patch! Looks like Blizz has a lot of work to catch up on.

I've also had this weird fear that if I don't dismiss a pet before I put it in the stable or move it around, that the pet will end up missing or something. D:

Re: *seriously ticked*

Posted: Tue Feb 08, 2011 8:41 am
by GormanGhaste
Cialbi wrote:fill all the empty spots in your stables with moths, all the same color, and each named Mothball. When you want to tame a new pet, you just release one of the moths. In fact, I think I'll take Shorelfon on a short vacation over in Azuremyst Isle sometime this week, and tame 10+ moths :P
I will seriously have to do this with my baby allie alts :lol:

Re: *seriously ticked*

Posted: Tue Feb 08, 2011 9:02 am
by Sokujo
Pwncess wrote:I've learned that you have to move a pet to the slot the stabled pet originally was in, and that seems to fix it. Hopefully this is in the hotfixes with the patch! Looks like Blizz has a lot of work to catch up on.

I've also had this weird fear that if I don't dismiss a pet before I put it in the stable or move it around, that the pet will end up missing or something. D:
That's what I do also and I don't ever get the problem anymore.

1. Make sure to dismiss your active pet.
2. If you stable the pet you just dismissed ( your last active pet ) make sure to put a pet in that cage slot. ( I usually keep my cage full with all five pets, so this isn't an issue for me )

example: Let's say I'm rolling with 3 pets in my cage. They are taking up the first three slots. Let's say my active pet is in the first slot.

Now let's say I get to a Stablemaster and I dismiss my active pet. I then stable that pet from the first cage slot. I then select another pet from my stables and "instead of putting it directly in the first slot, I absentmindedly put it in my "fourth" slot which was empty the whole time.

Now I close down my stable window I fly away without calling a pet, I get to where I'm going to and I call my pet only to get the message, because my first slot, that I took my active pet out of is still empty. I then do a faceroll on my keyboard, curse the hunter gods and fly to the nearest Stablemaster to correct my error. :)

Hope that helps.

Re: *seriously ticked*

Posted: Tue Feb 08, 2011 9:49 am
by Worba
Hmm. I've heard of not being able to summon an active pet after visiting the stables (swapping the pets' slot position 1-2 times normally fixes that for me)... but to be barred from taming a new one... when you have 1+ active slots open? That's new to me. :shock:

Re: *seriously ticked*

Posted: Tue Feb 08, 2011 9:53 am
by Starzein
Worba wrote:Hmm. I've heard of not being able to summon an active pet after visiting the stables (swapping the pets' slot position 1-2 times normally fixes that for me)... but to be barred from taming a new one... when you have 1+ active slots open? That's new to me. :shock:

Cause of the hunters level...16 only one slot there