I'll have it coded and such by tomorrow night. It'll be the first macro/ui combination window, in that it will require a macro to run in the background to function.
Planned Features:
Overall DPS/Damage Dealt
DPS broken down into attacks used(melee, kick/backstab/etc, and non-melee)
Damage taken/overall dps taken
Defense broken down into avoidance(misses), and then defensive skills(block/parry/etc).
What other features are needed in a basic parser?
Additionally I'm going to try and figure out how to easily merge in other macros, so that we can macro while the parse window is running...
DPS/Defense Parser window in the works
Moderator: MacroQuest Developers
DPS/Defense Parser window in the works
OMGWTFBBQ
Will this dissallow the ability to run custom macros, or will there be a way to thread it so you can still run a bot macro or what have you along with the dps parser?
I think it would be pretty sweet if MQ allowed threaded Macros, so you can run 2 macros at once, or however many you need (of course with an upper limit). After all, you can already run a pile of EQs with different macros running in each on one box, why not in the same EQ...
Then again I only konw the theory of threading and would have no clue how to implement it in to MQ.
I think it would be pretty sweet if MQ allowed threaded Macros, so you can run 2 macros at once, or however many you need (of course with an upper limit). After all, you can already run a pile of EQs with different macros running in each on one box, why not in the same EQ...
Then again I only konw the theory of threading and would have no clue how to implement it in to MQ.
-
Omnictrl
Chained Macros
This may already be in place, but it would be nice to be able to install a "service" that stays alive forever, like an "auto loot" service, or a "self heal", or "self buff" service. Something that is either activated by hooking into a service timer, or events. All the services could be chained together, sort of like old DOS TSR's, allowing the incoming events to either be filtered or passed onto the rest of the chain, and of course, allowing it to be filtered from the normal parser.
