mouse position?

returnfire · Post by **returnfire** » Sun May 09, 2004 3:08 am

trying to get mouse position

none of the following seem to work. Done a complete search on the forums...

${mouse[x]}
${mouse.x}

${mouse[X]}
${mouse.X}

$mouse[x]

Suggestions?

Thanks

Lax · Post by **Lax** » Sun May 09, 2004 4:25 am

The mouse position isn't in MQ2Data. What exactly are you wanting it for?

returnfire · Post by **returnfire** » Sun May 09, 2004 10:46 am

I have an addition to the cleric Genbot I have written for raids. When the raid pulls a ton of adds, clerics are expected to F8 and then assist... and see if PC the mob has targetted needs a heal. Carpal tunnel here I come.

So, I wrote something that gets a list of the closest 4 mobs in the area (less than 200 radius, non-dead). It checks their health (interesting issue here actually that appears to be a bug, see PS below) to ensure the mobhealth < 95% (to ensure tanks are sufficiently aggroed on them and then the program targets their target, healing as appropriate (the 95% thing is to stop me from healing the puller and getting mobbed on incoming from heal aggro). That way I can scan with my cleric the local pulls and watch over multiple tanks. Especially useful in trash mob clears.

Problem is that when I want to stop and go off auto-heal mode I just want to start moving the mouse. So I thought to write a little routine that stops the auto-pull if the mouse has NOT been in one position for less than two seconds. That is, if the mouse is changing position greater than a certain rate of time, it will pause the autoheal routine and let me take care of a certain buff manually.

So, basically, it is a crude interrupt routine. Is there a better interrupt routine for mouse events? "If mouse Move"? "IfMouseButtonDown"?

RF

ps- Minor issue-- I was scanning constructed list of local mobs using ${Spawn[array[x]].PctHPs and for some reason it does NOT update the PctHPs... I had to TARGET them before it would update. Still testing this to see if this is just my bad programming or not.

elkcit · Post by **elkcit** » Sun May 09, 2004 11:18 am

believe that is because the server may not be updating the information to the client until the entity is targeted..

returnfire · Post by **returnfire** » Sun May 09, 2004 11:43 am

elkcit-- Yes, that was what I had thought, looks like that ONCE you target it, spawn will continue to update it for you... but it appear you have to have targetted it once for HP info to come over.

Any info on the a mouse-event approach?

ml2517 · Post by **ml2517** » Sun May 09, 2004 11:47 am

Are you certain that it keeps sending you info on that mob after one targeting? This would be helpful if this is the case.

returnfire · Post by **returnfire** » Sun May 09, 2004 11:52 am

No, just checked. Does not. You have to continually target to get updated information.

RF

Chill · Post by **Chill** » Sun May 09, 2004 1:14 pm

k I dont think I can find the mouse info either, but I came up with 2 other possible solutions:

1) A simple /endmacro hotkey

2) You could check for ${Me.Moving} instead of mouse movement, and then just nudge yourself to stop the macro.

returnfire · Post by **returnfire** » Sun May 09, 2004 2:20 pm

Chill:

1. end macro is not what I want to do hehe... this is what I do now.
2. Nudging is good idea, but in a raid running around a lot anyway...

Basically in meantime am setting up a hotkey that sets a variable to lock it out of calling the routine. The MouseMoveCheck was the routine I was writing to SET to variable for lockout.

This is something only LAX can do it looks like hehe.

RF

Lax · Post by **Lax** » Sun May 09, 2004 2:53 pm

I'll add the mouse positions. I was keeping them out as long as possible to keep people from writing routines that have more accurate replacements but your idea is fine