Hello,

yesterday we used the addon first time to port our guild raid .
Thanks again for this great addon!
But some features would be nice to have (or I just cant find them ;) )

• have an option like on alt support to just accept requests from people with worldbuffs (or always port them last)

• delete people from the list they are already in the near because of self traveling or someone else without addon ported him
  I think we had the problem that someone in the raid without addon ported a requester and it was not able to delete him from the list then.

• when someone is using this addon on his warlock, and he is relogging to his mainchar in the same raid, the addon is still spamming the annoucements. The only solution to prevent this, is to deactivate the addon on non warlock chars

• have an option like on alt support to just accept requests from people with worldbuffs (or always port them last)

Do you mean only accept requests from people with world buffs?

Making them last priority could be an option, but I imagine that might lead to a lot of heartache (most raiders will be blissfully unaware of the addon or its features and/or not take advantage of them - people with worlds tend to be a bit grumpy about summons :))

• delete people from the list they are already in the near because of self traveling or someone else without addon ported him

I think we had the problem that someone in the raid without addon ported a requester and it was not able to delete him from the list then.

If that is not working it should be. The conditions for being able to be remove people from the list are: if there is no destination set and you are a warlock you can manually remove people, if a destination is set then anyone at the destination with the addon will auto remove, and the warlock who summoned can (wherever they might happen to be.)

Also, when everyone with the addon leaves the destination (some destinations can be quite large if there's no subzone), then any lock can remove. Did that person get summoned a ways away? the range detect is currently about 40 yards, but I guess I could boost that or make it configurable. Probably this is a problem when you're a summon alt, log onto main, and the other locks don't use the addon or something like that?

Unfortunately my guild is full of addon users now so these corner cases get tricky for me to see in action :) I'll figure something out, in the meantime, the person on the list can do -123 and that should get them off.

• when someone is using this addon on his warlock, and he is relogging to his mainchar in the same raid, the addon is still spamming the annoucements. The only solution to prevent this, is to deactivate the addon on non warlock chars

Hmm, I let an edge case slip through there. I'll figure out how that should work given I want people to be able to start a summon list before the locks get on - makes it a bit tricky when the locks go away, but I guess at that point any nags are a bit pointless anyway.

Do you mean only accept requests from people with world buffs?

Making them last priority could be an option, but I imagine that might lead to a lot of heartache (most raiders will be blissfully unaware of the addon or its features and/or not take advantage of them - people with worlds tend to be a bit grumpy about summons :))

Well we are just using it internally for guild raids and we want to force members to collect buffs and not support lazy members :D

If that is not working it should be. The conditions for being able to be remove people from the list are: if there is no destination set and you are a warlock you can manually remove people, if a destination is set then anyone at the destination with the addon will auto remove, and the warlock who summoned can (wherever they might happen to be.)

Also, when everyone with the addon leaves the destination (some destinations can be quite large if there's no subzone), then any lock can remove. Did that person get summoned a ways away? the range detect is currently about 40 yards, but I guess I could boost that or make it configurable. Probably this is a problem when you're a summon alt, log onto main, and the other locks don't use the addon or something like that?

Unfortunately my guild is full of addon users now so these corner cases get tricky for me to see in action :) I'll figure something out, in the meantime, the person on the list can do -123 and that should get them off.

I dont know what was the reason for our problem, we moved our Raid from Aq40 to Blackrock and had a portcrew in Kargath
Someone else logged a Warlock in, probably without addon, and also started to port members. One member was ported but still in the list. Removing from list or -123 wasnt working. So the Next button wasn´t usable anymore.
But when there is already a range check build in, it´s nice. I will try to force every warlock to install the addon next time.

Hmm, I let an edge case slip through there. I'll figure out how that should work given I want people to be able to start a summon list before the locks get on - makes it a bit tricky when the locks go away, but I guess at that point any nags are a bit pointless anyway.

I see and it make sense, maybe I just should tell everyone to deactivate the addon on non warlock chars, otherwise the raidchat got spammed

Well we are just using it internally for guild raids and we want to force members to collect buffs and not support lazy members :D

OK, fair enough. I'll add it as a todo with appropriate warnings in options.

I dont know what was the reason for our problem, we moved our Raid from Aq40 to Blackrock and had a portcrew in Kargath
Someone else logged a Warlock in, probably without addon, and also started to port members. One member was ported but still in the list. Removing from list or -123 wasnt working. So the Next button wasn´t usable anymore.
But when there is already a range check build in, it´s nice. I will try to force every warlock to install the addon next time.

Oh, I really want this stuff to work without having to force anyone to have the addon. I have to assume that's the default case - I'm not that megalomanic :) I have noticed that there is still some (unknown) condition which stops the addon from updating. In that case a /reload does fix it (obviously), but I really want to track down the why - so if you notice this again, another of report of things leading up to it would be good :) That'll help me narrow things down. One question, did anyone with the addon either log in or out about that time?

In the mean time I have a "predictive" fix ready to go which reduces the channel traffic for the "net lead" and shares it a bit more with other addon users that I need to test (this is my top suspect currently). Blizz will shut down comms for an addon that has too much comms in its opinion - I have all the proper checks for that (or I should, its buried in Ace3), and if that happened it would match the symptoms you describe.

I see and it make sense, maybe I just should tell everyone to deactivate the addon on non warlock chars, otherwise the raidchat got spammed

I have a fix ready to go for this, I just need to do due diligence testing at some point to release. Basically any raid wide announcement is switched off if there are no warlocks with the addon at the destination.

really appreciate your efforts!