ok thanks, it definitely seemed like i was triggering some kind of anti-cheat mechanism but i couldn't figure out why. i had 3 toons each in their own jaggedpine and they all had the same 3 hotkeys: target wisp /stick, pet attack (because auto attack while sticking to a moving target is sketchy at best), and target corpse /loot. so i would send the first guy after a wisp, kill it with pet, loot for gls, then send him after another wisp. while hes running i tab to the second guy, send him after a wisp, etc. so that whenever i tab in to one of the 3 chars he is sticking on a wisp ready for me to pet attack and loot it. all of the actions are manual aside from the running with /stick, even the looting and combining GLS. based on the description of fan botting i get why the instances are dropping, just wanted to make it clear that i'm not breaking any rules (at least afaik)

as a somewhat newer player i don't have really any idea how offensive or inoffensive the exploit was, but i'm generally against bans since we have a relatively small playerbase and the low-mid tier players rely on the higher tier guys for info, advice and help. also cancelling the halloween event would be a bummer and would punish those of us who have already suffered so much traumatic screen shaking

checken

i've had multiple disconnects about every 20-30min when farming SLS in jaggedpine. the characters can still move but cannot attack, cast or loot and then after 3 minutes or so they actually DC. the weird part is that 3 characters in 3 jaggedpine solo instances all have this problem simultaneously. just curious if there's something weird happening since i'm not zone pulling, aoeing, or anything that would cause server trouble. just killing wisps one at a time on 3 toons

     When a corpse is stuffed to the brim, some items get skipped over.  Some gems that are marked for destruction remain, and one dragon is looted but the rest (marked destroy) remain on corpse.  One gem + 3 ores remain on corpse.
     The crystals are ignored, but the augments are destroyed on one corpse, but on another, the opposite happens.

the destroy option has been similarly unreliable for me. i'd recommend just using ignore (or removing the item from the list) rather than destroy, because if destroy hiccups and you're left with some gotdamn zany zingers on your cursor you wont be able to loot a real item if it comes up next. i went through and just removed all the "destroy entries" from my .ini and it's been smooth sailing.

when "destroy" bugs it looks to me like it's going through the destroy button logic before the item is on the cursor, which means you're left holding it afterwards. if the next item you encounter is also a "destroy" this resolves itself but if it's a "keep"er you get the "can't loot with item on cursor" error and skip the corpse. the destroy-before-loot issue seems to happen reliably with certain items although it's seemingly unrelated to ABC order, as both delicious pumpkin bread and zany zingers fail while pumpkin candy works perfectly. i skirted around it by taking out all the "destroys" as mentioned above, and supervising the looter during the process (only because i'm paranoid, haven't seen it miss any goodies since removing "destroy" flags).

overall this macro is a huuuge qol improvement, 5 stars!