The LOS flag doesn't seem to work right for some reason because it fails instantly (ie, the client still knows that it is not in line of sight) -- it is not going to the server (you can see this because the spell starts casting, then stops with a message).

Nope, happens to mobs in casting range.

This always happens after a fight finishes (ie, extended target was cleared). Never when idle, no matter how long I wait. Environment was controlled (inside a task). No mobs were moving around. EDIT: It just also triggered after looting a corpse a couple of minutes after a fight. Perhaps triggered t...

I use this code: LineOfSight(GetCharInfo()->pSpawn, target) I think this is bugging since the last or last couple of patches. I notice the following: In a room with several mobs hidden behind walls in other rooms, LineOfSight will return FALSE when "idle". However, after killing one of the...

Also spotted a small bug that may access an item that doesn't exist. if (pAdvLoot && pAdvLoot->pCLootList && pAdvLoot->pCLootList->pLootItem && pAdvLoot->pCLootList->ListSize >= index) { DWORD addr = (DWORD)pAdvLoot->pCLootList->pLootItem; pitem = (PLOOTITEM)(addr + (sizeof(L...

I checked the MacroQuest source code, and if there is a problem there, then I suspect that DoAdvLootAction's (which seems to be an EQ function) first parameter is not what it appears to be. Since the Shared Loot table is sortable (by clicking on the columns), EQ might be keeping track of two index n...

It was using index before, it bugged then also.

I've changed the Loot module to use names instead of numbers, and now it is quite obvious from the logs that something is going wrong. From my EQ log: [15:20:05 2015] 1 item(s): Plain-Looking Scroll given to you. It has been removed from your Shared Loot List. [15:20:10 2015] 1 item(s): Diamond give...

I'll try a start delay... perhaps the list is still populating with the items from the latest kill, causing this glitch.

The loot is triggered though after a fight finishes (xtarget is clear). Any new items that would be added would have to come from a new pull which certainly isn't going to die in a couple of seconds ;-) I'll see if I can trace it down a bit further, or change it to use /advloot shared <name> instead...

I've been testing this, and I noticed something odd. I leave loots in the window and put them to "free grab", so the window is always open and there's usually some stuff in there that is on free grab. What I've noticed is that when I get the SList.Count and I (reverse) iterate through the ...

Well, you can use /delay with a condition, so you could:

/delay 100 ${Me.DistanceTo[loc Y X] < 10}

(syntax might be off, I rarely use the MQ macro language)