Lotto - If you figured out ISBoxer then you should be able to figure out MQ2. Both require a fair bit of tinkering to get them working for your setup. MQ2 injects itself into the EQ client. As such each time the client changes MQ2 breaks until someone can reverse engineer the offsets and internal structures.
Since it has most of the important internal structures handy its possible to get almost anything from the client.
MQ2 can do most of the things ISBoxer does and can take your boxing to the next level of automation. But just like ISBoxer you've got a fair bit of tinkering to do.
I use MQ2AutoLogin with WinEQ2 profiles and a small AutoHotKey script to log my crew in. Once there they check to see if they need to claim the free station cash and then start up my macro for botting.
I use MQ2BC and a private chat server EQBCS to communicate between eq clients. This passes the bots hp, mana, etc between clients. It also allows me to send commands like /bc //follow which would have each client issue /follow.
I use a heavily modified version of MQ2AdvPath to record/play back paths for automating running between various places, and for automating some camps.
I use NinjaAdvLoot.inc in my macros to handle looting and selling to vendors.
MQ2FPS is great for limiting screen updates, which lets you load more instances on older hardware. I wrote MQ2CPULoad to do load balancing which is helpful on my older Q6600 cpu.
MQ2Bot, /mac bot, autobot, modbot, and dave's macros are all different attempts to automate clients. Pete's bot code is the easiest to setup.
Keep reading and it will sink in. You didn't learn to play EQ in a day.