Creature Handler Archive
Thread: You can't tame that bug is still around!
SioBabble, you should do Mask Scent, I did that and most of the time, I fail and they dont notice me, soo i suggest do mask scent for aggro creatures, and I tried logging out for 20 minutes and switch chars but nothing works
SOLUTION: A Fresh restart stopped the bugged, this might work for people who tried doing the tame macro or the logged off for 20 minutes or switch to a differ char on a different galaxy for 5 minutes
YEAH!
Message Edited by ExistenceDeath on 08-07-2005 06:11 PM
Message Edited by ExistenceDeath on 08-07-2005 06:26 PM
Another issue I found over the weekend is pets suddenly stop getting XP. I wondered around Dant leveling up 3 pets. After a half-hour or so, the pets stop getting XP. This happened to me twice. Logging out (for over 6 hours) did not help. The only thing that fixed it was changing planets. So now I have to have my datapad open constantly because I'm paranoid of grinding for a while only to find that my pets are getting nothing for the effort.
MTOCatalog2 wrote:
I experienced the "can't tame that" bug for the first time yesterday on Tat. When I left the area and attempted another tame it worked fine. I agree it must be some kind of server boundary issue.
Another issue I found over the weekend is pets suddenly stop getting XP. I wondered around Dant leveling up 3 pets. After a half-hour or so, the pets stop getting XP. This happened to me twice. Logging out (for over 6 hours) did not help. The only thing that fixed it was changing planets. So now I have to have my datapad open constantly because I'm paranoid of grinding for a while only to find that my pets are getting nothing for the effort.
Hardley wrote:
Ya' ... I killed the rest of the Worrts around the lair and the baby I could not tame ... then tapped the lair and kept killing the adults. Another baby spawned but I still got the "You can't tame that"! I've logged off but when I get back on, if I still have the problem I will try spamming the "/tame" and see if that works. Thanks for the suggestions.
Try aggroing the baby and then dropping agro that works many times
I found that if I just spam /tame over and over again, it will eventually take. So I made a looping macro that just does /tame and calls itself. Set myself on follow on the baby and click the macro. Eventually it works, takes at most 1-2 minutes. It's not perfect, but it's worked for me every time since Publish 21.
"retreating" AI. That bug will be fixed (along with a host of other,
related issues) around publish 22 or publish 23 (i.e. "When it's
ready").
In the meantime, we've put in a safety net here to "fix" characters who
get in this state. Previously you had to logout and wait for your
character to unload from the server, or wait for a server restart, in
order to clear the flag: now it will clean itself up automatically
within 60 seconds.
So, you might still see the "You can't tame that"-message, but it
should no longer be as severe a problem as it was before. Just give it
a minute and it'll clear-up.
JFreeman wrote:
This is a bug in the AI system resulting from an attempt to tame a "retreating" AI. That bug will be fixed (along with a host of other, related issues) around publish 22 or publish 23 (i.e. "When it's ready").
In the meantime, we've put in a safety net here to "fix" characters who get in this state. Previously you had to logout and wait for your character to unload from the server, or wait for a server restart, in order to clear the flag: now it will clean itself up automatically within 60 seconds.
So, you might still see the "You can't tame that"-message, but it should no longer be as severe a problem as it was before. Just give it a minute and it'll clear-up.
Yay!
JFreeman wrote:
This is a bug in the AI system resulting from an attempt to tame a "retreating" AI. That bug will be fixed (along with a host of other, related issues) around publish 22 or publish 23 (i.e. "When it's ready").
In the meantime, we've put in a safety net here to "fix" characters who get in this state. Previously you had to logout and wait for your character to unload from the server, or wait for a server restart, in order to clear the flag: now it will clean itself up automatically within 60 seconds.
So, you might still see the "You can't tame that"-message, but it should no longer be as severe a problem as it was before. Just give it a minute and it'll clear-up.
Thank you for the update. It is appreciated.
JFreeman wrote:
This is a bug in the AI system resulting from an attempt to tame a "retreating" AI. That bug will be fixed (along with a host of other, related issues) around publish 22 or publish 23 (i.e. "When it's ready").
In the meantime, we've put in a safety net here to "fix" characters who get in this state. Previously you had to logout and wait for your character to unload from the server, or wait for a server restart, in order to clear the flag: now it will clean itself up automatically within 60 seconds.
So, you might still see the "You can't tame that"-message, but it should no longer be as severe a problem as it was before. Just give it a minute and it'll clear-up.
May the force be with you.
- Omadda Szool
Kauri
JFreeman wrote:
This is a bug in the AI system resulting from an attempt to tame a "retreating" AI. That bug will be fixed (along with a host of other, related issues) around publish 22 or publish 23 (i.e. "When it's ready").
In the meantime, we've put in a safety net here to "fix" characters who get in this state. Previously you had to logout and wait for your character to unload from the server, or wait for a server restart, in order to clear the flag: now it will clean itself up automatically within 60 seconds.
So, you might still see the "You can't tame that"-message, but it should no longer be as severe a problem as it was before. Just give it a minute and it'll clear-up.
Thank you for the saftey net, Jeff, and the update.
But.
The situations where I have run into this involved me running up to a baby, attempting to tame, and just getting the message. The baby didn't retreat from me. It was just standing there. And in at least two of the cases, there were no other players around me who could have caused it to retreat. In fact, the the CRC case, I moved away to tame the female razor cat, then moved back to the CRC baby's position to test the distance, and the CRC baby had despawned and an adult took its place with the other two lairless CRCs
However, I'm positive that in at least one case I was near a server boundary, because later in the same area (this about 3KM E of Keren on Naboo, Ahazi server) I had a problem sending my pets in to attack an NPC. The pet (a dewback) would freeze right next to me (NPC about 30m away) in an attack stance, but there would be no attack. I had to give the pet the follow me command (thank goodness this works again) to break out of combat, then move right next to the NPC to give the attack command, and then combat would proceed.
Thanks for the info. We'll look into it.
SioBabble wrote:
I believe that there are multiple different bugs that cause this
state. I hope that you're correct and this is it, it will make
things much better, but I can't help but wonder if there are OTHER bugs
that cause the "you can't tame that" message to pop up.