Question - Macros/Luas + EQ Instances

[MindBlayde]

Are MQ macro and Lua add-ons specific to individual EQ instances? Or do they attach themselves to all instances when they're first executed?

Also, do they persist and return when EQ is shut down?

My brain thinks they are instance specific and not persistent, however I'm a bit confused by the status messages that pop up in my foreground EQ instance's MQ window when I issue commands in a background EQ.

I can see how it would be simple to make them fire and forget so they become instance non-specific and persistent (and some definitely seem to be just that), but it strikes me that this may not be desirable behavior.

Perhaps they are a mix of both worlds? If so how do we tell them apart?

Thank you for your patience

 

[Sic]

Are MQ macro and Lua add-ons specific to individual EQ instances? Or do they attach themselves to all instances when they're first executed?

Also, do they persist and return when EQ is shut down?

My brain thinks they are instance specific and not persistent, however I'm a bit confused by the status messages that pop up in my foreground EQ instance's MQ window when I issue commands in a background EQ.

I can see how it would be simple to make them fire and forget so they become instance non-specific and persistent (and some definitely seem to be just that), but it strikes me that this may not be desirable behavior.

Perhaps they are a mix of both worlds? If so how do we tell them apart?

Thank you for your patience

each instance of EQ will run its own instance of MQ

plugins, luas, macros are all only on the instance of MQ that ran them --- meaning just on one character

your plugins retain a "loaded/unloaded" state in your settings and will automatically be the same state they were saved to be.
- /plugin <name> --- this loads <name> plugin and says "please set my configuration ini so that it loads again next time
- - /plugin <name> noauto --- this loads <name> plugin and says "please do not adjust my configuration ini"


luas need to be run manually (or you can utilize something like a .cfg --- like ingame.cfg to automatically load them (i have a video stickied in the lua section about that)
/Lua run <name>

macros are only running on the individual toon when /mac <name> is ran.

mq2dannet, eqbc, and the recent addition of "actors" allow you to see/do things on your background toons.

let's take mq2status for example

if you did the following:

/dgae /plugin status
- that would load mq2status on everyone on your dannet
and then
/dgae /status krono
- everyone on your dannet would report to everyone else on your dannet with how many krono they have

When your eq disconnects from MQ, it is no longer running, many scripts/plugins/luas only run while ingame, but that isn't universal - mq2autologin, for example, is a plugin that runs from just MQ itself - so it operates at character select and whatnot.

but mq is not able to make characters do things when they're not loaded into eq. some folks have made "headless" eq/mq things - but that is far outside of the scope of your question and outside the scope of something that mq natively offers or supports

 

[MindBlayde]

each instance of EQ will run its own instance of MQ

plugins, luas, macros are all only on the instance of MQ that ran them --- meaning just on one character

your plugins retain a "loaded/unloaded" state in your settings and will automatically be the same state they were saved to be.
- /plugin <name> --- this loads <name> plugin and says "please set my configuration ini so that it loads again next time
- - /plugin <name> noauto --- this loads <name> plugin and says "please do not adjust my configuration ini"


luas need to be run manually (or you can utilize something like a .cfg --- like ingame.cfg to automatically load them (i have a video stickied in the lua section about that)
/lua run <name>

macros are only running on the individual toon when /mac <name> is ran.

mq2dannet, eqbc, and the recent addition of "actors" allow you to see/do things on your background toons.

let's take mq2status for example

if you did the following:

/dgae /plugin status
- that would load mq2status on everyone on your dannet
and then
/dgae /status krono
- everyone on your dannet would report to everyone else on your dannet with how many krono they have

When your eq disconnects from MQ, it is no longer running, many scripts/plugins/luas only run while ingame, but that isn't universal - mq2autologin, for example, is a plugin that runs from just MQ itself - so it operates at character select and whatnot.

but mq is not able to make characters do things when they're not loaded into eq. some folks have made "headless" eq/mq things - but that is far outside of the scope of your question and outside the scope of something that mq natively offers or supports

Thank you for such a detailed and thorough response. The way you explain things happening is about how I envisioned, and exactly the way I think it should be from a security perspective.

I'm making an assumption that when you say

When your eq disconnects from MQ,

you mean when the EQ instance shuts down, or are there circumstances in which the EQ client can request or force a disconnection from MQ?

 

[Sic]

you mean when the EQ instance shuts down, or are there circumstances in which the EQ client can request or force a disconnection from MQ?

i added this specifically to cover all the potential bases - your eq crashes, you lose internet and toon is disconnected, server drops, for some-(dumb)-reason you did a /unload

EQ (server side) does not have a way to request mq to close