macro woes

A forum for the general posts relating to MacroQuest. *DEPRECATED: This forum is no longer in public use, but remains here for your reading pleasure. Enjoy

Moderator: MacroQuest Developers

MacroFiend
a grimling bloodguard
a grimling bloodguard
Posts: 662
Joined: Mon Jul 28, 2003 2:47 am

Post by MacroFiend » Sat Oct 11, 2003 11:44 am

I'm asking because I'm not finding it on the M$ site. I've been usingVS.NET 2002 w/o any issues

bob_the_builder
a hill giant
a hill giant
Posts: 275
Joined: Tue Jul 22, 2003 1:22 pm

Post by bob_the_builder » Sat Oct 11, 2003 11:57 am


Mckorr
Developer
Developer
Posts: 2326
Joined: Fri Oct 18, 2002 1:16 pm
Location: Texas

Post by Mckorr » Sun Oct 12, 2003 7:44 am

For Visual Studio .NET:

1) Unzip latest .zip file, making sure to use existing folder names to preserve directory structure.

2) Double click on the .sln file to open the Visual Studio .NET solution.

3) On the menu, click Build --> Configuration Manager. You get a dialog box. Make sure it is set to Release, and then make sure the check boxes are marked for EQLib and MacroQuest. Then click Close.

4) Build --> Clean Solution

5) Build --> Build Solution Make sure you see the message in the compiler window that says "Build: 3 succeeded, 0 failed, 0 skipped", or 2 succeeded if you didn't build mqext.

6) Copy eqlib.dll, macroquest.exe, eqgame.ini, and locations.txt to your MacroQuest working directory. In other words, don't run MQ out of the Release directory. That avoids having to redo your MacroQuest.ini file every time you download a new source, which fixes an amazing amount of problems believe it or not :)

7) Double click macroquest.exe. Move mouse over icon in system tray, make sure it doesn't vanish. Then go into EQ and check.

If this doesn't work, tell me exactly which step failed.
MQ2: Think of it as Evolution in action.

MacroFiend
a grimling bloodguard
a grimling bloodguard
Posts: 662
Joined: Mon Jul 28, 2003 2:47 am

Post by MacroFiend » Sun Oct 12, 2003 9:13 am

Addendum to #6: Copy MacroQuest.ini to your MacroQuest working directory if you don't already have a copy in the folder.

van
a lesser mummy
a lesser mummy
Posts: 37
Joined: Mon Jun 24, 2002 1:04 am

Post by van » Sun Oct 12, 2003 11:04 am

chosing the correct project file fixed most of it for me (not converting to 7.0).

but now any var seems to be incorrect.

rest of it works.

now to try to figure out what all those obj files are in release
and why

/varset v80 0

comes up with an error

if anything i am learning somthing :D

insanitywiz
a hill giant
a hill giant
Posts: 250
Joined: Mon Jul 08, 2002 7:50 am

Post by insanitywiz » Sun Oct 12, 2003 1:59 pm

What macro are you using to test? Does it have a /declare v80 in it? It sounds like you may be using an old (pre-@param) macro.

van
a lesser mummy
a lesser mummy
Posts: 37
Joined: Mon Jun 24, 2002 1:04 am

Post by van » Sun Oct 12, 2003 2:10 pm

thats it... i have to declare vars now..
knew somthing changed.. ben meaning to re-write my cleric-tank macro anyway