edit: I stand corrected, a bug has been fixed which will change how /if { } else {} is handled. Well too late, I read your flame :p. I'm curious though, did rh macro really run without making above mentioned changes? The melee macro I'm using had only one false else line and this was enough to malf...

This macro is working if you take your time to edit the linebreak errors. However there is nothing monkly about it except the flying kick and 'use epic if not hasted' features.

Neat. I made some additional changes in the attackloop. The if statements were cleaned up, since they were evaluating the same variables multiple times. Added a new event OOR which sets TargetOOR to True if it occurs. This enables MeleeDistance updates, incase the mob change runspeed or move too far...

I made some changes to the original code. I'm not using the ini file to set the MeleeDistance. I simply set MeleeDistance to Target.MaxRangeTo at the beginning of fight. As you know Target.MaxRangeTo doesn't return the right maxrange on all mobs. To avoid this problem I added a hitcheck in the :atta...