Recent content by chrisben

Copy ItemDisplayWindow from Default, and place it in your custom folder.

There were a bunch of accounts that got banned for being "compromised" being logged in by lots of difft people the orig owners tended to have got them back, just had to call and reclaim, provide info etc.

open your main Macroquest2.sln, add the plugins to your main MQ compile. This way you don't have to compile a bajillion plugins seperatly ) save MacroQuest2.sln when you are done, and copy it back in after each new patch. That way you only have to update offsets, and any other struct type...

If EQ is ported to be a DirectX 10 Native Game, then perhaps that'd be a logical statement. I doubt that will happen anytime soon, being that it would exclude so many people looking to stay on (relativly stable) XP

There's a sample macro in the MQ2 forums that gives syntax for using /face /keypress forward, /stick and stuff to avoid the vish DT. (the posted source doesn't work as posted, but isn't too bad to fix up.) (search for vish) I'm just saying it wouldn't be too hard to macro this without using...

Noone on the Gameless?

Re: RedQuest v5.2 (1/17/07 patch) Nope, here's my plugin list. mq2labels=mq2labels mq2itemdisplay=mq2itemdisplay mq2custombinds=mq2custombinds mq2fps=mq2fps mq2map=mq2map mq2bzsrch=mq2bzsrch mq2chatwnd=mq2chatwnd mq2eqbugfix=mq2eqbugfix mq2moveutils=mq2moveutils mq2cast=mq2cast...

Re: RedQuest v5.2 (1/17/07 patch) I'm having an issue with the version of exactspeed that I compiled from your source, but it runs fine with your precompiled version. PS. I'm not running RQ either, I'm using the one I compiled from the macroquest site. Has your source been updated w/ the code...