Perhaps it's less to do with an instance problem and more to do with that goofy group bug. The same zones I've had issues with instancing also go hand in hand with the problem where my boxes can zone in (even in pub) and not even see each other. A who list clearly shows them in the zone, but on occasion one or more group members will not be visible or even target'able... yet if I switch to that member, I am in that zone. When that happens, I have to camp the affected members and reinvite. I've never had this problem anywhere else other than the aforementioned zones.
And not being open to the zones themselves at least influencing this isn't going to help the problem. The common denominator is staring us right in the face, and I am very well aware of red herrings (my very livelihood has been based on process of elimination for over 30 years). There is something unique about these zones that does influence the problem... something maybe even crazy-sounding like the use of parentheses in mobs' names (which is a ludicrous suggestion, but I'm trying to think of things that are unique).
That's why I am trying to eliminate the easy targets first. As far as I have seen with any type of computer/coding related issue, it's usually the most obvious solution. I can double check to see if there is something special that I have not seen before. The problem children are: TACVI, chambersa, chambersb, and Anguish (correct?).
Some nice ideas. Hopefully if we can re-write the instance code things would be more stable? Again, Akkadius is the one that wrote the current code and is the current expert, but I'd be open to new ideas too, or see if he has any updates since.
I'll try to see what I can do on the weekend. Middle of the week very busy with work.
Hunter
His latest/greatest creation is the SendToInstance tool. However, to fully change that over it would require some hefty recoding. Not necessarily a bad thing, but a time consuming one. Thanks for considering it btw.
-Hate
