Macro Depot as a Files section?

[L124RD]

Salutations,
here goes... thought on implementation.


FileSystem:

MacroQuest.sf.net: Download Listing (on forums too?)
MySQL Table of Macros: ID, Filename, Name, Date, Author, Description.

Mirrors: /path/to/macroquest/mirror/ID


Mirrors:
MacroQuest.sf.net: mirror listing (mysql?)
ID, Name, Domain, full (web) path, last updated (?)


Mirror Updating:
macroquest2.com: no clue... anyone?


as you can see its not complete but... um... yeah...

[Mckorr]

Classes... I don't see any real need. We'd just be complicating the syntax more, and you have to admit that it can already get confusing enough. A simple agreement on file extensions would support much of the reorginazation (sp?). Then allow MQ to target include files in a subdirectory of the macros directory, .\macros\include.

Note to self: Write generic targetting routine (haven't done that one yet for some reason). Something that will take a passed parameter, add alerts, then target it when the passed spawn name(s) within the blue con range of the character's level appears.

Code: Select all

#include routines.inc
#include targetting.inc
#include fighting.inc
#include looting.inc
sub Main
/call target Mckorr
/call melee
/call loot
/return

(Nonworking code, so don't bother using it)

[lifewolf]

You dont really need a file depot. If we can get people organized and teach them how to write a GOOD macro...

I didnt really look at the macro kit, but something like that makes it a lot quicker and simpler to make macro. However it does little for a macro that in 1/2 a second must think "Do I have to heal anybody?" "Is my HP ok?" "Should I tell them im almost oom?" "are buffs holding?" "is anyone taking a lot of DPS that isnt a 'melee' ?" "which of these 80 spells should I cast?!" "Do I need to click my horse again?" "is anyone commanding me?" "do I hate cheese.mac like the wolf?"

[Mckorr]

I don't use MacroKit for long, involved bots. I just use it if I need to hunt one particular mob, or throw together a one time event. I write almost all my macros on the fly, and don't try to automate the character. Just some tedious quest tasks.

That being said, an object oriented approach does work well if you need something NOW, instead of taking days to write it. For times when you aren't worried about a bug in the script, as long as it accomplishes the task.

It also works well if you find yourself cutting and pasting the same code over and over again. Just use an #include to the existing code.

What I've found it does NOT work well for is /doevents. I've had nothing but failures there, find it almost won't work at all if you don't put those in the main macro.

And I will admit limitations on spell casting. I can get away with it because most of my characters use the same scheme for spell assignment (healing is always gem 5, etc.) But I can see how a more sophisticated player would want to work each set of code from scratch.

[Lord Yei]

I have space as well...FTP or webspace