Enchanter Pet won't "go away"

[AndMetal]

Originally Posted by Angelox

all casters had to develop AA's as to be able to invis with the pet, if not, the pet would poof on invis.

I had to double check, but I'm not seeing any AAs that allow you to invis with the pet, so I'm not really sure what you might be referring to.

I distinctly remember soloing on my shaman in one of the Luclin zones (Katta I think?) at the guards by the bank. Because killing them lowers your faction, I would already have a pet summoned & buffed (usually from someone in the Nexus), zone in, invis to the camp spot, then summon my pet to me. I'm not sure, but I believe the pet could still aggro mobs, which is why I usually did it that way (but I could be wrong about that). However, I know previously, you couldn't invis with a pet summoned & they also wouldn't zone (until after beastlords came around).

One caveat, though, was they would poof after being logged for somewhere between 10 & 30 minutes (similar to summoned items). As far as I know, that was mainly to prevent having to resummon your pet if you went LD (which was always a PITA during raids).

For reference, I stopped playing EQ Live sometime in 2004 or early 2005.

Originally Posted by Angelox

Also, all casters had to earn AA's that would allow them to "suspend" the pet so it would not get lost on zoning or camp out.

This didn't have any affect on zoning, it just let you "save" your pet to resummon later (although I never used it myself personally). The main idea with those, as I understand it, was so you didn't have to rebuff or summon new items for your pet, which was especially nice for mages (less mana spent on resummoning items, give pet nice weapons/armor, etc).

On a side note, I'm not trying to be argumentative, just trying to make some clarifications.

Back to the original issue, it sounds like, because chanter pets are somewhat unique, they might have been coded differently than regular pets, and there might not be a check for the commands. I'll have to see if I can peek at the source code a little later.