Lets look at this, you want... A way of telling where a event came from... (#event CurePerson "#1# tells you, '#*##2##*#'")(assuming I remember my MQ2 right) A faster way of handling said events... (still have to wait for /doevents) And a decentralized way of doing incoming chat... (becaus...

Change ${Me.Buff[Skinspikes]} To ${Spell[Skinspikes].Stacks} That way you don't keep trying to cast it if someone else has given you a better DS that doesn't stack. You can set a bool when you lose the DS, and then have a buff sub that checks all your bools, and recasts any buffs that are marked as ...

overnight dual prime95s in stress mode, no harm in doing that, and you will find out if your cpu is stable.

Programming in general will help you write macros better, but learning the macro language is a place to start also, just don't get used to the goto's when you move to other languages.

Have FreqMod and Freq, then just load and save window positions, takes all of a couple seconds per window, once a month or less.

http://www.macroquest2.com/wiki/index.php/DataType:math

Check out Distance

Well I didn't do much at all, I made it sit between casting. I use the ViP spell_routines.inc and didn't test with SpellCast.inc. I changed the include to the SpellCast.inc so that a ton of questions don't come up about where to find the ViP one. This also includes the destroy no-rent lines of code ...