MacroQuest64

Greetings Constructs,

I apologize in advance if this is a stupid question. But, in reference to eqjoes comment:

/click is a low priority item IMHO. If you absolutly want to macro /click commands then you can use Xylobot. There have been lengthy discussions on this board about this and Xylobot. Use search for more information.

Question: What ARE the high priority items?
Comments: I have checked the sourceforge bug list and there are very few bugs posted there. This board is a tangle of threads about the status of the application. In my limited time (less than 3 days) with the application I have discovered many new bugs not posted either here or on sourceforge. BEFORE anyone flames me...I will post these bugs when I do more research.

Question: Is there a list of developers?

Question: Are there certain areas that ceratin developers are responsible for?
Comments: It seems that there may be an informal arrangement of responsibilities. However, I was unable to find a centralized location detailing who is responsible for what. Yes, reading posts gives a general idea of some responsibilities (i.e. help and documentation..) But, it might be better to have a more formalized list posted.

Question: <<OT>> How does one qualify to become and official developer?

End of line...

NealThorpayt wrote: Question: What ARE the high priority items?

This is my opinion.

Click is not a priority because implementing click leads to unattented plat farming. That is the surest way to get SoE/VI to crack down on us again. MQ is perfert 2-boxing with a cleric bot and Sony is happy about that (two accounts == $$).

High priority is keeping MQ up and running.

NealThorpayt wrote: Question: Is there a list of developers?

http://macroquest2.com/phpBB2/groupcp.p ... c3bcd3f105

NealThorpayt wrote: Question: Are there certain areas that ceratin developers are responsible for?

No.

NealThorpayt wrote: Question: <<OT>> How does one qualify to become and official developer?

L124RD is the official unofficial leader around here.

No, there is no formal, or even informal, list of responsibilities. Various developers are working on areas that interest them, unless a major problem crops up, whereupon everyone turns their attention to that. For example, I jump back and forth between poking and prodding at /click, and porting this all over to a freeware compiler (Dev-C++ in this case). In between I've restructured the source code tree and set it up for VC6 instead of .NET, but that's only my personal build and not the official party line.

Yes, the board is a tangle of threads, but stick around a bit and you rapidly learn which ones to watch for something useful, and which ones can be ignored. In general, if the thread was started by certain names, usually on the developers list but not always, it might be worthwhile to read it. Unless I started the thread, in which case all flames should be directed at me by private message to avoid messing things up even more.

Current priorities seem to be:

1) Keep it running as EQ's memchecker evolves.
2) Repairing broken structs, since several of them remain either nonfunctional or buggy.
3) Recovering my train of thought....
4) Fixing /click... and this doesn't really get done because we are busy working on 1 and 2.
5) Possibly simplifying the actual macro language itself, since it can be a bit cryptic in places. This will never get done because of 1, 2, and 4.

Finally, if you want to join the ranks of the developers NealThorpayt, talk to L124RD. Your fix for the guild tags, and your beginning work on /charinfo probably qualify you.

Feel free to PM me if you want to talk about any of this.

Salutations,
If you are a dev, you do waht you want to. Just got up? want to work on it? get the CVS tree, when you're done email anything you want to contrib to dont_know_at_all (our new cvs admin, though I haven't spoken to dont_know about this... :p)
What needs to be done:

• High Priority:
  • keep mq working
    fix all the broken structs
    make sure all commands actually work still
  Medium Priority:
  • /forget <gem>
    $target(pid) & pids on /who list
    $screen(NewUI|x|y)
    keybind lookup, $key("Move_Forward") $key("Jump")
    bind macros to keys (?)
    fix flood crashes
    $char(stamina,xxx)
    $looting
  Low Priority:
  • Fix /face to do real turning
    Clean up Code
    Events for HP/MP/Stamina/Target changes
    /varcalc to handle ,
    Packet loss Checking
    MouseLoc for new UI
    text file IO (?)

If you want to become a dev, PM or email me and I'll be happy to add you, you seem like you have already gathered alot about the MQ code and will be a very good addition to the project.[/code]

I'm the one that submitted the PID thing, and upon further reflection, I believe it's probably server-side.... forget $target(pid) and pids on /who, unless you think it could still be client-side.

after all, why would the client need to know the individual account ID of each other player in the zone?

PID's were avaliable on /con last I knew, but not by a /who, but that was awhile ago.

Just wondering (yep, have tried search, A LOT)

With the new CVS version of MQ, does /click work again ????

Now that MQ will be "buyware", i would like to know what works in the package

No, /click still isn't functioning, and the 'payware' thing was an April Fools joke that should now be removed from the homepage in my opinion.

/click is still broke. It's all over the boards.

The buyware thing was an april fools joke. Macroquest is released under GPL which means they could charge for it but they still would have to supply the source which would be freely distributable.