Macroquest Features / Doc's?

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

AlphaBeta
a ghoul
a ghoul
Posts: 126
Joined: Sat Nov 09, 2002 12:35 am

Macroquest Features / Doc's?

Post by AlphaBeta » Fri Nov 07, 2003 11:17 am

Ok its prolly my fault for not keeping up with the forums like I should :oops:

But... Is there is updated list of microquest features? I just found /mapfilter and now I see Prices on some items I see was added. I think the doc's in general have fell way behind. I would love to see more code examples added. I still can't write a simple macro to save my life :(

I know everyone hates writing doc's.. its a pain the ass. But I think its something that needs to be addresed.

Thanks alot guys <Hugs>

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

Post by Mckorr » Fri Nov 07, 2003 11:20 am

Check the readme file.
MQ2: Think of it as Evolution in action.

AlphaBeta
a ghoul
a ghoul
Posts: 126
Joined: Sat Nov 09, 2002 12:35 am

Post by AlphaBeta » Fri Nov 07, 2003 11:46 am

hiya Mckorr

Yeah I have read the readme file. I just wish it had more detail in it for some things. Also there are commands that no one seems to know what they do or are used for. I guess I like long discriptions with well formated examples.

just looking at the readme file jumping around :


#event varname "string"
Creates a custom event (Sub Event_varname) that occurs whenever string is sent to the chat box. A matching Sub must be used.

I know from reading it that it does something when some matching text goes to the chat box other then that I have no clue on how to use this function. Guess casue I am not a programer type *shrug*

just stuff like that I wish had better discriptions and code examples. Many of the functions and variables are list as:

Name:
One line discription:

I guess what I am looking for is more of a how to guide and not a high level over view of commands. Also a history.txt or .htm would be nice to be able to see fix's, updates, new features added etc..

NotSoCSharp
a ghoul
a ghoul
Posts: 85
Joined: Sat Oct 25, 2003 10:48 am

Post by NotSoCSharp » Fri Nov 07, 2003 11:56 am

I think what we really need is a FAQ or HOWTO for MQ.

How do I do X:



Works great for Linux topics ( and others as well ).

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

Post by Mckorr » Fri Nov 07, 2003 12:58 pm

You just need to look for a matching command. For #event, the matching command is /doevents.

No doubt things could be better. If I get a chance this weekend I'll plug the readme file into HTML Help Workshop and see if I can't get a better layout/format.

Wassup did a great job on the readme file, but it's a struggle to keep up with all the changes. He's doing great just to keep the basic html updated.
MQ2: Think of it as Evolution in action.

wassup
Official Guardian and Writer of TFM
Official Guardian and Writer of TFM
Posts: 1487
Joined: Sat Oct 26, 2002 5:15 pm

Post by wassup » Fri Nov 07, 2003 4:02 pm

I have a newer one that I can send to someone. I'm not sure how well liked it will be, but since I used css for the majority of the file it makes it fairly simple to change.

I asked people to send me critiques on specific sections that need improvement and I can get to it. Suggestions for illustrations or examples can be added fairly easily. I just need to know what slash commands or $variables need attention.

I am more than happy to do this, the devs have alot on their plate.

If you have suggestions feel free to PM me anytime.

I have been sending it to EQMule for updates, but if someone else is willing to take this over from him I can work with them.